We will create a new model according to Wagby's normal operation. Navigation information showing the workflow behavior is displayed at the bottom of the screen.
When newly registering the data of the model corresponding to the workflow, the workflow is automatically started. I will describe it with an example applied to the "vacation application" model.
Log on with account "arakaki" and register one data.The item "application flow" is displayed at the top of the model defined using the workflow.hereAvailable application flow only available for selectionIt is possible to select flows that can be used in this model.This is the flow registered in "Setting the workflow definition in the model".
After data registration, the column of "application status" is displayed at the bottom of the screen, and a button is prepared to apply for this data.
We have not started workflow yet.At this stage, the data update button is displayed.
Enter a comment in the application status column at the bottom of the screen and press the "application" button of the workflow.
"Processing content" changes to "Application".Data can not be updated.
Next, log on with the approver "miyagi" and check the data in Fig. 4.Since "miyagi" is an approver, you can see that there are buttons "approval", "remand" and "reject".You can also update the data.
Write a comment and press the approval button.
If you take action (approve) on the workflow, you can not update the data.
Since this workflow is two nodes (sequential → sequential), it is automatically decided at this stage.
Log on again with account "arakaki".You can see that workflow has been decided.
You can obtain the status of the workflow with the FLOWSTATUS function.You can grasp the status of the workflow on the list display screen as shown in Fig. 9.
After applying, you can cancel this flow by pressing the "Cancel" button as long as the next approver has not yet approved (or handled about flows such as remand, reject, approval, etc.).
(In the flow event, it is recorded that "cancel" was done.)
The cancel button is prepared when the following conditions are satisfied.
The operation of each process at flow execution is as follows.
Apply the registered data to the approver and forward the flow to the next node.After applying, data can not be updated/deleted.You can cancel your application if the next approver has not done the approval process yet.
Approve the application flow and advance the flow to the next node.In case of final approval (approval), the flow ends.
After the flow is over, neither the applicant nor the approver can update/delete the data.
Return to the previous node.Applicant can apply again for returned data.
Reject the application and let the flow finish.After completion of the flow, neither the applicant nor the approver can update the data, but the applicant can delete the data.
"Status" and "Event" prepared in the workflow are as follows.
FLOWSTATUSIt can be obtained by function.
|(Blank)||It is unapplied.The workflow has not started.|
|Application||The applicant has started workflow.|
|Approval||Approval by approvers.In the case of a multistage node, it transitions to several approval states.|
|Decision||It is an approval act by the final approver (authorizer).The workflow will end.|
|Dismissal||This workflow has been rejected.The workflow will end.Please make a new workflow for re-application.|
|cancel||The applicant has canceled the application for this workflow.The workflow will end.Please make a new workflow for re-application.|
|start||Start||We have newly registered workflow data.The state has not been filed yet.|
|Application||Application||I applied for this workflow.|
|Approval||Admit||I approved this workflow.The approval action of the final approver (approver) is also included.|
|Dismissal||Reject||I dismissed this workflow.|
|Pass back to the previous||Back||I redeemed this workflow.It returns to the previous node.|
|Return to applicant||Rewind||I redeemed this workflow.I will return to the applicant (first node).|
|cancel||Cancel||I canceled this workflow.|
|Decision||End||After final approval, this workflow was approved.|
In Figure 1, if the option of "application flow" is empty, in the "flow participant setting" of this workflow, it is set in the flow participant or flow participant group of the node (applicant, person in charge, approver) To a user groupI am not affiliatedThere is a possibility of using it with an account.
If the log (system.log) shows as follows, please check the following points.
[ERROR jp.jasminesoft.util.VelocityUtils mergeContent] occur ResourceNotFoundException file:s-c.xml