-
Start:
-
Initiation:
-
The workflow begins automatically or manually, but it’s triggered when there's an update to the table "BT20.SACheckMaster."
-
The initial condition checked is whether the check status is "CP."
-
-
Creator Approval (Activity A1):
-
Responsibility:
-
The request is reviewed by the designated creator.
-
-
Wait Settings:
-
There are provisions to wait for 1 day, with retries allowed indefinitely if not approved.
-
-
Outcome:
-
If the request is not accepted, it transitions to "Move Status to CE."
-
If accepted, it transitions to "Create AP Set."
-
-
Move Status to CE (Activity A4):
-
Function:
-
This activity changes the status of the check request to "CE" if not accepted.
-
-
Process:
-
Utilizes a C# script to update the status in the system.
-
Logs activities and errors for tracing.
-
-
Create AP Set (Activity A5):
-
Function:
-
Initiates financial processes for accepted requests.
-
-
Process:
-
Evaluates tool codes; specifically processes those with code "IN."
-
Calls "SACheckMasterRules.ProcessAPSet" to handle financial setup.
-
-
Error Handling:
-
Error (Activity):
-
If any issues occur, an error handler is in place. It notifies the creator and retries the operation indefinitely until resolved.
-
-
Not Accepted (Activity):
-
Function:
-
Rejected requests are routed here.
-
-
Action:
-
Notifies the creator and manages actions based on the rejection.
-
-
Transitions:
-
Transitions between activities are managed based on conditions like acceptance or rejection (activity status of "Y," "A," or "N").
-
Example:
-
If activity status is "N," the transition is from "Creator Approval" to "Move Status to CE."
-
If status is "Y" or "A," the flow moves to "Create AP Set."
-
-
End:
-
Conclusion:
-
The workflow concludes after executing all necessary activities and transitions. No further actions are taken unless a new trigger initiates the process again.
-