No ratings

K2 Five (5.3) November 2020 Cumulative Update Fix Packs

Fix Pack

Release Date

Download Link

Fix Pack 22 19 August 2021 Download Fix Pack 22
Fix Pack 21 5 August 2021 Contact Support for this Fix Pack
Fix Pack 20 29 July 2021 Contact Support for this Fix Pack
Fix Pack 19 19 July 2021 Contact Support for this Fix Pack
Fix Pack 18 8 July 2021 Contact Support for this Fix Pack
Fix Pack 17 30 June 2021 Contact Support for this Fix Pack
Fix Pack 16 25 June 2021 Contact Support for this Fix Pack
Fix Pack 15 27 May 2021 Contact Support for this Fix Pack
Fix Pack 14 21 May 2021 Contact Support for this Fix Pack
Fix Pack 13 7 May 2021 Contact Support for this Fix Pack
Fix Pack 12 16 April 2021 Contact Support for this Fix Pack
Fix Pack 11 9 April 2021 Contact Support for this Fix Pack
Fix Pack 10 26 March 2021 Contact Support for this Fix Pack
Fix Pack 9 12 March 2021 Contact Support for this Fix Pack
Fix Pack 8 4 March 2021 Contact Support for this Fix Pack
Fix Pack 7 26 February 2021 Contact Support for this Fix Pack
Fix Pack 6 11 February 2021 Contact Support for this Fix Pack
Fix Pack 5 5 February 2021 Contact Support for this Fix Pack
Fix Pack 4 28 January 2021 Contact Support for this Fix Pack 
Fix Pack 3 8 January 2021 Contact Support for this Fix Pack
Fix Pack 2 23 December 2020 Contact Support for this Fix Pack
Fix Pack 1 15 December 2020 Contact Support for this Fix Pack

Prerequisites and Dependencies

The Fix Packs are only compatible with K2 Five (5.3) products. Because Fix Packs are cumulative, each new Fix Pack contains the updates and fixes that were included with the previous Fix Pack releases. K2 Five (5.3) November 2020 Cumulative Update must be installed first after which the latest Fix Pack must be installed. To determine which cumulative update or fix pack has previously been installed in your environment see https://help.k2.com/kb000426.

 

Installing the Fix Pack

To install the Fix Pack, run the Fix Pack 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. 

  • Backup your K2 database.
  • Download the K2 Five (5.3) November 2020 Cumulative Update FP.exe.
  • Double click the .exe file and select a location to extract the installation files.
  • 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. 
     

    1.png

     

  • 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.
  • 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.
  • Click OK to continue with the update.
  • Wait for the update to complete, and then click Finish.
  • If you need to view the installation log file, open it from the link at the bottom of the Update window or you can locate the InstallerTrace[date].log file in the %temp%\K2 Setup Log folder.

 

 

Rollback Instructions

 

  • To roll back the K2 Five (5.3) November 2020 Cumulative Update Fix Pack, uninstall K2 from your environment.
  • Re-install K2 Five (5.3).
  • Re-install K2 Five (5.3) April 2020 Cumulative Update.
  • Re-install the Fix Pack you had installed prior to this rollback.
  • Delete the database created when you re-installed.
  • Restore the K2 database using the backup made before the update.

 

You can also restore the K2 database before re-installing K2. When you re-install, you can just point to the restored K2 database.

Considerations

If you had K2 4.7 installed before any of the K2 Five versions, and you make use of the client tools that was installed with K2 4.7, you need to start the re-install with K2 4.7 before you can re-install the K2 Five version.

 

Fix Pack 1

This fix pack includes the following fixes:

  1. Code Fix: In some instances where the originator of the process has an underscore in the username, the originator is not displayed correctly
  2. Code Fix: K2 expression numbers are converted into scientific e-notations
  3. Code Fix: K2 on-premises Sync Engine takes a long time to sync ADFS users and groups
  4. Code Fix: When attempting to add a document to a SharePoint Document Library, an error occurs
    • Consideration
      After installing the Fix Pack, you need to refresh the DocuSign Service instance and SmartObjects.
  5. Code Fix: The Image Attachment control is not executing the On Change rule when a transfer rule transfers an empty value

