OWB - Process Flow

Notes about process flow in OWB

The code generated from a process flow definition is in industry standard XML Process Definition Language (XPDL).

• OWB - OMB snippet for Process Flow
• OWB - Process Flow Parameters and Variables

You can do that with the OWB - Public Views (metadata). Here below an example for a mapping :

SELECT PACKAGE_NAME, 
       ALL_IV_PROCESS_ACTIVITIES.PROCESS_NAME, 
       ALL_IV_PROCESS_ACTIVITIES.ACTIVITY_NAME, 
       ALL_IV_PROCESS_ACTIVITIES.ACTIVITY_TYPE 
  FROM ALL_IV_PROCESS_ACTIVITIES, 
       ALL_IV_PROCESSES
 WHERE ALL_IV_PROCESS_ACTIVITIES.BOUND_OBJECT_NAME = 'NameofTheMapping'
   AND ALL_IV_PROCESS_ACTIVITIES.PROCESS_ID = ALL_IV_PROCESSES.PROCESS_ID

You can use the Fork activity to launch multiple, concurrent activities after the completion of an activity.

configuration properties “Use return as Status”:

• enabled then values for return statuses are :
  • 1 - SUCCESS
  • 2 - WARNING
  • 3 - ERROR
• disabled then value
  • 0 means SUCCESS
  • and non-zero - ERROR.

As a workaround, you can define processflow variable and bind RESULT_CODE parameter of Sql*plus activity to this variable. Then you can define transition from sqlplus activity with custom (“complex”) condition (like PF_VAR_RC=2 etc.).

Create a function which return as Status to return 1, 2 or 3 to direct the process flow into SUCCESS, WARNING or ERROR respectively.