Many portions of the license file can optionally contain one or more ClearTrigger aliases or name:value substitution pairs.
These aliases are useful when you want to group several objects together by a single name so that they can name can be used to represent that grouping throughout the clearbits file. This is useful for creating fictitious "groupings" (the term "grouping" instead of "group" is used because ClearTrigger aliases can be used to group not just (users) into groups but also to "group" numbers of <groups>, {elements}, [VOBs], [VOB:replicas], %views%, @times@, 'clearcase regions^ or ^^ or any combination of each of the types. Additionally, this section can contain a pattern match for the current environmental variable ABS_TRIGGER_POLICY (i.e. ^development_phase^ or ^urgent_delivery^). Aliases can be used to "group" types as in brtype<integration> lbtype<main>. An alias "grouping" might consist of (users), <groups>, {elements}, [VOBs], [VOB:replicas], %views%, @times@, 'regions' or ^env variable matches^ as found in:Example (each on single line) |
---|
#!cleartrigger_alias good_users (&) (cclarke) (slewand) (rcarter) |
#!cleartrigger_alias dev_vobs [*cell] [*proj_##_?] |
#!cleartrigger_alias mgt_access [*mgt*] {*/corp/*} <mgt> |
#!cleartrigger_alias limit_types brtype<main> lbtype<REL#.#*> |
#!cleartrigger_alias corp ~good_users ~dev_vobs ~mgt_access |
Example |
---|
; vobadm ~good_users <*adm> ; |
; jgardner ~bad_users ~interns ; |
pre_MODIFY_ELEM;R; ;0;0;0;D;~students ;N; ~admins ;0;tag.pl; |
pre_MODIFY_ELEM;R; ~limit_types ;x;10; |