Creating Execution Workflow Step Sources

Before creating an execution workflow step source, see Execution Workflow Step Worksheets . It contains the information required to properly configure the workflow step source.

To create a new execution workflow step source:

From the Workbench shortcut bar, select Configuration > Workflows.
Open a workflow.

The Workflow window opens and the Workflow Step Sources window opens.
Select the Workflow Step Sources window.
In Filter by field, select Requests, Packages, or Release Distributions, depending on the type of workflow.
Select the Executions folder.
Click New.

The Execution window opens.
Type the information as listed in the following table.

Field Name	Description
Name	The name of the workflow step source. The step can be renamed when added to the workflow.
Workflow Scope	Describes the type of workflow that will be using this step source. Use the list to select a workflow scope. The following lists the possible values: ALL. For all workflow types. Requests. For Demand Management request workflows. Packages. For Deployment Management package workflows. Release Distributions. For Deployment Management release workflows.
Reference Code	Automatically populated with information entered in the Name field.
Description	Description of the step source.
Execution Type	Used to select the type of execution to be performed. Use the list to select an execution type. The following lists the possible values: Built-in Workflow Event. Runs a predefined command and returns its result as the result of the step. SQL Statement. Runs an SQL statement and returns its result as the result for the workflow step. PL/SQL Function. Runs a PL/SQL function and returns its result as the result for the workflow step. Token. Calculates the value of a token and returns its value as the result for the workflow step. Workflow Step Commands. Runs a set of commands, independent of an object, at a workflow step.
Workflow Event	For Execution Type Built-in Workflow Event, the specific event to perform must be selected. The available choices depend on the workflow scope selected and include: execute_object_commands. Runs the object type commands for a package line. execute_request_commands. Runs the request type commands for a request. create_package. Generates an Deployment Management package. rm_ready_for_release. Adds the current package to an existing release. Note that the existing release must be in an Open state. create_package_and_wait. Generates an Deployment Management package. The create workflow step that generates the package holds it until the package is closed. create_request. Generates another request. wf_close_success. Sets the request or package line as closed with an end status of Success. wf_close_failure. Sets the request or package line as closed with an end status of Failed. wf_jump. (Deployment Management and Demand Management) Instructs the workflow to proceed to a corresponding Receive Workflow Step in another workflow. wf_receive. (Deployment Management and Demand Management) Instructs the workflow to receive a Jump Workflow Step and continue processing a request or package line initiated in another workflow. wf_return. (Deployment Management and Demand Management) Used to route a subworkflow process back to its parent workflow.
PL/SQL Function	For Execution Type PL/SQL Function, the actual function to run. The results of the function determine the outcome of the step. The results of the function must be a subset of the validation values for that workflow step.
Token	For Execution Type Token, the token to be resolved. The results determine the outcome of the workflow step.
SQL Statement	For Execution Type SQL Statement, the actual query to run. The results of the query determine the outcome of the workflow step. The results of the query must be a subset of the validation values for that step.
Workflow step commands	For Execution Type Workflow Step Commands, the actual commands to run. The commands result is either Succeeded or Failed. Use a validation with those values to enable transitioning out of the step based on the execution results.
Processing Type	Determines when the execution step is performed. Use the list to select one of the following processing types: Immediate. Runs the workflow step upon workflow step eligibility. Manual. A user is to manually perform the workflow step.
Validation	Validations determine the transition values for the workflow step. Select a validation from the list.
Timeout	The amount of time that a step is eligible before completing with an error. Timeout intervals can be in minutes, hours, weekdays or weeks. Timeout parameters for executions are a combination of a numerical timeout value and a timeout unit, such as weekdays. If this workflow step remains eligible for the value typed in the timeout value, the request, package line, or release can be configured to send a notification to interested parties. Timeouts can be uniquely configured for each workflow step in the Layout tab. The timeout value specified in the workflow step source acts as the default timeout value for the step. When adding a workflow step to the workflow using this workflow step source, you can specify a different timeout value for the workflow step. For executions, timeouts can be uniquely configured for the amount of time that an execution is allowed to run before completing with an error. This applies to the workflow step commands and object type commands only. Command level timeouts are set in the Command window of an object type.
Icon	You can select a different graphic to represent this steps of this workflow step source. This graphic needs to exist in the icons subdirectory. All icons are in .gif format.
Enabled	The workflow step source must be enabled in order to add it to the workflow layout.

Click the Ownership tab.

The Ownership tab configures which security groups will have the ability to edit this workflow step. The default is to allow all security groups who can edit workflows to edit a workflow step source. For complete instructions on how to configure the Ownership tab, see Configuring Ownership of Workflow Step Sources.
Click the User Data tab.

Product entities such as packages, workflows, requests and projects include a set of standard fields that provide information about those entities. While these fields are normally sufficient for day to day processing, user data fields provide the ability to capture additional information specific to each organization. User data is defined under the User Data tab. If there are no user data fields, the User Data tab is disabled.
Click the Used By tab.

The Used By tab displays reference information concerning the workflow step.
Click OK.

The new workflow step source is now included in the Workflow Step Sources window. It can be used in any new or existing workflow with the corresponding workflow scope.