What's New in K2 Update 18

New Features

the Designer

Style Profile Designer Developer tab: A Developer tab is now available that allows you to use custom external resources such as Cascading Style Sheets (CSS) and JavaScript (JS) in your style profiles. This allows you to include modern capabilities, extend the look and feel of your style profile, and optimize web page behavior.

Management

AssureSign Broker: Nintex K2 Cloud Update 18 integrates with Nintex AssureSign through SmartObjects. Create an AssureSign service instance and SmartObjects to send documents for esigning.
Authorization Framework: The Authorization Framework has been enhanced to include authorization for SmartObject Service Types and Service Instances. This provides extra security to SmartObjects and increased control around the management of Service Types and Service Instances. A new Service Instances Security node has been added to the Integration node of Management. See Authorization Framework Overview, Service Instances Security, Service Types, and Service Instances for more information.

Enhancements

Workflow
- When you configure a Call Sub Workflow step in a workflow and manually type the name for a sub workflow that has not been created yet, the Folio and variables of the sub workflow are now automatically created for use in the main workflow. This allows you to complete the configuration of the Call Sub Workflow step before creating the sub workflow. Tab or click outside the Which workflow? field to show the Folio and variables.
K2 DocuSign Integration
- DocuSign has announced a change for authentication techniques by deprecating legacy authentication and OAuth 1.0 protocols. Since August 2021, any new API applications integrating with DocuSign must use the OAuth 2.0 authentication flow. By October 4, 2022, all existing DocuSign customers and partners integrating with DocuSign must be updated to use OAuth 2.0, including applications already in production. For more information on the changes, see DocuSign’s blog at https://www.docusign.com/blog/developers/october-2022-oauth2-required. In Nintex K2 Cloud Update 18 we updated our integration to the OAuth 2.0 standard. If you use the K2 Integrator Key, you will need to configure your own personal Integrator Key for enhanced security. The steps are documented in the DocuSign topic, and the DocuSign Go-Live steps are at https://developers.docusign.com/docs/esign-rest-api/go-live/. There are two known issues related to the DocuSign integration. See the Known Issues section below for details.

Behavioral Changes

Authorization Framework: Service Type and Service Instance Security
- You no longer need workflow Server Admin permissions to access Management to manage Service Types and Services Instances. Prior to Nintex K2 Cloud Update 18, you needed workflow Server Admin permissions to access Management before you could create or manage a Service Instance of a Service Type. With Nintex K2 Cloud Update 18 you only need Create and View rights to the specific Service Type in Management allowing you to create and manage the Service Instance.
- All rights now apply to all underlying SDK libraries and user interfaces providing enhanced security that is consistent across the entire platform.
- With Nintex K2 Cloud Update 18, all workflow Server Admin users are granted the Allow permission to all rights on the root Service Instances Security level, and the Everyone role is granted the View right at the Service Instances Security level. This is to allow Admin users to manage all Service Instances and Service Types until a more granular setup is implemented, and to allow all users with access to the Designer the ability to still view and use all Service Instances in their SmartObjects.
- If you add a user as a workflow Server Admin with Nintex K2 Cloud Update 18, the user does not have rights to manage Service Types and Service Instances. These rights must be granted in the Service Instances Security, Service Types, or Service Instances nodes.
- You need at least Create, Modify, Delete, or Security rights on at least one Service Instance or Service Type to access Management and manage Service Types and Service Instances, and View rights to see the object in Management and the Designer.
- The changes to rights and permissions also apply when using the SmartObject Tester tool.

Deprecated functionality and components

Microsoft has ended support for Silverlight on October 12, 2021. As a result the K2 legacy Silverlight designer will be removed from Nintex K2 Cloud with the next release. Ensure you rebuild these in the Workflow Designer (HTML).

Considerations

The Style Profile Designer is not available in Internet Explorer (IE), as it uses CSS custom properties (CSS variables) which is not compatible with Internet Explorer. We suggest you use a modern browser for the Designer, such as Google Chrome.
Download the enhanced Package and Deployment tool from https://<runtimeurl>/Management/Remote. Once downloaded, log a ticket with Nintex Customer Central to provide your public IP address ranges to K2 Operations. This allows access to your K2 Cloud environment from your network. Please see the Package and Deployment Considerations topic for further considerations about working with the Package and Deployment tool.
If you are using K2 for SharePoint, you must run through the K2 for SharePoint registration wizard after upgrade. See the following steps:
1. Click the K2 for SharePoint app from the Site Contents page or Quick Launch menu of the app catalog site and run through the Registration Wizard by clicking the Registration Wizard link in the Administration section to register the app with your K2 environment's URL. (If you do not see the Registration wizard, make sure you are on the app catalog).
2. (This step is only required if there were changes to the K2 for SharePoint app. See the K2 for SharePoint release notes for information about previous releases and the latest version.)
  Deploy the app to one or more site collections using the Manage App Deployments page in SharePoint. A link to this page is provided on the K2 for SharePoint settings page. It is recommended you do this by paths rather than individual URLs, but individual URLs give you more control regarding which site collections have K2 integration. You should deploy as a SharePoint Administrator if you are deploying to multiple site collections.

