Example Rule: Component Rules - Butt Welded Piping Cap
- Last UpdatedNov 22, 2022
- 2 minute read
To illustrate the use of line list configuration rules, the following example will show how to conditionally populate the LLFROM and LLTO pseudo attributes with a substitution text string, which is applied based on a check of the component type at the termination of a pipeline.
The setup of the rule is displayed in the Rule Properties section of the dialog:
Each of the rule properties is explained below.
|
Rule Property |
Value |
Meaning |
|---|---|---|
|
Attribute |
LLFrom and LLTo |
The pseudo attributes this rule will populate. |
|
End Condition |
Valid HREF/TREF |
Determines when this rule is applied - either when a branch is correctly terminated (as in this case), or when it is not correctly terminated, or always. |
|
Item Types |
DbElementType[]Array |
The database element type that this rule applies to. |
|
Name |
Butt Welded Piping Cap |
The name of this rule. |
|
PML Expression |
'But Welded Piping Cap' |
A PML expression used to derive the value which will be used to populate LLFRON/LLTO. In this example it is a simple text string describing the type of element which terminates a pipeline. |
|
PML Expression Object |
EndComponent |
The element used to derive LLFROM/LLTO - either the terminating SCBRANCH or, as in this case, the first/last component. |
|
Rule Filters |
-- |
Multiple filters can be added - in this example one filter is present which limits the applicability of this rule to pipe terminations which have a component class value of PipingCap. |
Once configured, the line list related pseudo attributes will be populated each time they are queried.