Assertion flags can be implemented in the Assertion Type Editor
or from the Policy Contract tab.
Refer to Working with the assertion type editor for information.
The following assertion flags are supported.
- Locked: If an assertion is locked, for a particular policy
target, it indicates that it cannot be further personalized at a lower Target
level.
- Visible: If an assertion is marked as visible, it indicates
that it will be shown during personalization time (regardless of whether the
user is allowed to change it or not.)
- Required: If an assertion is marked as required, then during
endpoint selection any endpoint that does not satisfy that assertion will
automatically be discarded as a candidate. This flag is valid only for endpoint
assertions.
- Fill From Context: If an assertion is marked as Fill from context,
it is automatically included in the invocation context. This flag tells the
system to populate the asserted properties of an assertion from the context
at runtime. The fill from context assertion flag selection appears
only if the assertion has more than one property and is valid only for content-based
assertions that can be added to a policy.
Navigation
Navigate to the Editor of the Policy/Editor
and access the Assertions tab from the bottom of the workbench.