Applications, components, and generic processes share some process steps. This step applies to application processes, component processes, and generic processes. This step applies to application processes that are associated with application templates.
| Field | Description |
|---|---|
| Name | A name for the step. Other process steps can refer to this step by this name. |
| Process | The generic process to run. |
| Max # of concurrent jobs | The maximum number of component processes to run at the same time. To run an unlimited number of concurrent processes, specify -1. In this field, you can use a value from another process property. UrbanCode Deploy attempts to resolve the value to an integer. If the value does not resolve to an integer, then the -1 value is used by default. Important: The number of component processes that can run concurrently is limited by the agent, based on the hardware configuration the agent runs on. |
| Fail Fast | If this check box is selected, the step does not start more processes after one process fails. |
| Precondition | A JavaScript 1.7 script that defines a condition that must exist before the step can run. The condition must resolve to true or false. In the script, do not use the ${p:component.myProperty} notation. For example, to check the value of a component property in a component process, use properties.get("myProperty") == "myValue". See Property scopes for information about property access. |