Workflow Component

Business Scenario • RO raises a request which needs to be approved by either BO , CO and SCO respectively. This scenario depicts single level authorization.

 •  The status of the request would be New Request, Pending Authorization and Authorized /Rejected as the flow proceeds.

 

Workflow Inputs/Outputs

Inputs

*    Process Name
*    RoleID

Inputs

* Next level authorizer* Status of request

Workflow Component

Business method

 The call to the workflow from the business method would be generally as follows:
    ValueObject vo =workFlowMethod(processName, RoleID );
Ø  The workflow would return the desired results in this case the Authorizer and the Request Status embedded as a ValueObject.
<WorkflowProcess code=“1” Createdby=“admin” description=“Workflow for auth request”  name=“TESTWORKFLOW”  version=“1” >

 

<Activity assign_mode=“R” code=“REQUEST_ACTIVITY” description=“RO BO CO AMLCO raises a request”  function_id=“FUNCTION.WF.PC.CAMBERLMT.REQUEST” subversion=“1”>
    <Transitions>
          <Transition code=“Tr2Req1” description=“when RO raises a request” toActivity=“AUTH_ACTIVITY1” >
                  <MetaRef code=“10” version=“1” />
            </Transition>
          <Transition code=“Tr2Req2” description=“when BO raises a request” toActivity=“AUTH_ACTIVITY2” >
                  <MetaRef code=“11” version=“1” />
            </Transition>
    </Transitions>
 </Activity>
<Activity assign_mode=“R” code=“AUTH_ACTIVITY1” description=“BO CO AMLCO authorizes a request”  function_id=“FUNCTION.WF.PC.CAMBERLMT.AUTH1” subversion=“1”>
    <Transitions>
          <Transition code=“Tr2Auth” description=“when request is authorized” toActivity=“ENDACTIVITY” >
                  <MetaRef code=“120” version=“1” />
            </Transition>
          <Transition code=“Tr2Auth” description=“when request is rejected” toActivity=“ENDACTIVITY” >
                  <MetaRef code=“121” version=“1” />
            </Transition>
    </Transitions>
 </Activity>
 <Activity assign_mode=“R” code=“AUTH_ACTIVITY2” description=“CO AMLCO authorizes a request”  function_id=“FUNCTION.WF.PC.CAMBERLMT.AUTH2” subversion=“1”>
    <Transitions>
          <Transition code=“Tr2Auth” description=“when request is authorized” toActivity=“ENDACTIVITY” >
                  <MetaRef code=“120” version=“1” />
            </Transition>
<Transition code=“Tr2Auth” description=“when request is rejected” toActivity=“ENDACTIVITY” >
                  <MetaRef code=“121” version=“1” />
            </Transition>
    </Transitions>
 </Activity>
<Activity assign_mode=“R” code=“END_ACTIVITY” description=“dummyActivity”  function_id=“FUNCTION.WF.PC.CAMBERLMT.END” subversion=“1”>
    <Transitions>
          <Transition code=“Tr2Auth” description=“End of activity” toActivity=“” >
                  <MetaRef code=“150” version=“1” />
           </Transition>
    </Transitions>
 </Activity>
</WorkflowProcess>

 

                                               Java program/Parser logic

 

 

 

 

The parser logic (generally) would be as follows:
1.Validate the XML file (file has been formed correctly with the required parameters)
2.FUNCTION_ID mapping is proper i.e. the user is authorized to perform the request/authorization.
3.Parse the XML and get the logic from the XML file
4.Return the next level authorizer and the status of the request.

 

•General Idea on Workflow

2•How it works and functions

3•High level configuration and design with a small example 

4•Workflow at its simplest is the movement of documents and/or tasks through a work process.
  
5•More specifically, workflow is the operational aspect of a work procedure:
   
*    How tasks are structured
*    Who performs them
*    What their relative order is
*    How they are synchronized
*    How information flows to support the tasks
*    How tasks are being tracked. 
Eg: CR(Change Request ) 

Single steps or components of a workflow can basically be defined by three parameters: 

* Input description ( ProcessName, role name)
* Transformation rules, algorithms (Business rules in WF)
* Output description  (Output out of the workflow which would be the next authorizer’s role or end of flow)
Eg: CR(Change Request ) 

Single steps or components of a workflow can basically be defined by three parameters: 

* Input description ( ProcessName, role name)
* Transformation rules, algorithms (Business rules in WF)
* Output description  (Output out of the workflow which would be the next authorizer’s role or end of flow)
•Workflow could be added to the Business component as shown: