To update an existing workflow definition in a scenario
with a different version of the same workflow definition, use the
Replace procedure described in this topic. The name of the workflow
must be the same as the existing one in the scenario.
To replace a workflow definition with a different version
of the same workflow definition:
- From the Simulation Designer Tools menu, select Replace Workflow.
- Locate the workflow definition to replace the existing
one in the scenario. The workflow definition can be stored in any
location.
- If you have defined initial values for the data fields
(Arrivals tab), you can clear them and replace
them with any values specified in the incoming workflow definition
by selecting the
Replace the initial data field values from the imported
workflow check box. Otherwise, to retain the initial field
values defined on the Arrivals tab, clear the check box.
Note the following results of replacing an existing workflow definition
in a scenario:
- The replacement keeps any arrival, shift, and other resource settings
in the scenario.
- If there are new resources in the incoming workflow definition,
they are added to the resources list; resources that were in the original
version but not in the update version are retained.
- If the incoming workflow definition contains new steps, you must
specify the properties of those steps. If steps are deleted, that
information is removed from the scenario.
- If initial values have been defined for data fields, you can clear
all the values specified on the Arrivals page by selecting the Replace the initial data field values from the imported workflow check box. If you clear them, Simulation Designer replaces them
with the field names and any initial values from the imported workflow.
Otherwise, if you do not clear the fields and values defined on the
Arrivals page, Simulation Designer compares the data fields from the
incoming workflow definition with the data fields on the Arrivals
page and update the data fields table as follows:
- If the field exists in the incoming workflow definition but not
in the current list of fields, the field is added.
- If the field exists in the current list of fields, but not in
the incoming workflow definition, the field is removed.
- If the field exists in both the incoming workflow definition and
in the current list of fields, and the fields are the same type, keep
the value that is defined in the current list.
- If the field exists in both the incoming workflow definition and
in the current list of fields, but they are not the same type, use
the type and initial value, if any, from the incoming workflow definition.