Fix Pack 2

This fix pack includes the following fixes:

  1. Code Fix: Chinese characters do not return when you execute a SmartObject created from an Oracle stored procedure
  2. Code Fix: When adding a new Endpoints Web Service Instance or Endpoints Assembly Service Instance on a K2 Node Cluster environment, the new Service Instance does not show in all nodes

Fix Pack 3

This fix pack includes the following fixes:

  1. Code Fix: When you use OOTB Identity versus sync legacy Identity you don't give the exact same FQN format when you set the provider ID to UserPrincipalName and Name to SamAccountName. OOTB would have the FQN as Label:UserPrincipalName where as legacy sync would use the provider name to set the FQN giving you Label:SamAccountName
  2. Code Fix: When you have a checkbox or radio button control to the right on a form, clicking either of the controls results in the focus on the form to scroll back to the left
  3. Code Fix: When you copy and paste Tasks in a workflow, the system name of the copied task displays the existing Task step display name instead of the default name

Considerations:

Note: These steps should only be used if the LDAP Service Provider is used for Sync Service. Using this for any other Service Provider might result in data not being synced.

 

After installing Fix Pack 3, the following SQL scripts need to be completed in SQL Management Studio. This is important for the first code fix listed in Fix Pack 3:


Step 1 

--Set @ProviderName to the one created, then execute to get the ProviderInstanceID
--A provider can have more than one instance so one would need to know which one to choose when there is more than one result, or incase both needs to be added step 2 needs to be performed for each. (Copy and paste below into new query for SQL against K2 DB)

DECLARE @ProviderName NVARCHAR(20) = 'K2LDAP';
select [p].[Name], [pi].ID as [ProviderInstanceID] from [K2].[SyncEngine].[Provider] as P
join [K2].[SyncEngine].[ProviderInstance] as [pi]
on P.ID = PI.ProviderID
WHERE [p].[Name] = @ProviderName
  --DECLARE @PName NVARCHAR(20) = 'K2LDAP';


STEP 2, (Copy and paste below into new query for SQL against K2 DB)

--Update @ProviderInstanceID with ID result from step 1 and execute the insert with it
--SyncEngine ProviderInstanceRuntimeConfig has configs per Provider Instance 

DECLARE @ProviderInstanceID NUMERIC(3,0) = 6;
INSERT INTO [SyncEngine].[ProviderInstanceRuntimeConfig]
           ([ProviderInstanceID]
           ,[ConfigKey]
           ,[ConfigValue])
VALUES
           (@ProviderInstanceID
           ,'UseLegacyPropertyBehavior'
           ,'True')


STEP 3, (Copy and paste below into new query for SQL against K2 DB)

--Set @ProviderNames separated with ; for all the Provider labels that needs to run with new changes
--example: K2LDAP or for multiple K2LDAP;K2LDAP2;TEST
--SyncEngine RepositoryConfig is a global config and thus all Providers get added to one config setting

DECLARE @ProviderNames NVARCHAR(20) = 'K2LDAP';
INSERT INTO [SyncEngine].[RepositoryConfig]
           ([id]
           ,[ConfigKey]
           ,[ConfigValue])
     VALUES
           ('579E84D3-758B-42F6-A6DB-AB1BD63C0296'
           ,'ProvidersLegacyPropertyBehavior'
           ,@ProviderNames)


STEP 4
--Restart K2 server
--Run  System > Sync Service > Operation > Start Sync again
--Provider Name: K2LDAP 
--Run the UMUser > Get Users to see the being returned, the format for FQN will be K2LDAP:[user@domain]
--Run the UMUser > Get User Details for K2LDAP:[user@domain]

 

Fix Pack 4

