Some processes are appropriately run on a schedule while other are run on an as needed basis. For example, a process that is designed to back up databases is best run on a regular schedule. A process that is designed to restore a database would be run only when needed. Content designers create agendas to start processes that are designed to run on a schedule. Content designers create start request forms to start on-demand processes that require users to specify settings at run time.
For on-demand processes with static settings, a start request form is not needed. You initiate the execution directly, from the process itself. Processes designed to be run at the discretion of users are in appropriate to schedule or start with triggers.
Processes run on an Orchestrator that is running the process control. When you start a process, the process control creates an instance of the process in memory. Operators in a process are then processed according to the logical order icons and the links between them in the process defines.
When error conditions arise, a process can perform corrective actions or can notify users with email alerts. You can open a suspended process to change parameter settings or edit the flow itself before restarting the flow. A suspended instance of a process can be re initialized and started from the beginning or restarted from where it left off.
|
Copyright © 2014 CA.
All rights reserved.
|
|