Rules, data elements and extensions

This is the part of the SDK most developers use once they move beyond simple read-only discovery. Rules define behavior, rule components hold actions and conditions, data elements hold reusable values, and extensions provide the delegates behind those objects. This overview page points you to the smaller workflow pages so you can read only the part you need.

Use this area

Read this area when you need to answer questions like:

• How do I create or revise a rule?
• How do rule components relate to rules and extensions?
• How do I create data elements and extension-backed configuration?
• How do I inspect a resource across the upstream library chain?
• How do I prepare a review-friendly JSON diff with associated records and impacted rules?
• How do I work with extension packages and private authorizations?

Page map

• Rules Read this when you need rule CRUD, revisioning, origin lookup, or rule-level upstream and comprehensive review lookup.
• Rule components Read this when you need to build conditions and actions with explicit rule and extension relationships.
• Data elements Read this when you need reusable values backed by extension delegates, or impacted-rule analysis for review workflows.
• Extensions Read this when you need installed extension instances, extension configuration, or extension-level dependency review.
• Extension packages & authorizations Read this when you are uploading, releasing, or sharing extension packages.

Common journeys

1. Create or update the rule in Rules.
2. Add the supporting components in Rule components.
3. Add reusable values in Data elements if the rule depends on shared inputs.
4. Inspect installed delegates and package metadata in Extensions and Extension packages & authorizations.
5. If you are comparing behavior across libraries, start with the comprehensive helpers documented on Rules, Data elements, Extensions, and Upstream chain.