# What are ClearTrigger ~Aliases?

**URL:** <https://community.abs-consulting.com/t/what-are-cleartrigger-aliases/35>\
**Category:** ClearTrigger\
**Created:** [November 8, 2021, 5:39pm UTC](https://community.abs-consulting.com/t/what-are-cleartrigger-aliases/35 "2021-11-08T17:39:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![robert](https://community.abs-consulting.com/user_avatar/community.abs-consulting.com/robert/32/28_2.png) [@robert](https://community.abs-consulting.com/u/robert)\
**Post date:** [November 8, 2021, 5:39pm UTC](https://community.abs-consulting.com/t/what-are-cleartrigger-aliases/35/1 "2021-11-08T17:39:28Z")

</div>

# ClearTrigger ~Aliases

Many portions of the license file can contain _aliases_. 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% or @times@ or any combination of each of the types.

Additionally, aliases can be used to “group” types as in brtype lbtype. An alias “grouping” might consist of **(users)** , **\<groups\>** , **{elements}** , **[VOBs]** , **[VOB:replicas]** , **%views%** or **@times@** as found in:

- MOTD Restriction List
- Region Inhibited List
- Region Special Access List
- Comand Key Allow List
- Command Key Disallow List
- Comand Key Trigger Not User List
- Command Key Trigger Only User List

or they may be a **type item** as found in **RIN List** :

- Restriction List
- Inclusion List
- Negation List

You may define up to **40** aliases in the ClearTrigger Region such that:

- Alias names may contain up to **50 characters** from [a..z,A..Z,0..9,\_]
- Alias values may contain up to **256 characters** not to include ‘,’ or ‘;’
- Alias values may contain other aliases (so a hierarchy can be built) up to **5 levels deep**
- Alias must fit under **2048 characters** when fully expanded
- Alias definitions are only valid **before the license key** in the clearbits file. All other alias definitions after the license key are treated as comments.

Alias definitions are “hidden” in the upper portion (above the license) of the clearbits file and are of this form:  
**#!cleartrigger\_alias {alias\_name} {alias\_value}**

**Dynamic Variables** and **Patterns** may be used in the alias value as well and are evaluated at run\_time. There are examples below:

**Example (each on single line)**  
#!cleartrigger\_alias **good\_users** (&) (cclarke) (slewand) (rcarter)  
#!cleartrigger\_alias **dev\_vobs** [_cell] [proj\_##\_?]  
#!cleartrigger\_alias **mgt\_access** [mgt] {/corp/_}   
#!cleartrigger\_alias **limit\_types** brtype lbtype\<REL#.#\*\>  
#!cleartrigger\_alias **corp** ~good\_users ~dev\_vobs ~mgt\_access

Once defined in the clearbits file that alias can be used instead of the “grouping” in Region fields and command keys. Refer to an alias as **~alias** when you want ClearTrigger to expand the alias at runtime. There are examples below:

**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;

**NOTES:**

- The ~alias **must** have a trailing ’ ’ character after it when referenced
- Alias references are expanded before error message are build so “real” user, groups, VOBs etc. are display (not the ~alias name)