Known Issues

Issue: When editing an existing OAuth/Static DocuSign Feature Instance via Management and entering an incorrect UserID, the instance will be updated but will present an error when an execution is attempted to DocuSign which requires the UserID.
Error message states:
Error: SmartObject Server Exception: {"error":"invalid_request"}.
When attempting to create a new OAuth DocuSign Feature Instance using an incorrect UserID the same error will be presented on the DocuSign Service Broker configuration Step.
Issue: When you create a new OAuth DocuSign Feature Instance and the OAuth section details (ClientID, UserID, Authentication Service Url, Scope, RSA Private key) are all correct but REST API URL or the AccountID is incorrect, clicking OK will take you to the Feature Instance configuration screen and fail with a validation message stating that the REST API URL or the AccountID are incorrect.
Issue: When you correct the REST API URL or the AccountID value but you add the incorrect values for OAuth section and click OK, the Feature Instance configuration will succeed as the token for your OAuth DocuSign Feature Instance has already been created. Only when the token expires or is deleted will the validation for OAuth section activate again. When you edit an existing OAuth DocuSign Feature Instance where the token has not expired yet, you will also be able to add the incorrect values into the OAuth section and validation will not appear.

Bug Fixes

Each release includes all bug fixes from preceding releases; see the release notes for previous releases for more details on bug fixes in previous versions. K2 Cloud includes the following additional bug fixes:

All bug fixes in K2 Cloud Update 17 Fix Packs 1-13.
When using K2 for SharePoint and trying to upload a document (image) with Image Tags, a "The requested item 'MediaServiceImageTags' cannot be found in the collection" error occurred. Follow the steps below to successfully apply the fix:
1. In Management > Integration > Service Instances, select your service instance and click Edit.
2. Copy and paste the following XML into the Excluded Fields field in the Setting section. Click OK.
  Copy
```
1
<properties><property name="InternalName" value="MediaServiceImageTags"/><property name="InternalName" value="MediaServiceImageTags_Value"/></properties>
```
3. The service instance may take a couple of minutes to update. Click OK once it is complete.
4. Restart the K2 service.

Fix Packs

The following Fix Packs apply to this version of K2 Cloud. To determine the version and Fix Packs applied to your environment, please see the KB article KB003537: How to determine the installed K2 software version, Cumulative Updates, and Fix Packs for K2 Platform and K2 Cloud

