Association criteria of type 'Logical component'

Checking the Logical component flag for an association criterion has the following effects:

• The association criterion is not (or no longer) evaluated individually in data context, but only if relevant as a sub criterion.

• The association criterion does not appear in the list of 'Matching criteria' of the function 'Data context', even if relevant as a sub criterion.

• The association criterion is not (or no longer) featured as a choice for Assign for objects, that as controlled by association criteria.

• Existing assignments of the association criterion to such objects are not removed, but are ineffective as long as the criterion is flagged as a logical component.

• The association criterion is not (or no longer) featured as a choice for behaviours of the Association criterion matched type in forms.

• Any existing selections for behaviours of the Association criterion matched type are not removed, but are ineffective as long as the criterion is flagged as a logical component.

Well-directed use of this option will improve transparency regarding assignments and prevent unnecessary computing time for data context.

►NOTE◄ If an existing association criterion should be handled as a logical component in the future, but is currently assigned to objects, these assignments should be removed for better clarity. The Usage function can be used to determine existing references:

In this example the Usage button lists two references to an association criterion (XFLOW_ORG) to be flagged as a logical component in the future.

• The first reference from another association criterion 'XFLOW_ADMIN' specifies 'XFLOW_ORG' as sub criterion and is non-critical as it will continue to be effective.

• The second reference is an assignment to portal 'XFLOW_ACFT' and should be removed, since it will cease to be effective for a logical component.