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 the following items:
- URI: The URI location of the assertion
- Namespace: The namespace the assertion is associated to
- Name: The name of the assertion
- Description: A description of the assertion
Assertion Information
The Assertion Information group provides the following items:
- Comparator: Determines how property values are compared to context
values
- Usage: Enables assertions to be applied to an endpoint, a policy
or both.
- Type: Defines the type of assertion.
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, see Working with correlation queries.
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 with a
policy (for example: Reject Always).
An assertion type can have an allowedUsageConstraint annotation: ENDPOINT
POLICY BOTH.
The system does not permit you 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:
- A policy condition can include expressions involving asserted properties
of the assertion (for example, AccountSize > 1,000,000).
- A content-based assertion can be used in a policy contract like any other
assertion with fixed values for its assertion properties.
- A new Fill From Context content-based assertion can appear in the selection
policy with the values injected at run time from the message
content. The contract asserted by a policy is only considered if its conditions
are satisfied.
Assertion Comparators
The following policy condition comparators are available for writing expressions
about content-based assertion properties:
- not equal ≠
- less than or equal to ≤
- greater than or equal to ≥