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.
Rollback Instructions
You can also restore the K2 database before re-installing K2. When you re-install, you can just point to the restored K2 database.
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:
Fix Pack 2
This fix pack includes the following fixes:
Fix Pack 3
This fix pack includes the following fixes:
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:
Fix Pack 5
This fix pack includes the following fixes:
Fix Pack 6
This fix pack includes the following fixes:
Fix Pack 7
This fix pack includes the following fix:
Fix Pack 8
This fix pack includes the following fix:
Fix Pack 9
This fix pack includes the following fix:
Fix Pack 10
This fix pack includes the following fixes:
Fix Pack 11
This fix pack includes the following fix:
Fix Pack 12
This fix pack includes the following fix:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fix:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fixes:
This fix pack includes the following fix: