Application processes, like component processes, are created
with the process editor.
IBM® UrbanCode Deploy provides
several common process steps. Otherwise, application processes are
assembled from processes that are defined for their associated components.
Apply Configuration
Runs a component process of the type Operational (No Version
Needed) or Configuration Deployment.
Acquire lock
This step acquires a lock on a specified string value.
You can use locks to prevent concurrent modification of resources.
Release lock
This step releases a lock on a specified string value.
Set Status
This step sets the ending status of the process. The step
can specify that the process is completed or failed.
Switch
This step branches the process that is based on the value
of a property.
Join
The Join step merges a process so that only one step runs
at a time.
Note
The Note step adds a note to a process diagram.
Run Generic Process
This step runs a generic process as a step in an application
process.
Manual Application Task (Utility)
A manual task interrupts an application
process until manual intervention is done. A task-interrupted process
remains suspended until the targeted user or users respond. Typically,
manual tasks are removed after the process is tested or automated.
Apply Configuration
Runs a component process of the type Operational (No Version
Needed) or Configuration Deployment.
Acquire lock
This step acquires a lock on a specified string value.
You can use locks to prevent concurrent modification of resources.
Release lock
This step releases a lock on a specified string value.
Set Status
This step sets the ending status of the process. The step
can specify that the process is completed or failed.
Switch
This step branches the process that is based on the value
of a property.
Join
The Join step merges a process so that only one step runs
at a time.
Note
The Note step adds a note to a process diagram.
Run Generic Process
This step runs a generic process as a step in an application
process.
Manual Application Task (Utility)
A manual task interrupts an application
process until manual intervention is done. A task-interrupted process
remains suspended until the targeted user or users respond. Typically,
manual tasks are removed after the process is tested or automated.