This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
When creating a custom SharePoint integrated workflow that is stored in a nested folder structure, the full workflow name does not display when deploying the package to a different environment using Microsoft Management Console (MMC).
If the Workflow is stored as “AutomationProcess\Workflows\Inbound Transactions”, when deployed the name displays as “AutomationProcess\Workflows”.
- Ensure you have K2 4.7 installed.
- Download and install the K2 4.7 May 2017 Cumulative Update from K2 Partner and Customer Portal.
- Get the K2 4.7 May 2017 Cumulative Update FP1 from Regional Support.
- Install the K2 4.7 May 2017 Cumulative Update FP1 to apply the fix.