The system checks the following Syntax Rules when a Move Elements rule is created and the page is saved. An error message displays if a syntax rule does not meet requirements and the rule is not saved:
syntax rule for move action |
example |
Source and Target OID Paths cannot be NULL |
- |
Cannot move a folder to a form |
Folder:Lab-> Folder:Lab/Form:Hematocrit |
Cannot move a parent folder under its own child |
[Subject]-> [Subject]Folder:Lab |
The last elements of both form objects must be identical when moving a form to a form. |
Folder:Labs/Form:Hematocrit-> Folder:Lab/Form:Hematocrit |
Each wildcard (*) used in the target path must match the wildcard used in the source path. |
Folder:Labs/Form:Hematocrit (*)-> Folder:Lab/Form:Hematocrit (*) |
Cannot use a global variable (defined as A-D in the drop down, appearing after a folder or form) in a move rule if the global variable does not exist in a Create rule to begin with. |
Folder:Labs/Form:Hematocrit (A)-> Folder:Lab/Form:Hematocrit (A) when (A) was not previously declared in a Create Elements rule. |
If the source uses a fully qualified path for the move action, then the target path must also be a fully qualified path. |
[Subject]/Folder:Labs/Form:Hematocrit -> [Subject]/Folder:Lab/Form:Hematocrit |
The following behavior holds true for a Move Elements rule:
Behavior |
Description |
Rule uses fully qualified path |
Indicates use of drop down selection of [Subject]. A fully qualified path specifies the exact location in the hierarchy to the [Subject] and recreates the same hierarchy from the source to the target. [Subject] indicates the subject level or the root of the hierarchical path. |
Rule uses relative path |
When [Subject] is not used, the system determines the full OID path in the source, up to the first element of the source path. When a match is found during migration in the target, the move from source to target is completed. |
Move occurs between folders whose last elements in the source and target are the same. |
The last element in the source is moved under the parent of the same element in the target. |
Move occurs between folders whose last elements in the source and target are different. |
The children of the last element declared in the source are moved under the last element declared in the target. |
OID Paths of matching elements with wildcard occurs in both source and target. For example, Lab(*) occurs in both source and target. |
When this occurs in a move action, the OID Paths of matching elements with wildcard are matched first, from the last element in the path up to the subject root. |
OID Paths without matching elements with wildcard occurs only in target. For example, Lab(*) occurs only in target. |
When this occurs in a move action, the OID Paths of unmatched elements with wildcard are matched last, from the last element in the path up to the subject root. |
Move action occurs Only if Target Parent Exists |
When selected, if the system cannot find the parent,the system ignores the rule and no error displays. |
Move action occurs when Target Parent does not exist |
When the system cannot find the parent, it creates the object. |
Move action creates an object |
The repeat number only displays when a wildcard is used. This implies that the user has more than one object and wants to see the repeat number. |
The rule is set to move a form to another form. |
When this occurs, there is a change of parent folder. |
The rule is set to move a form to a folder. |
When this occurs, there is a change of parent folder |
The rule is set to move a folder to another folder. |
When this occurs and the last elements of both folders are the same, then there is a change of the parent. |
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.