Workflow Components

A Workflow includes the following components, which you must define. Executable instances in a Workflow, Workflow Structures, and Notifications are all called Workflow activities.

• Oracle LSH Executable Object Instances. To execute a Load Set, Program, Report Set, or Data Mart as part of a Workflow, you must create an instance of it in the Workflow. See Adding Executables.

• Workflow Structures. You can add predefined structural activities such as Fork, And and Or to control Workflow execution. See Adding Workflow Structures.

• Notifications. Notifications are messages sent to Oracle LSH users either simply to convey information or to request approval. You can link a Notification to the completion of an activity in the Workflow. For example, when a Load Set execution completes you can request approval from one or more people. The Workflow waits while these people verify that the Load Set successfully loaded the correct data. Only after receiving approval from one or all recipients (depending on how you define the Notification) does the Workflow proceed to the next activity. You can also use a Notification to alert a group of people that a report has been successfully generated on fresh data. See Defining Notifications.

• Transitions. Transitions define the condition, if any, required to move from one activity to the next. You must define a Transition between each sequential pair of activities. See Defining Transitions.

• Workflow Parameters. You can define Parameters directly in the Workflow for the purpose of passing their value (which is set in the Execution Setup definition or at runtime) to input Parameters of the executables within the Workflow. You can also set up value propagation from the output Parameter of one Program to the input Parameter of another Program executed later in the Workflow. See Setting Up Parameter Value Propagation.