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 three Kanban Task Manager editions.
This allows us to be both backwards compatible and future-proof.
One product with three editions
The three 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 the differences depend
solely on how sandboxed solutions, add-ins and client-side
web parts behave in SharePoint.
Installation in site
All editions are used in a site, and Kanban Task Manager
creates a tasks list and a settings list where all the data
and settings are stored. It is not possible to have more
than one installation in the same site, so when there is
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 page
Kanban Task Manager can be embedded in a page with
the embed code found in the settings, with the add-in edition
app part or by using the client-side web part.
Supported SharePoint versions
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
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 client-side web part has been deployed in
the farm's or tenant's app catalog, it is available to all
users for embedding in modern pages. Soon it will also be
available for Teams.
Try the Kanban Task
Manager for SharePointClient-side web part
- The Kanban Task Manager client-side web part
is intended for modern SharePoint pages and Microsoft
- When the .sppgk file has been uploaded and deployed
in the organization's app catalog, Kanban Task Manager
is available among the web parts in all modern pages.
- 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 modern SharePoint page, so
that it can be embedded 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 embed
the modern webpart in many pages in the same site, all
those pages use the same tasks and settings lists.
- SharePoint sites with client-side web parts cannot be saved as
- 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.)
Sandboxed Solution .wsp
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.
Try the Kanban Task
Manager for SharePoint Sandboxed Solution
- 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,
custom script is enabled in the SharePoint Admin
- 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
- 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
- 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.
The add-in edition is recommended for organizations who
use SharePoint on-premise with modern SharePoint sites and
pages but still have not upgraded to SharePoint 2019.
Try the Kanban Task Manager
for SharePoint Add-in
- The Kanban Task Manager add-in is primarily
intended for modern sites. It is installed in each site
with the "add an app" command.
- The .app file can be downloaded from the kalmstrom.com
website or from SharePoint Store.
- When the .app file is downloaded from kalmstrom.com
and then uploaded to the organization's app catalog,
it becomes available to the whole farm or tenant under
"Apps You Can Add".
- The add-in creates its own Kanban Task Manager
"app web" connected to the site where it is installed
(called the host web), and Kanban Task Manager
is displayed on its own page in that app web. The url
of the app web is very different from the host web's
- SharePoint sites with add-ins cannot be saved as
- You can embed the add-in with a web part that is
contained in the the .app file. In a modern page, it
is dsplayed among the other modern web parts. In a classic
page, the same web part is called an "app part".