configure the user interface as follows :
configure the user interface as follows statement incorporates clauses that fall into four distinct categories:
configure the user interface as follows statement must include at least one user modes clause. This clause names one or more user modes under which the configuration does or does not apply. Use the
when in phrase to list the user modes that apply to a set of configuration clauses. Use the unless in phrase in a user modes clause to list the user modes that do not apply to a set of configuration clauses. For example:
configure the user interface as follows :
when in developer or end-user mode : { INCLUSIVE }
... ;
unless in administrator, developer, or end-user mode : { EXCLUSIVE }
...
or reserved word. When specifying three or more modes, separate the identifiers with commas, and include the reserved word or before the last identifier.
configure the user interface as follows statement that applies only under administrator mode. You can specify configurations that apply when not in administrator mode. This prevents you from unintentionally restricting access to a portion of your own KB.
Specifying Appropriate Operations for the Target Class
If a clause in a configure the user interface as follows statement refers to a menu choice, attribute, or low-level G2 operation that is not appropriate for the class of the target item, G2 ignores that reference in the configuration clause.
configure the user interface as follows :
unless in developer mode :
menu choices for rule or custom-object exclude :
hide
RULE class in the menu choices for rule exclude clause, because hide is not one of the system-defined menu choices for the RULE class. However, G2 does not ignore the entire clause, because hide could be a user-menu-choice for the user-defined CUSTOM-OBJECT class.