Task References

On this page:



The transformation task allows the user to run a JSON Schema Transformation (JST) that has already been loaded into the system. A JST is used to transform data from one set of JSON Schemas to another set of JSON Schemas. Currently, JSON Schema Transformations are provided by Itential artifacts (App-Admin_Essential) and are not able to be freely created within IAP.

Blank Transformation

Creating a transformation in the Itential Automation Platform (IAP) using the API will require a unique name. This "name" is used when configuring the transformation task (see the Properties section below for more information). The user must populate the Transformation Name field with the "name" provided via the Create API (POST /transformations) or with the Search API (GET /transformations) and then click the corresponding name from the dropdown list. If the transformation in question does not contain a "name", then the "id" value can also be used. At this point, the Incoming Schema(s) section will be discovered and rendered from the transformation.

Matched Transformation


Name Description
Transformation Name This is the name of the transformation in the database. The name can be found by searching for a transformation using the Search API or from the "name" key in the response of the Create API.
Incoming Schema(s) The incoming JSON Schemas associated with the transformation. Each of these schemas require a data binding from either a previous task, job variable, or a static value. Each JST has a different (but not necessarily unique) set of incoming schemas.


Name Description
extractOutput This option extracts the output value if the transformation only has one outgoing JSON Schema. For example, a transformation with a single outgoing schema having an "$id" of "fruit" would normally respond as follows: { "fruit": "apple" }, but with the extractOutput option, the response would just be "apple".