Working with the assertion type editor

The Assertion Type Editor is used to view all assertions.

The following defines all groups contained in the Assertion Type Editor.

General Information

The General information Group provides:

Assertion Information

The Assertion Information group provides:

Correlations Group

This group lists all the pertinent correlation queries for the object type being edited. All Direct correlation sections still exist. All Indirect correlation sections have been collapsed into a single section. For more data, refer to the Working with correlations section.

Usage Types

Some assertions may only be used on an Endpoint (for example, Hours of Operation and Propagate policy). Other assertions may only be used on a Policy (for example, Reject Always).

An assertion type may have an allowedUsageConstraint annotation: ENDPOINT POLICY BOTH.

The system does not allow to add an assertion to a policy if it is constrained to endpoints, and vice-versa This prevents imaginative “creative”, yet unsupported, use of Hours of Operation and other specialized assertion types The usage constraints for an assertion are shown in the Assertion Type Editor.

Content-based Assertions

There are three ways to define the composite policy used for an endpoint selection:

Assertion Comparators

The following policy condition comparators are available for writing expressions about content-based assertion properties:
Related concepts
Implementing an assertion flag
Related tasks
Adding assertions
Related reference
Setting up an assertion listing