Share this page

# Examples of baseline template rules

These examples are based on the following normal lifecycle for item type XYZ:

PRELIMINARY > DESIGNED > COMPLETED > TESTED > RELEASED

Suppose an item of type XYZ (OWNED by an included, non-suspended design part) exists in five revisions, none of which is currently checked out or suspended. The following table shows when each revision was last updated and to what lifecycle state it was then actioned:

Revision | Last updated | Current state
--- | --- | ---
1 | 1/1/2022 | TESTED
2 | 1/2/2022 | TESTED
3 | 1/4/2022 | COMPLETED
4 | 1/3/2022 | COMPLETED
5 | 1/5/2022 | PRELIMINARY

Then consider in turn each of the following alternative choices of template rule for item type XYZ.

If the template rule were as displayed, then for the above item, the revision to be selected, together with the reason for this selection, is as displayed alongside.

Lifecycle state | Code | Revision selected | Reason
--- | --- | --- | ---
DESIGNED | Latest from state (LFS) | 3 | 1, 2, 3 & 4 qualify; 3 is latest
DESIGNED | Most progressed state above specified state or specified state (MPS) | 2 | Latest at nearest-to-final state
DESIGNED | Specified state or most progressed state (SMP) | 2 | Latest at nearest-to-final state
DESIGNED | Specified state or next existing state upward (SUP) | 3 | Latest at next state up
DESIGNED | Specified state only (EQS) | None | None at DESIGNED state
PRELIMINARY | Most progressed state above specified state or specified state (MPS) | 2 | Nearest-to-final state preferred
PRELIMINARY | Specified state or most progressed state (SMP) | 5 | Specified state preferred
*All revisions (*ALL) |  | 1,2,3,4 & 5 | Includes everything
*Latest edit revision (*LATEST) |  | 5 | Latest of all at normal states
*Latest edit revision at final state in lifecycle (*FINAL) |  | None | None at final state
*Latest edited revision at the most progressed state (*HIGHEST) |  | 2 | Work back from final state; take latest at first state found
*Revision built from selected inputs (*BUILT) |  | ? | Cannot say; see following considerations
*Revision that makes selected outputs (*MADE OF) |  | ? | Cannot say; see following considerations

Guidelines:

1. "None" means that, if this were the template rule, then this item would not appear in the baseline.

2. The revision (if any) which would be selected by *BUILT cannot be determined from the information given. This is because if this is a built item, the revision selected would depend on the corresponding revisions of the input items used to build it, and those revisions would be selected by template rules for other item types.

3. The revision (if any) which would be selected by *MADE OF cannot be determined from the information given. This is because if this is an item selected because it is in a made-of list of some built item, the revision selected would depend on which revision of the built item was included, and that revision would be selected by a template rule for some other item type.

4. Revisions 1 or 4 could not be selected by any rule, except *ALL, and possibly *BUILT or *MADE OF, because in each case another revision, more recently updated, exists at the same lifecycle state.

Back to top

See also:

- Rule operation
- Rules using implicit states

https://admhelp.microfocus.com Dimensions CM 8942
Tips to improve your search results... Dimensions CM Help Center CM Help 14.7 All View Local Help Center View Online Help Center Version: