Before reviewing the example, it's recommended that you first read the How to Start a Job tutorial.
The example below shows the job template experience when a user selects All for their job Strategy when their process does not have required or optional input arguments.
In this example, the event that invokes this template is the creation of a new account. Defining how it gets invoked is application specific and not covered in this example.
The following steps and images are an example of how the connector works from design time (i.e., user inputs) to run time (i.e., sending the HTTP request).
- Enter a Job Template Name.
- This name is used in your application and can act as a unique identifier in case you want to start different jobs depending on the event that occurs in your application.
- Enter the Process Name that you want to start.
- After entering the process name, the connector sends a request the Releases endpoint to retrieve all of the process Environments.
- The system processes the response and populates the Environment drop-down list with the EnvironmentName values and the Input button becomes disabled because the process does not have any input Arguments (i.e.,
- Select the Environment that you want to start the job in.
- Select the Strategy that you want to apply to the job (i.e., All).
- Click Save.
- When a new a new account is created in the application, the connector sends a request to the Jobs endpoint to start the specified process.
Updated about a year ago