Known Issue: Using environment fields in a workflow and switching between environment libraries

Issue

When you have a workflow containing an environment field with a specific value, the environment field is used in more than one environment library, and you then select another environment library containing the workflow and environment field with a different value for the field, the incorrect environment value is used in the workflow.

Cause

When you deploy the workflow, it builds a reference to the default library field value. If you select another environment library as the default, the workflow reference is out of sync and uses the previously built reference.

Resolution

Using environment fields in a workflow and switching between environment libraries containing the same environment fields:

• If you switch between environment libraries on the same environment, you must change the environment fields in the workflow to use those of the new environment library and then redeploy the workflow. This is required because the workflow builds a reference to the current default library field value when you deploy the workflow. Failing to do so will cause errors when you try to use the workflow in the new library.
• If you use K2 Package and Deployment to deploy the solution to another environment, the workflow does not exist in the new environment and you want to use another library in the new environment, you must edit and redeploy the workflow on the new environment to enable the rebuild of references to the newest default values.
• If you use K2 Package and Deployment to deploy the solution to another environment, the workflow already exists in the new environment, and you want to use another library in the new environment, you must edit and redeploy the workflow on the new environment to enable the rebuild of references to the newest default values.