Map Variables - Map Variables - Content Innovation Cloud - Hyland Automate Modeler - Current/Hyland-Automate-Modeler/kaa1674557330159 - Current - Current

Hyland Automate Modeler

Platform
Content Innovation Cloud
Product
Hyland Automate Modeler
Release
Current
License
ft:lastPublication
2026-11-09T23:07:34.300254
ft:locale
en-US

When you select Map variables as the mapping type, each input and output parameter can be configured individually. This gives you control over how data is transferred at runtime and ensures that the correct values are used when a process interacts with other elements, such as decision tables or integrations.

Choose Map variables when you need full control over how inputs and outputs are connected. Use clear and consistent variable names that reflect business meaning, such as invoiceTotal or approvalStatus, to make mappings easier to understand.

You can map variables in one of the following ways:

Mapping Type Description
Process variables

Use existing process variables to provide input values or store output values. The type of the process variable must match the type of the parameter: for example, a parameter of type string cannot be mapped to a variable of type file.

Use this option when the value is already available in the process and does not require transformation.

Expressions

Use expressions to create more advanced mappings using a JSON editor. Expressions allow you to extract or transform values from structured data. For example, the expression of ${temperature.celsius} retrieves the value the celsius field from a JSON object. In the following example, the expression would result in a value of 16:

  {
	"day": "Monday",
	"temperature": {
  	"celsius": 16,
  	"fahrenheit": 66
		}
  }

Use expressions when you need to work with nested data or adjust values before mapping them.

Static values

Enter a fixed value instead of using a process variable.

Use this option when the value does not change during runtime.

When the process reaches a step that uses mapped variables, the system reads the mapped input values, executes the step, and then writes the mapped outputs back to process variables.

An example of using the Map variables option is a decision table that contains the input Price and the output Decision and the process contains the process variables Total and customerResponse. At runtime, the value for the process variable Total will be sent as the input to the decision table when that point in the process instance is reached. Once the decision table has evaluated the input, the value of the output Decision will be sent back to the process variable customerResponse which can then be used later in the process, such as in sending an email to a customer.