What's New in K2 Cloud Update 7 Fix Pack 1

The following bugs have been fixed in this Fix Pack:

  • After upgrading to K2 Cloud, various workflow errors occurred including "Missing reference at EnvironmentField 'From Address...'". If this error occurs on an existing workflow, it is advised to remove and re-add all customization such as references after applying the fix pack. In addition, if your workflow contains a Task Notification or a Send Email step, then the following steps are required:
    • Task Notification:
      1. Copy the content in the Body.
      2. Deselect the Send email task notification check box.
      3. Reselect the Send email task notification check box.
      4. Paste the content of the Body.
      5. If you use Fields from the Context Browser, remove it and then re-add it.
      6. Deploy the workflow.
    • Send Email Step:
      1. Create a new Send Email step.
      2. Copy the content in the Body of the existing Send Email step.
      3. Paste the content in the Body of the new Send Email step.
      4. If you use Fields from the Context Browser, remove it and then re-add it.
      5. Delete the old Send Email step.
      6. Deploy the workflow.

  • An error occurs in runtime when the create reference step in a workflow attempts to loop through SharePoint list items that contain an ampersand (&).

  • Missing Item Reference in a workflow prevents deployment. An error stating "Missing reference at K2Process: ..." occurs.

  • Upgrading certain cloud environments to K2 Cloud Update 6 results in an error stating "The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_Identity_Identity_SyncEngine_ProviderInstance_ProviderInstanceID".

  • When you attempt to deploy a workflow from a SharePoint App where the SharePoint List or Library has a long name and the workflow has a long name, an error occurs. The error message states “The value cannot be more than 128 characters in length”.

  • Unable to deploy a package where the category name exceeds 200 characters.

  • In Management on service instances, when the "Generate SmartObjects" check box is used the SmartObjects tied to the service objects that no longer exist are not deleted.

    Opening a workflow that was deployed from a package containing a workflow that calls a SmartObject List method using an input parameter results in a missing SmartObject filter. Apply the fix pack then recreate the package.

Related Topics