This fix pack includes the following fixes:

  1. Code Fix: If you apply styling to a list view or editable list view at design time, the styling is not applied in runtime.
  2. Code Fix: After upgrading from K2 Five (5.2) May 2019 Cumulative Update with Fix Pack 47 to K2 Five (5.3), an error occurs on a sub workflow when the sub workflow starts.

Fix Pack 5

This fix pack includes the following fixes:

  1. Code Fix: An error occurs when attempting to deploy a package containing a large form when a corrupted entry was created at the time of creating the package and deployment .zip file. Error Message: "SourceCode.ComponentModel.Zip.Zip.BadReadException: bad read of entry".
  2. Code Fix: A user with Modify rights on a Role can't edit or access the role.

Fix Pack 6

This fix pack includes the following fixes:

  1. Code Fix: Unable to deploy a package to the target environment, even if no errors occurred when the package was created.
  2. Code Fix: When you use multiple users for a Task even in an IF inline function, the users are concatenated and do not receive worklist items.
  3. Code Fix: When running a sync on an ADFS provider, multiple errors are logged.
  4. Code Fix: An error occurs when you install K2 Five (5.3) November Cumulative Update FP 5 due to the K2 Server taking to long to start.

Fix Pack 7

This fix pack includes the following fix:

  1. Code Fix: When you use the Active Directory "Everyone" group for K2 permissions, an error is logged in the Host Server log file.

Fix Pack 8

This fix pack includes the following fix:

  1. Code Fix: When an Active Directory username contains "NUL", the user is unable to log in to K2.

Fix Pack 9

This fix pack includes the following fix:

  1. Code Fix: When you use the Envelope Audit SmartObject, an error occurs.

Fix Pack 10

This fix pack includes the following fixes:

  1. Feature Enhancement: When adding assemblies that contain methods with the same names in different cl....
  2. Code Fix: Formatting is not applied correctly to drop down list values.

Fix Pack 11

This fix pack includes the following fix:

  1. Code Fix: An error occurs on email steps when you use SMTP configurations.
  2. Code Fix: When an email contains an attachment, the attachment is not received on mobile devices.

Fix Pack 12

This fix pack includes the following fix:

  1. Deprecation of Dynamics 365 Regional Discovery service
Fix Pack 13

This fix pack includes the following fixes:

  1. Code Fix: When you attempt to deploy a workflow, an error occurs.
  2. Code Fix: Unable to copy and paste text in a Rich Text control that already contains text.
Fix Pack 14

This fix pack includes the following fixes:

  1. Code Fix: The Workflow SmartObject step with the “Wait for external system” option does not work.
  2. Code Fix: Exchange Administration Enable Mailbox error since Exchange April 2021 is installed.
  3. Code Fix: An error is displayed in Viewflow on an incorrect activity.
  4. Code Fix: An error occurs when you deploy a K2 package that contains a K2 Studio workflow.
Fix Pack 15

This fix pack includes the following fix:

  1. Code Fix: The K2 Server stops intermittently.
Fix Pack 16

This fix pack includes the following fixes:

  1. Code Fix: The onChange event of a Calendar control is executed incorrectly.
  2. Code Fix: Unable to adjust column width after Chrome browser update to version 91.
  3. Code Fix: When you double click to add a user to a role, the label is not added.
Fix Pack 17

This fix pack includes the following fixes:

  1. Code Fix: The incorrect decision step name is referenced in K2 Workflow error logs.
  2. Code Fix: Transferring 195 or more values/items to the Picker control results in an error.
Fix Pack 18

This fix pack includes the following fixes:

  1. Code Fix: The + and – node icons for the tree control data source configuration popup are missing.
  2. Code Fix: Worklist item link in a user task notification is missing a custom form parameter.
  3. Code Fix: When user attempt to submit forms in K2 Management, an error occurs.
Fix Pack 19

This fix pack includes the following fixes:

  1. Code Fix: K2 Workflow does not go into error state when required SmartObject property is empty.
Fix Pack 20
Labels: (1)
Version history
Last update:
‎08-19-2021 04:42 AM
Updated by: