Skip to main content

4 posts tagged with "Policy"

View All Tags

Policy – Added

Added normalized variants of the v4 entity policy fields evaluate endpoint, for collection data groups with many items. Each collection data group returns every unique evaluated field once in its evaluatedFields list, and each item carries only an ordered evaluatedFieldRefs list of integer indices into that list, reducing payload size. To rebuild an item, resolve each index against the list in order. Indices are assigned per response and are not stable across requests.

The normalized endpoint takes the same request as the existing endpoint and returns the same evaluations; only the shape of the collection data groups differs. The existing endpoint is unchanged.

The read-only/normalized endpoint returns a slimmer field shape intended for read-only and display scenarios: only the single fields and collection data groups, each with the properties needed for display. Values evaluation is always skipped, validation errors are not returned, and access layers filtering is always applied, so these options are not part of the request.

Policy – Changed

Extended the requirement set retrieval API to support a configurable limit on the number of versions returned per jurisdiction.

New query parameter versionsLimit (optional): An integer to specify the maximum number of versions per jurisdiction. If not provided, it returns all.