The Action Orchestrator uses schemas to define its user interface (UI).  This is useful in that schema definitions can be easily created and modified for customer purposes.  The schemas exist in the system's database as JSON data structures, and there are both View and Data schemas for each UI page.  Outside the database, schemas exist in .json format files, with the view and data sections being in the same file.

The Manage Schemas page helps to view and modify existing schemas, as well as create new schemas in a UI setting without editing JSON text directly, and separates the view and data sections of the schemas seamlessly.  Within Manage Schema, user interfaces of all adapter objects, including adapters, targets, account keys, activities, and events, are driven by their corresponding schemas. Each object type has its own schema definition. Each object type’s schema includes both Data Schema and View Schema.

  1. Data Schema: Data schema contains the data attributes of each object type. A database schema is the skeleton structure that represents the logical view of the entire database. It defines how the data is organized and how the relations among them are associated. For example, data schema of a target describes all target configuration property names and data types of those properties.

  2. View Schema: The View schema is used to describe how an object should be rendered properly in an UI. For example, view schema of a target describes how those configuration properties will be rendered on the UI. That is which UI component should be used to render a property, display name of a property, position of a property in UI, which UI section a property belongs to, etc.

  3. Sample Schema: Displays the sample schema, to be used for reference only.

  4. JSON Standard Keywords: Displays the list of JSON standard keywords used by Action Orchestrator.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks