Map the Version of the Associated Workflow to the Parent Workflow

When you package a workflow containing a Workflow activity which is in turn associated to other workflows, you can change the configuration settings of the current workflow in the Associated Workflow Details grid that appears towards the lower section of the settings form.

In the Associated Workflow Details grid, you can specify the version of the associated workflow to which the current workflow should be mapped. In this grid, you can specify the version of the associated workflow to which the current workflow should be mapped in the target environment. However, the Associated Workflow Details grid will not be available in the configuration settings of the current workflow, if Workflow Activity expression editor is used to define the Workflow property.

You use the Associated Workflow Details grid to specify only the target version of the associated workflow to which the current workflow should be mapped. The configuration of the associated workflow is done separately from the package temple as it is added as an individual artifact.

The Associated Workflow Details grid contains the following fields:

• Workflow Name: Displays the name of the associated workflow.

• Source Version: Displays the source version of the associated workflow. You can use the same values for the target, or change the values as required.

• Target Version: Displays the target version of the associated workflow. You can use the same values as that in the source, or change the values as required.

  In case you do not edit the Target version field and retain the default value 'Latest', then the latest version of the associated workflow will be mapped to the current version in the target environment.

  If the Target version is left blank, then the source version of the associated workflow present in the target environment will mapped to the current workflow. If the source version is not present in the target environment, then the latest version of the associated workflow will be mapped to the current version in the target environment.

  If the Target version of the workflow is not present in the target environment, then the latest version of the associated workflow will be mapped to the current version in the target environment.

Scenario where duplicate messages are logged in history for an artifact

While installing or uninstalling a workflow containing a workflow activity, you might see duplicate log messages in history. This occurs if the workflow in the workflow activity is also a child workflow of the workflow being packaged.

In case of installation, the child workflow gets installed first and then the parent workflow is installed, and the following messages are logged in history:

• When the child workflow is installed, the following message is logged:

  Associated artifacts not present and installed as draft: <Name of the parent workflow>

• Later when the parent workflow is installed, the following message is logged:

  Workflow installed successfully.

  While uninstalling, the parent workflow gets uninstalled first and then the child workflow is uninstalled.

• When the parent workflow is uninstalled, the following message is logged:

  Workflow not uninstalled as child artifact(s) are present.

• Later after the child workflow is uninstalled, the parent workflow is again uninstalled and the following message is logged:

  Workflow uninstalled successfully.