Moving objects

Purpose of moving objects

Moving objects to another Folder

What happens when you move an object

Moving Rule versions (AccountingIntegrator only)

Purpose

For purposes of organization, you may need to move an object from one Folder to another. However, Composer objects exist in an interlinked hierarchy of object dependencies. To maintain coherence in the hierarchy of object dependencies, objects that reference each other must be stored in the same Folder, or in Folders that belong to the same root Folder.

Restrictions

The following restrictions apply:

• You cannot move objects from one Composer Entity to another.
• You cannot move objects to or from PrebuiltFolders.
• When you move objects to another Folder, Composer also moves all referenced objects if the target Folder does not belong to the same root Folder, as described below.
• You cannot move objects that have the status Archived, ToBeCommitted or Committed.

Moving objects to another Folder

Before moving objects

You can move one or more objects from a WorkFolder in the Entity Browser to:

• A parent, child or sibling Folder of the current Folder
• A root WorkFolder

How to move a single object

To move an object to a different Folder:

1. Click to open the Entity Browser.
2. Select the object in the right pane of the Entity Browser.
3. Drag-and-drop the object to the target Folder on the Folder tab in the Entity Browser.

How to move multiple objects

To move multiple objects from one Folder to another:

1. Click the Shift button and select adjacent objects or click <Ctrl> and select non-adjacent objects in the right pane of the Entity Browser.
2. Right-click one of the selected objects and drag-and-drop the selected objects to the target Folder.

What happens when you move an object

The results of moving an object vary depending on whether the target Folder belongs to the same root Folder or not.

Moving an object in the same root Folder

If you move an object to a Folder that belongs to the same root Folder, the object can still reference its associated parent and child objects since all objects are stored under the same root. In this case, Composer only moves the selected object, as shown in the following diagram.

Moving an object to a different root Folder

References between objects cannot exist between objects that belong to different root Folders.

So, if you move an object to a Folder that belongs to a different root Folder, Composer moves:

• The selected object
• All its associated child objects, on condition that these objects are not used by an object that does not belong to the tree of objects that you are moving

To see which objects are linked to a given object, use the Object Dependencies Browser.

In some cases, the tree of objects associated with the selected object can be extremely large. However, there is no limit to the number of objects moved with the selected object during the move operation.

Resolving naming conflicts

If you move an object to a Folder that already contains an object of the same type with the same name, Composer checks that both objects are identical - with the same properties and dependencies.

If the objects are:

• The same, Composer replaces the moved object with the existing object.
• Not the same, Composer renames the moved object by adding the suffix _copy to the original name.

AccountingIntegrator: Moving Rule versions

When you create versions of an object, you must create them all in the same WorkFolder as the original object. This is because all versions of a given object must be linked to the same parent object. If you move one version of a Rule, Composer also moves all other versions of the same Rule. If it cannot move one of the Rule versions, the operation is aborted.

If you move a Rule version from one root Folder to another, and if other Rule versions already exist in the target root Folder (and its sub-Folders), the operation is interrupted if the existing Rule versions are not located in the target Folder itself.

When you move a Rule version, Composer automatically attaches this object to the set of Input-Events and Processing-Context-Out objects in the target root Folder that already reference this Rule. If any Input-Event or Processing-Context-Out is non-modifiable, Composer modifies the name of the moved object and adds the suffix _copy to the original name. In this way, the operation does not involve updating the Input-Events or Processing-Context-Out objects.