Scripting with the Job Input in Mind

Robot School is the knowledge & learning centre for the Automation Cloud

Previously in the course, we used to define the data right in the Script. In this lesson, you'll learn how to upgrade your solution to consume Job inputs. It's all about keys and values!

Cinema mode: Off

There are two components to scripting with Job input in mind:

Specify all the desired input keys via the "Input" panel. For each input key, provide the value – an example piece of data.
Connect your Script actions with Job inputs using the Value.getInput pipe.

The Value.getInput pipe acts the same way as the Value.getConstant. The difference is in the configuration. The constant one needs you to define the value directly, and the input one expects a key. Keep the value in the "Input" panel of the Autopilot.

For optional form fields, go with an empty value per input key.

When a Job runs in the Automation Cloud, it ignores the input bundles (those are for Autopilot only!). Instead, a Job requests all the inputs from a client, your app. It's up to you to provide some or all the information on job creation, or in due course.

The Input Panel

Create as many inputs as you need.
To create an input snippet, hit the "+ Add input" button, specify the key and the value. The value acts as an example piece of data.
A list of inputs forms a bundle. Feel free to create a few bundles to test your automation with various input values for the same set of input keys.