Design Templates
User Guide
Modify
: Order Local Names
Order Local Names
When the rules within a Design Template definition are executed (for example, when a design instance is copied into the 3D model), the rules for the member elements are evaluated, by default, in descending hierarchic order.
If the rules for one element involve the current attributes of another element, the order in which the rules are executed becomes significant and the default sequence may not give the intended result. For example, if the positions of elements /A and /B are both defined by rules, and if the position of /A is defined relative to that of /B, then the rule for positioning /A only gives the correct result if the rule for /B has already been executed.
The user can control the order in which the rules for a given Design Template are executed by assigning a rule sequence to an element that contains a local name. Refer to
Assign Local Name to Template Element
for further information.
Design Template rules are executed in order of sequence, rules for elements not included in the sequence is then be executed in the default sequence.
To define the sequence in which the rules for Design Template members are to be executed, make sure the correct Design Template is highlighted in the Template Browser.
On the
Design Templates
tab, in the
Modify
group, click
Order Local Names
to display the
Local Name Rule Sequence
window.
The name of the currently selected template displays at the top of the
Local Name Rule Sequence
window.
The user can define the rule sequence by defining the order of the list of Local Names.
Moves the currently selected local name to the top of the Local Names list.
Moves the currently selected local name up one place in the Local Names list.
Moves the currently selected local name down one place in the Local Names list.
Moves the currently selected local name to the bottom of the Local Names list.
Click
OK
to apply the rule sequence or
Cancel
to discard any inputs and close the
Local Name Rule Sequence
window.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.