Kanban Task Manager Editions
Microsoft has given three major ways to build tools for
SharePoint: the classic sandboxed solution with .WSP packages,
the add-in APP packages and the new SPFX technique for
client-side web parts, with SPPKG packages.
These tools all have their different toolsets, Microsoft
recommended techniques and gotchas, but the kalmstrom.com
team has managed to work around all that and created one
common build for all Kanban Task Manager editions.
This allows us to be both backwards compatible and future-proof.
One product with four deployment editions
The different Kanban Task Manager editions are one
product, so you can use and combine them as you like. They
have the same version number and features, and any differences
depend solely on how sandboxed solutions, add-ins and client-side
web parts behave in SharePoint.
We also supply a PowerShell script for smooth installation
and upgrade in multiple sites.
Installation in site
All editions are used in a site, and at installation,
Kanban Task Manager creates a tasks list and a settings
list where all the data and settings are stored.
When there is already an existing installation in a site,
any new additions of Kanban Task Manager will use
the same tasks and settings lists, no matter which edition
it is. Any changes in one instance of Kanban Task Manager
in the site are reflected in the other instances in the
same site.
Embed in pageWith the client-side web part edition, you can embed Kanban Task Manager in modern as well as classic pages. The sandboxed solution and the PowerShell editions has an
embed code for classic pages in the settings.
Supported SharePoint versions
| File type |
SP 2013 |
SP 2016 |
SP 2019 |
SP Online |
| .spppkg |
No |
No |
No |
Yes |
| .wsp |
Yes |
Yes |
Yes |
Yes |
| .app |
Yes |
Yes |
Yes |
Yes |
| .ps1 |
Yes |
Yes |
Yes |
Yes |
Overview
The most detailed descriptions of the Kanban Task Manager
SharePoint editions are given in the
manual, but these are the important differences:
Client-side web part SPPPKG file
The client side web part is very easy to manage, so this
is the edtion we recommend you to use when it is possible.
As soon as the SPPGK file has been deployed in
the tenant's App catalog, the web part is available to
all modern and classic site pages in the tenant. Soon it will also be available
for Teams.
- The client-side web part never has its own SharePoint
page or subsite. Instead it shows up among the other
web parts when you edit a SharePoint page, so
that it can be added there.
- The first time the Kanban Task Manager client-side
web part is added to a page in a site, the task list
and the settings list will be created. If you add
the webpart to many pages in the same site, all
those pages will use the same tasks and settings lists.
- SharePoint sites with client-side web parts cannot
be saved as site templates.
- To be released soon: When the Kanban Task
Manager client-side web part Teams synchronization
has been activated in the app catalog, Kanban Task
Manager can be added to a tab in a Teams chat or
channel. (A SharePoint site is automatically created
when you create a team, and that is where the actual
Kanban Task Manager installation is hosted.)
Download and learn more
about the Kanban Task Manager for SharePoint Client-side
web part
Sandboxed Solution, WSP file
Sometimes you hear that Microsoft has deprecated sandboxed
solutions, but that is not true. What has been deprecated
is custom code in sandboxed solutions, but the kalmstrom.com
SharePoint solutions do not contain such code. Instead our
products build on no-code sandboxed solutions, which Microsoft
will continue to support.
FAQ
- The Kanban Task Manager sandboxed solution
.wsp file is primarily intended for classic site collections,
but it can be used for modern site collections too,
if
custom script is enabled in the SharePoint Admin
center.
- The sandboxed solution is downloaded from the kalmstrom.com
website and uploaded to the root site of a site collection.
When the file has been activated in the root site, it
is available for all sites in the collection, but the
feature must be activated on each site where it should
be used.
- The sandboxed solution creates a ktm_sp folder with
the Kanban Task Manager files when the feature
is activated for a site. The content in these files
are displayed on its own Kanban Task Manager
page.
- The Kanban Task Manager site can be saved
as a site template. Just note that when you restore
the site template on a newly created site collection,
upload the Kanban Task Manager .wsp file too
(along with the site template .wsp file).
- The sandboxed solution can be embedded in a classic
or modern page with the embed code given in the Kanban
Task Manager settings.
Download and learn more
about the Kanban Task Manager for SharePoint Sandboxed
Solution
Add-in, APP file
The APP installation creates a Kanban Task Manager "app web" connected to the site where it is installed (the host web), and
Kanban Task Manager is displayed on its own page in that app web. All content is stored in the host web.
- The Kanban Task Manager add-in is intended for modern sites. It is installed in each site
with the "Add an app" command.
- When the APP file is downloaded from kalmstrom.com
and then uploaded to the organion's App catalog,
it becomes available to the whole farm or tenant under
"Apps You Can Add".
- SharePoint sites with add-ins cannot be saved
as templates.
Download and learn more about
the Kanban Task Manager for SharePoint Add-in
PowerShell edition, PS1 file
To use the PowerShell edition, you should have some earlier
experience of PowerShell, but is is the quickest method
to install and upgrade Kanban Task Manager in multiple
sites.
You will have a package with a .ps1 file that should be
modified and run in PowerShell ISE. When the script is run,
all sites that are included in the script will get Kanban
Task Manager. The script installs an edition that
reminds of the sandboxed solution.
Download and learn more about
the Kanban Task Manager for SharePoint PowerShell
edition
|
