Executing and Managing Business Processes
Use the BPW_PROC_RUN component to define the business process run control.
Use the BPW_PROC_INST component to review and control the business process execution.
Use the BPW_PRCRUN_REQ component to schedule business process execution.
Use the BPW_PURGE_REQ component to purge the business process instance data.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
BPW_PROC_RUN |
Set up run controls for the business process that provide data parameters to execute the tasks. |
|
|
BPW_PROC_INST |
Review and control the execution of business processes. |
|
|
BPW_PRCRUN_REQ |
Schedule the execution of business processes. |
|
|
BPW_PURGE_REQ |
Set up the options to purge the business process instance data. |
Use the Business Process Run Control page (BPW_PROC_RUN) to set up run controls for the business process. It provides data parameters to execute the tasks.
Navigation:
This example illustrates the fields and controls on the Business Process Run Control page (1 of 2).
This example illustrates the fields and controls on the Business Process Run Control page (2 of 2).
Note: The system disables the Start Process button on the Business Process Weaver Run Control page when a user does not have access to the first step in the Business Process Weaver definition. A user must have access to both the first step in the definition and the first step in the run control security data.
Field or Control |
Description |
|---|---|
Inherit Definition Security |
Select to copy and use security defined on the Business Process Security page. At least one security row must be defined on the process definition to inherit security. If security has not been defined, the system hides the Inherit Definition Security check box. See Defining Business Process Weaver Security Options for more information. |
Security |
Click the Security link to define security by role or user and override security set up on the process definition. See Defining Business Process Weaver Security Options for more information. |
Inherit Notifications |
Select to copy and use notifications defined on the Business Process Definition Notifications page. At least one notification must be active on the process definition to inherit notifications. If none of the notifications are active or defined, the system hides the Inherit Notifications check box. When you select the Inherit Notifications check box, the system hides the Notifications link. See Setting Up and Using Business Process Notifications for more information. |
Notifications |
Click the Notifications link to select and override notifications set up on the process definition. See Setting Up and Using Business Process Notifications for more information. Note that the Notifications setup from the Run Control page is the same as the setup from the Business Process Definition. |
Many of the fields are copied from the Business Process Definition page. See Defining Business Processes.
Run Control IDs
Run controls identify the data (parameters) that are the inputs to the processes/programs. Each run control is identified by a Run Control ID. Four levels of Run Control IDs are available. A lower level ID is generally provided by default from a higher level if a value is not provided. For example, the Thread Run Control ID is used for a step if the Step Run Control ID is not provided. Step Thread Run Control ID is the lowest level, and it is the Run Control ID that is passed to the Task (for example, batch process/job) when the task is executed.
From high (parent) to low (child):
Process Run Control ID – This ID identifies the business process run control. It is unique per user and per business process.
Thread Run Control ID – This ID identifies a process thread inside the business process. Each process thread should have a different Thread Run Control ID.
Step Run Control ID – This Run Control ID is associated with the step. It is used to create a step thread if no step threads were created explicitly. If an event handler is associated with the step to create step thread run controls dynamically, then this value can be used to pass the “master” run control to the event handler to partition data and create step thread run controls. If the prompt record is set up in the Task Registry for the step’s task, then a user can select existing Run Control IDs from the prompt table. However, regardless of whether a prompt table is set up, users can enter any desired value as the Step Run Control ID.
Step Thread Run Control ID – This Run Control ID is associated with the step thread and is the run control passed to the task for execution. At least one step thread is created for each step. If a prompt record is set up in the Task Registry for the task of the parent step, then a user can select existing Run Control IDs from the prompt table. However, regardless of whether a prompt table is set up, users can enter any desired value as the Step Thread Run Control ID.
Header
Server Name – Optionally, you can specify the Process Scheduler Server to run the process.
Start Process – After the run control is set up, you click on the Start Process button to start running the business process. You are automatically transferred to the Business Process Instance page with the created business process instance opened.
Refresh from Definition – When a business process run control is created, the business process definition selected is copied. This action will ensure the integrity of the run control. If after the run control is created the definition is changed, then this message and the Refresh button will be available for users to sync with the definition manually. The business process run control will be recreated with the same process thread/step/step thread run controls (if the step is not deleted).
Process Threads/Steps
The Process Threads section allows you to create multiple process threads. The Process Steps section allows you to associate run controls to each step.
Multiple Threads– In the Business Process Run Control page, users can create multiple step threads to manually partition the data and create multiple parallel executions. When users select this check box, the Step Threads button will be available to allow users to enter multiple step thread run controls, and the Step Run Control ID will be hidden. If a value is already entered in Step Run Control ID, then it will be used as the first Step Thread Run Control ID. This check box is disabled if multiple Step Thread Run Control IDs are already entered.
Step Threads – When Multiple Threads is selected, this button is available for users to open a secondary page to enter the Step Thread Run Controls.
RC Status – This value indicates the Run Control Status. Business Process Weaver (BPW) checks and displays the RC Status, depending on the value entered and the task setup and whether event handler will create dynamic run controls. The status icons are described below. You can hover over the icon to see a description, and click the icon to open a pop-up menu that provides more details. The RC Status field can have the following values:
Field or Control
Description
Run Control
Setup ExistsRun control prompt record is set up in the associated task and the run control entered exists in the record.
Run Control
Setup MissingRun control prompt record is set up in the associated task and the run control entered does not exist in the record.
Run Control
Not RequiredRun control prompt record is set up in the associated task and the run control entered does not exist in the record. However, the task registry indicates the run control is not required to execute the task.
Run Control
Setup UnknownRun control prompt record is not set up in the associated task and it is not possible to check whether the run control exists.
Dynamic
Run Control The step is associated with an event handler, which indicates that dynamic run controls will be created.
Run Control Setup – If the associated task is set up to have a Run Control Prompt Table and a Run Control Setup page in the Task Registry, then this button will be available to allow users to open the Run Control Setup page directly from the Business Process Run Control page. If the Run Control ID exists, then that run control is opened automatically. If the Run Control ID does not exist, a new run control is created and opened directly. In both cases, users must save (click OK or Apply) on the Run Control Setup page to save the updated or new run control. After returning from the Run Control Setup page, the RC Status will be refreshed.
Graph
The Process Graph shows the flow of the process and the run controls for each step. It is displayed by the process thread.
Each node shows the Step ID and its Run Control ID with RC Status for a step. You can hover over Step ID to see the step description and the task ID for the step. If an icon is associated with the task, it will appear at the top-left of the node.
If Run Control Setup page is set up (for example, a Run Control Setup button is available in the Process Steps section), you can click the Run Control ID to open the run control setup page. Whether this is available is shown by hovering over the Run Control ID to see if the Run Control ID is highlighted.
If the step has multiple step threads, then the Run Control ID appears as “(Multiple),” and you click it to display a pop-up menu for the list of the step thread run control IDs.
In addition, a count bubble is displayed at the top-right of the node.
You can click RC Status Legends to toggle the display of the RS Status Legends.
The graph is copied from the business process definition.
Since it has been set up in the Business Process Definition page, you are not able to move and rearrange the nodes. However, you can use the zoom in and zoom out icons, as you do on the Business Process Definition Page.
Use the Business Process Instance page (BPW_PROC_INST) to review and control the execution of business processes.
Navigation:
This example illustrates the fields and controls on the Business Process Instance page (1 of 2). You can find definitions for the fields and controls later on this page.
This example illustrates the fields and controls on the Business Process Instance page (2 of 2). You can find definitions for the fields and controls later on this page.
Field or Control |
Description |
|---|---|
Search Process Instance |
Click this link to access the Business Process Instance Search page. |
Notifications |
Click this link to view the notifications for this Run Control ID. The Business Process Instance Notifications secondary page provides display-only notification details. Notification links received by email or worklist direct the user to the Business Process Instance page. See Setting Up and Using Business Process Notifications for more information. |
Process Action |
Select a valid action from the drop-down list to apply the action to the whole business process. |
Refresh |
Click this button to refresh the data on the page. |
Field or Control |
Description |
|---|---|
Started / By |
Displays the date and time that the business process instance was started and the User ID that initiated the process. |
Process Status / At |
Displays the Process Status of the business process instance and the date and time when it was last updated. You can click the Process Status link to open the Process Log secondary page, which shows the log entries for the entire business process. |
Process Instance Number |
Displays the instance number that is assigned to the business process instance when it was started. |
Business Process
This section provides information from the Business Process Run Control.
Process Threads
Field or Control |
Description |
|---|---|
Started / By |
Displays the date and time that the business process instance was started and the User ID that initiated the process thread. |
Process Status / At |
Displays the Process Status of the process thread and the date and time when it was last updated. You can click the Process Status link to open the Process Log secondary page, which shows the log entries for the process thread. |
Thread Instance Number |
Displays the instance number that is assigned to the process thread. |
Process Steps
Field or Control |
Description |
|---|---|
Action |
Select a valid action from the drop-down menu to apply the action to the step. Valid actions are determined by the status and whether the user is the user who set up the run control or whether the user is a process scheduler administrator. |
Step ID |
Click this link to open the Step Threads for the step. |
Process Status |
Indicates the process status of the step. Click the link to open the Process Log secondary page, which shows the log entries only for the step. |
Status Date/Time |
The date/time the process status is updated. It is a link that users can click to open the Message Log secondary page, which shows the log entries for the step. |
Step Instance Number |
The instance number assigned to the step by BPW. |
Graph
The Process Graph shows the flow of the process and the process status for each step. It is displayed by process thread.
Each node shows the Step ID and its process status and valid actions. You can hover over the Step ID to see the description and task ID for the step. If an icon is associated with the task, it will appear at the top-left of the node
Click on the process status to open a pop-up menu to drill down to the Process Log, Message Log, and Step Threads secondary pages, similar to using the Process Status, Status Date/Time, and Step ID links in the Process Steps section. From the pop-up menu, you can also open the Reports and Log/Trace page to review the reports, the logs/trace, or both as generated from the process. For batch, this capability enables you to review the reports and logs/trace without navigating to the Report Manager or Process Monitor.
An alert icon can appear in front of the process status to indicate whether an error, warning, or information message is available in the Process log, Message log, or both that you should review.
If valid actions exist, you can click Action to open a pop-up menu with a list of the valid actions for the step and select the action to apply to the step, similar to using the Step Action drop-down menu in the Process Steps section. If related actions are associated with the task, then the related actions will also appear in the pop-up menu. The related actions are created and performed by the event handler associated with the step.
The graph is copied from the business process definition. Since it has been set up in the Business Process Definition page, users are not able to move and rearrange the nodes. However, you can use the zoom in and zoom out icons, as you do on the Business Process Definition Page.
Use the Business Process Runner page (BPW_PRCRUN_REQ) to schedule the execution of business processes.
Navigation:
This example illustrates the fields and controls on the Business Process Runner page. You can find definitions for the fields and controls later on this page.
Business processes can be started from the Business Process Run Control page (by clicking the Start Process button). However, if you want to schedule the business process or to run multiple business processes at the same time, you can use the transaction/page to run the business processes.
Field or Control |
Description |
|---|---|
Run Control, Report Manager, Process Monitor, and Run |
These are common fields that exist on other Process Scheduler run control pages. When you click the Run button, you can schedule and run the Application Engine process, BPW_PRCRUN, which then starts the business processes that you have specified. |
Business Process Type, Business Process ID, and Business Process Run Control ID |
Specify the business process run controls to be executed. They are set on the Business Process Run Control page and are all required fields. |
RC Status |
Indicates whether the selected Business Process Run Control ID exists |
Run Control Setup |
Opens the Business Process Run Control page as a modal component. It is available if the Business Process Type, Business Process ID, and Business Process Run Control ID fields are populated. If the selected Business Process Run Control already exists, it will be opened. If not, a new one with the selected run control ID will be created. Note: The new run control is not saved automatically; you must make changes and save. |
Enabled |
Select to enable a particular business process run control. |
Last Run, Instance |
If the business processes have been executed previously, these fields indicate the date/time stamp and the Process Instance. The Instance link takes you to the Process Monitor (as modal component). |
Business Process Instance Number |
The instance number of the business process instance of the previous execution. It is a link that takes users to the Business Process Instance (as modal component). |
Use the Business Process Purge page (BPW_PURGE_REQ) to set up the options to purge the business process instance data.
Navigation:
This example illustrates the fields and controls on the Business Process Purge page. You can find definitions for the fields and controls later on this page.
Run Control ID, Report Manager, Process Monitor, and Run are the common fields that exist on other Process Scheduler run control pages. When you click the Run button, you can schedule and run the Application Engine process, BPW_PURGE, with business process instance data specified.
Process Status - The process status of the business process instances to be purged.
Days Before Purge – Enter the number of days that must pass since the last status update on the business process instances before the data will be deleted.
Enabled - Select this check box to enable this option. It is available only if Days Before Purge are specified.
Last Run, Instance - If the data purge executed previously, then these fields indicate the date/time stamp and the Process Instance. Instance is a link that takes you to the Process Monitor (as a modal component).