Fix Pack	Release Date	Details
Fix Pack 14	March 2023	When a view containing a Slider control is hidden on a form and a rule is used to set the Slider control at runtime, the values for the control did not show. When using task notifications in a workflow, an error occurred stating the string is not in the required format for an email address. When using SmartActions, a "SecurityToken has Expired" error occurred intermittently.
Fix Pack 13	March 2023	When hovering over a category with a long name in the K2 Workflow Designer Toolbox, the tooltip did not display. When configuring an email reminder on a Task step, using the Infinite setting in the Repetitions field, and using a variable containing an empty value, caused reminders to be sent every second infinitely. Follow the steps below to successfully apply the fix: Delete the reminder by clicking the Trash bin. Click the Email Reminder link to recreate the reminder.
Fix Pack 12	February 2023	When using an external file to apply a style profile to a form, then opening a subview from the form, the style profile did not apply to the subview.
Fix Pack 11	February 2023	When configuring working hours in Management, selecting a Start Time or End Time between 12:00 AM and 12:59 AM, then adding the configuration and clicking Finish, the AM changed to PM.
Fix Pack 10	January 2023	When configuring a workflow Task Reminder and selecting the option Within working hours only, then navigating away from the tab, the setting did not save.
Fix Pack 9	January 2023	When transferring data into a Picker control on a form containing a style profile, characters containing a part below the baseline (tail) such as g and y did not resolve correctly as shown in the image below.
Fix Pack 8	January 2023	When opening Management, the nodes of the tree view took long to display. When adding or editing a Custom Workspace in Management, selecting the Menu tab, and trying to configure a workspace, the fields in the right-side menu were not enabled.
Fix Pack 7	December 2022	When trying to integrate DocuSign using OAuth authentication, an unsupported authentication error occurred. When Configuring the SmartObject OData API and changing the Record Limit under EndPoint Data Limits, a “false” message was shown and the value did not update. When trying to create an AssureSign service instance, a “VALIDATIONThe given key was not present in the dictionary” error occurred. When using a role or user in a variable as a Task Recipient, or using a role in a Send Email step, the following issues occurred: Tasks were not delivered to role members or users. When the Task’s “Resolve Groups to Individuals” option was checked, roles were not resolved to individuals and when clicking on the role in the Management Task List, the Role Members button was disabled. In the “Choose Recipient” list, when switching to “Type/Construct your own”, tasks were not delivered to users, roles, or groups. User roles were incorrectly available in the “Choose Recipient” list on the Task Email Reminder and Send Email Steps. Only users and groups must be available in this context. Follow the steps below to successfully apply the fix: If you used a role in a Task Email Reminder or Send Email Step, remove the role and use a user or group instead. Remove and re-add current Task Recipients (Users, roles, groups and variables). This is to ensure that the return types are now set correctly in the workflow JSON definition. Deploy your workflow. When trying to generate an OAuth Token and clicking on the link, a "Bad Request - Request Too Long" error occurred.
Fix Pack 6	December 2022	When adding or editing a filter in a SmartObject Smartfield in the workflow designer, the filter settings did not save.
Fix Pack 5	November 2022	.NET 6 background service change of behavior caused the K2 Configuration Service to stop. Rolled back the following fix due to issues experienced: When you use the standard AppOnly OAuth resource to authenticate the Exchange Web Services for K2 SmartActions, Task Notification Emails, and EmailEvent, an admin is required to give impersonation rights. A “The account does not have permission to impersonate the requested user” error occurred for users without admin rights. Please see the following link for more information on Integrating K2 with Exchange Online: Integrating K2 with Exchange Online using OAuth with lesser permissions.
Fix Pack 4	November 2022	When you select Start with a SharePoint List under the start event in the Workflow Designer and then select a SharePoint subsite, a 500 server error occurred. It is recommended to clear your browser cache to successfully apply the fix. When you select Start with a SharePoint List under the start event in the Workflow Designer and then select a SharePoint site collection, either the libraries, lists, or subsites displayed depending on which was returned last, rather than displaying all the sites. It is recommended to clear your browser cache to successfully apply the fix. When you upgrade to K2 Cloud Update 18 Fix Pack 3 and you try to open the Swagger URL or Base URL of the Workflow Rest API Preview version in Management, a “Server Error in '/Api/Workflow/Preview' Application” error occurred. When you use the standard AppOnly OAuth resource to authenticate the Exchange Web Services for K2 SmartActions, Task Notification Emails, and EmailEvent, an admin is required to give impersonation rights. A “The account does not have permission to impersonate the requested user” error occurred for users without admin rights. Please see the following link for more information on Integrating K2 with Exchange Online: Integrating K2 with Exchange Online using OAuth with lesser permissions.
Fix Pack 3	November 2022	When setting a user to Out of Office in Workspace, and searching for a user to forward tasks to, the search results returned values starting with the search term instead of containing the search term. When a form contains a Picker control with the Allow Multiple property checked and a value is specified for the Max Rows property, applying a style profile to the form displayed the selection only in the first row of the control display at runtime. When you use the ampersand '&' character in a search using the Picker control, the results were returned as '&' instead. When you have an item reference mapping between a workflow and a sub workflow, and starting an instance of the workflow, a “28042 IPC Failed to Start: 28006 Datafield ApplicationDetails_1 not found” error occurred when reaching the Call a Sub Workflow step. To successfully apply the fix, redeploy the workflow.
Fix Pack 2	October 2022	When using HTML in a Variable to set a parameter in a rule in the Designer, the HTML did not render correctly at runtime. When you uncheck the Visible property of a form, the form was still visible at runtime. Follow the steps below to successfully apply the fix: Restart the K2 service Refresh Internet Information Services(IIS) From your web browser, clear your browsing data using the All time option. Ensure to select all the options to clear all history and sites. If the form must be visible, check the Visible property. If the form must not be visible, uncheck the Visible property. After upgrading to K2 Cloud Update 18 and editing a resource from Management > Authentication > OAuth > Resources that previously contained RefreshTokenEndpoint and MetadataEndpoint values, those fields were empty. When using a SmartObject as the data source for the Auto-Complete control and configuring a rule to set a property of the control, values containing an apostrophe were returned incorrectly.
Fix Pack 1	October 2022	When creating a Custom Voting Rule on a Task step in a workflow and using any of the operators in the rule to set the number of responses, an ‘AtLeast’ function was applied to all operators selected. When replacing an existing Task step with a new Task step in a workflow, the Form rules of the existing SmartForm Task remained but it was showing the new Task’s name. Follow the steps below to successfully apply the fix: Edit the following file: [K2 install folder]/K2Designer/Web/K2DesignerHost/configs/environments/environment.config.json. Search for the following in the file: Copy `"activityNamingStategy": { "random": false },` Change the value false to true. Clear browser cache. When configuring an email reminder on a Task step and using the Infinite setting in the Repetitions field, the reminder was only sent once. Follow the steps below to successfully apply the fix: Delete the reminder by clicking the Trash bin. Click the Email Reminder link to recreate the reminder. When using a Table control on a view, and only certain rows contain a Check Box control, the rows that follow a Check Box control contained extra padding. When a workflow contains a Task step using a Text > Split function in the Task Notification, a “500 Server Error” error occurred when trying to edit the workflow.

What's New in K2 Cloud Update 18