Activities

A Process Definition is composed of Process Activities. An Activity refers to the unit of work or job to be performed. An activity can be human task, service task, sub pipeline or inline process.

Adding a Human Task
Adding a Service Task
Adding a Sub Pipeline
Adding an Inline Process
Deleting an Activity

Adding a Human Task

Human Task is used if an activity requires a human intervention to go to the next activity.

To add a human task

From the Process Flow tab, click Human Task from the Activities pane in the floating toolbar and click on the drawing canvas where you want to place it.
Double-click icon. The Activity tab is displayed.
Enter the details as given in the table:

Field	Description
Activity ID	Displays the automatically generated Activity ID.
Activity Name	The activity name is displayed automatically same as the Activity ID. Modify the activity name if required.
Activity Desc	Enter the description of the Activity.
Activity Type	By default, the activity type of the selected activity is displayed.
Status	Select the status of the activity from the drop-down list. The list displays the seeded values in the AAI_WF_STATUS_B table.
Outcomes	This is not applicable if the Activity is a Run Task. Select the required Outcomes from the drop-down list. The list displays the seeded values in the AAI_WF_OUTCOMES_B table.

Click to add tasks for the activity.

Click Add to add a new task. For more information, see Tasks section.
Click Group Approval to configure sequential or parallel group approval. For more information, see Group Approval section.

Click to select the Notifications tab to add notifications for the activity. For more information, see Notifications section.

Adding a Service Task

Service Task is an automatic task which gets triggered in the Process flow. It is used to execute the Business Logic which is defined through Application Rule of Execution Rule type. For more information on configuring Application Rule, see Application Rule section.

Service Tasks are typically used to invoke External Model Service through Rest API, External Java APIs, Stored Procedures, and Functions.

More detailed explanation of invoking external model service is available in How to invoke External Model through Web Service section in OFSAAI Process Modelling Framework Orchestration Guide.

To add a service task

From the Process Flow tab, click Human Task from the Activities pane in the floating toolbar and click on the drawing canvas where you want to place it.
Double-click icon. The Activity tab is displayed.

Activity ID is auto populated.
Enter Activity Name and Activity Description.

Click . The Implementation tab is displayed.
Select the required information domain from the Infodom drop-down list. The list displays all the infodoms mapped to the applications configured in your OFSAA instance.
Select the Execution Rule which needs to be executed for this activity. For more information on how to define an Application Rule, see Application Rule section.

Click . The Participant Details window is displayed with all Application Rules of Execution Rule types available in your Process.
Click the Name link of the Application Rule to view the details.
Select the required Rule and click Ok.

Add Parameters you want to pass to the Execution Rule using Data Fields. You can pass Static values or Dynamic Values. In case of Dynamic, the value needs to be entered during execution of the workflow.

Click Add under Parameters. The Binding Details window is displayed. This window allows you to add parameters to the selected run definition in case of Run Task.
Select the required parameter to which you want to pass the value, from the Data Field drop-down list. The list displays the defined Data Fields for the current process or package.
Select the Parameter Type as Static to pass a static value to the selected Data Field in the Value field or as Dynamic to pass the value during execution of the workflow.

Select an application rule which you want to execute before executing the Execution Rule.

Click corresponding to Pre Rule and select the required application rule.

Select an application rule which you want to execute after executing the Execution Rule.

Click corresponding to Post Rule and select the required application rule.

Adding a Sub Pipeline

Reusability is important while designing your pipeline. Sub Pipeline is the mechanism in the PMF to call another pipeline from your parent pipeline.

To configure a sub pipeline

From the Process Flow tab, click Sub Pipeline under Activities toolbar in the left pane and click the drawing canvas where you want to place it.
Double-click icon. The Sub Process Details window is displayed.
Enter the details as given in the table:

Field	Description
App Package ID	Select the Application Package from which you want to call a process, from the drop-down list. The package IDs that are seeded from backend are displayed in the list.
Process ID	Select the Process which you want to call within your workflow, from the drop-down list. The list displays all processes defined for the selected Application Package.
Object ID	Select the Object ID from the drop-down list. Object ID is the entity ID used to identify if a workflow needs to be started from the beginning or from the current stage. Object ID drop-down list is populated from the Data Fields..
Object Type	Select the object type from the drop-down list. Object Type is used to identify a workflow that is passed by the application.
Data field pass	Select Yes to pass the parameters passed to the parent workflow to be passed to the selected sub process.
Calling Mode	§ Synchronous – Select this option if you want the sub process to complete before the flow moves to the next activity. Asynchronous – Select this option if you do not want to wait for the sub process to complete. And the parent workflow proceeds to the next activity.

Inline Process

Inline Process is mostly used for readability and usability. It is used to group a set of tasks as an Inline Process. This helps to represent a Process Flow with so many tasks /OFSAA widgets in a systematic and organized way. You can have Inline Process inside another Inline Process.

For example, if an RRF Run definition has multiple sub processes (RRF), each sub process can be represented as an InLine Process.

To add an Inline Process

From the Process Flow tab, click InLine Process under Activities toolbar in the left pane.
Click the drawing canvas where you want to place it.
Mouse over the icon . The sub menu is displayed.
Click to modify the Inline Process name. click OK.
Double-click the Inline Process icon .
Design the process flow using various components available in the Process Flow tab. For more information on each component, see Components for Designing Your Process Flow section. You can have another InLine Process inside your InLine Process.

Deleting an Activity/Sub Process/OFSAA Widget/InLine Process

You cannot delete an Activity/Sub Process/OFSAA Widget/InLine Process which has incoming transitions to it.

To delete an Activity/Sub Process/OFSAA Widget

From the Process Flow tab, mouse over the Activity/Sub Process/OFSAA Widget icon and click . A confirmation message is displayed.
Click Ok to delete the Activity. If any connecting Activity is there, you will be prompted to delete it first.