This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
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.
If variables are changed in a sub process, the "Call a Sub Workflow" step in the parent breaks. The variable becomes blank under the "Start Sub Workflow" section of the step and cannot be deleted:
The workflow will still deploy, however when an instance is started it will hang on the call sub workflow step.
A blank variable field in the "Start Sub Workflow" section of a sub workflow call step will appear and cannot be deleted. This will cause an error when the workflow is deployed and an instance hits the Call Sub Workflow step.
A fix is scheduled for this issue in K2 5.2. In the meantime, you can workaround this issue by recreating the step in the parent process