Workflows and Automation

  Error Encountered: Error during K2 5.6 migration to a new machine, keeping the SQL server unchanged. Error message:                       20:49:59:>> Certificates.FindCertificate: Found 1 certificates                       20:49:59:>> RegisterShard.Execute: Adding additonal connection string parameters to config service shard                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional connection string parameter value: empty                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional ConnectionString Parameters is empty                       20:50:04:>> AnalyzableAction.PopulateValidate...

This guide outlines the steps to using the Client Credentials Flow for accessing Nintex K2 Cloud's OData, Workflow REST, or SCIM APIs. Before you begin: Ensure your environment is eligible for Client Credentials Flow by contacting Nintex support ( https://customer.nintex.com/cases/Pages/default.aspx ). Have a SHA256 hash of the client secret of your choosing ready. Steps: Onboarding: Open a support ticket with Nintex requesting the onboarding of the Client Credentials Flow for your environment. Provide the SHA256 hash of your the client secret. https://help.nintex.com/en-US/k2cloud/userguide/current/Content/IdProviders/ClientCredentials.htm You can Generate the secret hash from a Client Secret value in a .NET console application. The onboarding team does not need the actual secret value, only the hash of it. Use the following steps and code example to generate the hash: Add the  IdentityModel  NuGet package. Add the  IdentityModel  library reference in the ...

Even though the K2 server and database were migrated, it was still trying to connect to the old SQL server, but on port 1434. While data was being written to the correctly migrate K2 database on port 1433, this unnecessary connection on 1434 needed to be addressed. The culprit was an outdated entry in the Configuration.Shard table referencing the old SQL instance. Here's how to fix it: 1. Identify the correct EnvironmentID: o Run the provided SQL query to decrypt the Configuration.Shard entries to identify the correct/incorrect row. Replace the ConfigShardIDValue with the EnvironmentID from the SELECT query to decrypt the Value for each row. SELECT * FROM [Configuration].[Shard] BEGIN EXEC [Utility].[EncryptionBegin] @KeyGUID = NULL; BEGIN TRY SELECT [EnvironmentID], (SELECT CONVERT(NVARCHAR(MAX), [Utility].[DecryptData] (CONVERT(VARBINARY(MAX), [Value], 1)))) AS [Value] FROM [Configuration].[Shard] WHERE [EnvironmentID] = ' ConfigShardIDValue ' EXEC [Utility].[Encryp...