...
The imported workflow now appears in the Process Workflow workspace.
Upon |
While importing a workflow, |
all the related entities such as custom attributes used in the matching condition, set fields, associated communication templates, web services, and permissions are also imported- All dependencies such as users, organizations, categorizations, value lists, custom attributes, task catalogs, task groups, task flows, etc. should be available in the destination environment.
- Only custom attribute or custom attribute templates are created if these do not exist in the target.
- In case an HT attribute does not exist in the destination, an attribute is created but values are not created. Matching criteria or the assignment rules based on HT attribute would be created with empty values.
- In case the HT attribute exists in the destination but the data is not the same as the source - rules based on values available in the destination environment are created. Rules, based on values that are not available in the destination, would be created with empty values.
- For List, Radio type of attributes, if the attribute exists in the destination but values are not the same, matching criteria/assignment rules would be created but the value part would be blank. When the value is created in the destination, the matching criteria/assignment rule should work as expected.
|