Input variables

The input variables define the values an activity requires before it can start. They provide the necessary context and data for the activity to execute correctly.

You can define, assign, and validate input variables passed into orchestration flows using the modeling interface. Correct configuration of input variables supports state setup and orchestration logic, ensuring successful Symphony execution and approval.

Input variables can be sourced from:

  • Symphony variables
  • Outputs of previous activities
  • Static (manually entered) values

Example

A Data Flow activity might require these input variables:

  • FilePath
  • CustomerNumber

These inputs specify which file the activity should process and which customer the file is associated with, enabling the activity to run with the correct data.

Best practices

Follow these best practices to ensure reliable input value configuration:

  • Avoid using raw JSON, XML, or base64 payloads, as these are not supported in Symphony input fields.
  • Ensure input values conform to the declared data type.

    These are the supported variable types:

    • String
    • Boolean
    • Integer
    • DateTime
    • Double
    • LIST
    • IFS USER
    • IFS GROUP
    • DATE
    • URL
  • Do not use null, blank, or space-padded values.