Copying, Pasting and Moving in Magic xpi (Magic xpi 4.9)
You can copy, paste and move steps and branches either within a flow or between different flows in your integration project. When you do this, the step or branch automatically retains its assigned flow variables. You can also copy and paste flows and business processes, as well as pasting steps and branches into flows that are part of other business processes.
-
To copy and paste items between flows, use the context menu options.
-
To copy a branch, right-click on the step that appears at the beginning of the branch.
-
To move steps and branches within a flow, you can either drag the items or cut and paste them using the context menu.
-
To copy and paste multiple steps between flows, first select the steps using Ctrl key and then use the context menu options. (Since version: 4.7)
-
When you copy a step with a variable that does not exist in the target flow, the variable will be created when you paste the step.
-
If you copy a step with similar variables in the target flow, the Duplicate Variables dialog box opens. Here, you need to set one of the following options:
-
-
Use Existing: If you select this option, which is unchecked by default, there is no change in the target variable name and its default value. When you select this option, the Create As column becomes read-only, and any value that was previously there is deleted.
-
Create As: If you select this option, a new variable is created in the target repository. The value set in this column is a variable name. Therefore, any values appearing there will automatically receive a prefix of F. (for flow variables) or B. (for business process variables). The newly created variable in the Create As column must be unique for that particular flow or business process repository.
-
When copying variables with same name but of different types, the Use Existing option will be disabled in the Duplicate Variables dialog box for that variable.
-
When you copy and paste steps, the flow variables that are used in database SQL statements and WHERE clauses are not automatically created. You should make sure that you check SQL statements after pasting a step or a flow. Note that SQL is not parsed, but treated as a string and not as an expression; therefore, errors for these type of unhandled cases will only be issued during runtime. Warning message alerts or Checker/Builder errors will not be issued.
-
Pasting a branch that includes a GoTo command that points to another branch (and not to itself) is valid only within that flow, and only to branches that share a mutual linear parent.
-
When moving a branch, GoTo steps that point to a location that does not share a linear parent with the moved-to location will be lost.
-
When copying a step to any place in another flow, the condition will always be copied. However, copying a Root step with a condition to any other place other than to the root will not copy the condition. A condition on a root node is actually a condition on the flow, after the triggers (if defined) are executed. Therefore, pasting a root node does not paste the condition.
-
Copying a step as Root will change the Parallel setting to Linear, if such a setting was defined.
-
The Save Point and Wait for Completion definitions cannot be copied to another step.
-
The Processing Mode definition is copied when copying the first step, unless it is pasted as a Root step.
-
The Logic Flow definition will be set to No in the target flow. This is because it is a flow definition and not a step definition.
-
Copying a Data Mapper step will also copy its Error Flow definition.
-
Paste operations can be undone. For more information, see Undo Actions over Flow Components. (Since version: 4.7)
