Company rule
Rule types – Abstract
Purpose: Is considered 'passed' if the Company of session is included in the whitelist defined by the parameters Companies and or any child company (all levels).
A Company rule is considered 'passed' if the company account (see Company accounts) in the current login context belongs to the companies that the rule configuration specifies via the static parameters Companies and or any child company (all levels).
If no Companies are specified in the configuration, then the Company rule is always considered as 'failed'.
Configuration
The Company rule refers to the Company of session, which is primarily defined by the session, but can be temporarily changed in the context of event handling by the Run as event action (see also Session based).
The reference object in the execution context is irrelevant for this rule.
The configuration of the Company rule provides a static multiple selection via a Multiselect combobox with a search function in the Companies parameter, which offers all Company accounts with at least read access in the context of the configuration for selection. If no Companies are selected, the rule is always considered as 'failed'. ►NOTE◄ If read access is missing for a company that has already been selected, then a label ('Hidden company') appears for this company that has been neutralized except for the internal ID. As long as such an entry is not specifically removed, it will remain in the list even if other entries are added or removed. 'Hidden' entries deselected by 'inversing' an existing selection do not reappear in the selection by 'inversing' again. |
|
The option or any child company (all levels), which is deselected by default, expands the selection of company accounts accepted by the rule to include all child companies of the explicitly selected companies. Child companies are all companies that belong to the hierarchy below a company and refer to it directly or indirectly as a 'parent company'. ►NOTE◄ The option cannot be selectively applied to specific Companies. Instead, however, two instances of the Company rule can be linked by an OR junction to select companies 'with and without child companies', if required. |
|
Example
An association criterion is 'passed' if the current session takes place in the context of a company that either belongs to one of the company groups 'EMEA' or 'APAC' defined in the company hierarchy as child companies (see Companies as groups) or is included in a list of companies defined directly in the association criterion.
Configuration:
To satisfy the explicit and implicit requirements (above), the association criterion is configured using multiple instances of the Company rule as shown on the right:
|
|
►NOTE◄ Since the groups 'APAC' and 'EMEA' can each conceal an extensive multi-level company hierarchy, it would be advantageous – at least theoretically – with regard to the performance of the evaluation of this association criterion, which may be necessary to check the more specific selection (above: right) with priority, so that the more time-consuming evaluation of entire hierarchies (above: left) is not necessary in the case of any direct match. Simply swapping the pages within the OR junction, which is achieved by cut and paste in a few clicks starting from the above configuration, ensures this 'runtime optimization' for the check logic. Due to the same reasoning, shown in the example on the right, the order within the AND junction has also been swapped, so that the evaluation of the child companies is also omitted within a session with a group company account. |
|