The Metadata action is a non-rendering container used exclusively for transporting metadata from its creation point to its resolution or failure. It acts as a simple pass-through vessel with no additional logic or features.

Key Features:

Data Vessel: Designed to carry metadata without performing any computation or rendering.
Single-level Context: The context allows only one level of key-value pairs, where keys are strings and values must be of scalar types (string, number, boolean, or date in ISO 8601 format`). Complex structures like arrays or objects must be serialized before inclusion.

Use Case: Ideal for scenarios where metadata needs to be preserved and passed through unchanged across different stages of a business process.

Union (required)

This action lacks a resolution mechanism and depends on union resolution to complete its lifecycle.

Macro level details for how union attribute behaves can be found within the Union documentation.

Context (required)

Name	Type	Description	Rules

Example

Below is an example payload for adding an Metadata action to a business process or blueprint.

{
    "type": "metadata",
    "union": 1,
    "context": {
        "firstName": "John",
        "lastName": "Doe",
        "Age": 31,
        "Married": false
    }
}