K2 Five (5.3) November 2020 Cumulative Update

  • 26 November 2020
  • 1 reply

Badge +9

K2 Five (5.3) November 2020 Cumulative Update


K2 Five 5.3
K2 Five (5.3) April 2020 Cumulative Update


The K2 Five (5.3) November 2020 Cumulative Update contains updates and fixes for issues reported in K2 Five (5.3). K2 recommends keeping your K2 environment updated by installing the latest cumulative update, and that you test this update before you deploy to a production environment.

Prerequisites and Dependencies

This cumulative update is only compatible with K2 Five (5.3). Each new cumulative update contains the updates and fixes that were included with the previous cumulative updates. The cumulative update does not require any previous cumulative updates or fixes to be installed, and no additional cumulative update is required to fully update a K2 environment. If you have installed individual code fixes included in this cumulative update, those code fixes are not changed unless a newer version of the code fix is available for the update.

Before you install this cumulative update, please check the K2 Product Releases and Build Numbers article to verify that this is the latest cumulative update available and that you have a current backup of your K2 database.
Database owner permissions are required to install this cumulative update or any of the fix packs.



Getting and installing the update

You can download the K2 Five (5.3) November 2020 Cumulative Update on the K2 Partner and Customer portal.

Download Now

To install the cumulative update, run the cumulative update installer on every machine in your environment where a K2 product or component is installed, including desktop machines that have K2 Studio or K2 Designer for Visual Studio installed. The same installer is used to update the specific K2 products and components that are installed on that machine. To determine which cumulative update or fix pack has previously been installed in your environment see https://help.k2.com/kb000426.

Install Instructions
    1. Backup your K2 database.
    2. Download the K2 Five (5.3) November 2020 Cumulative Update.exe.
    3. Double click the .exe file and select a location to extract the installation files.
    4. The Update window opens. Click Change if you need to change the K2 database. Select the correct information and click Accept. Click Update to start the installation.
    5. A warning is displayed if a backup of the K2 database is not found. Create a backup before selecting OK. Click OK on the warning window to continue with the update. Click Cancel if you want to create a backup first.
    6. After creating the backup, you can click Update again on the Install window. If a backup for the K2 database was recently performed, the installer shows you the date and time of the last backup.
    7. Click OK to continue with the update.
    8. Wait for the update to complete, and then click Finish.
Rollback Instructions
  1. To rollback the K2 Five (5.3) November 2020 Cumulative Update, uninstall K2 from your environment.
  2. Re-install K2 Five (5.3).
  3. Restore the K2 database using the backup made before the update.



Included in this Update

This cumulative update includes the following fixes:

Previous Fix Pack fixes
New fixes in this Cumulative Update
  • When you have multiple participants for a task with the configuration one (1) slot to action the task, if one participant opens their worklist, all the participants status display as completed in reports for the specific Task, instead of expired.
  • When you design a view and use a pipe (|) in the HTML property of the RichText control and the Design View option is disabled, attempting to edit the view results in the designer to become unresponsive.




There are no known considerations for this cumulative update at the time of release.


1 reply

The FixPacks Guides always specifies 

"Database owner permissions are required to install this cumulative update or any of the fix packs.", and my ServiceUser is dbo, but the Installation promts that it needs the rights dbcreator und securityadmin. Is this really needed, am I doing something wrong or do I missunderstand the "Database owner permissions"?


Kind Regards