TO.NET_APPROVAL

TIME CARD ONLINE

1. Start Activity

   • Purpose: Initializes the workflow. It does not execute any particular action but sets up the conditions for the next steps.

2. A22 - Load Email Address

   • Action: This activity fetches the email address of the entry clerk from the user database using their user ID.

   • Result: If found, it loads the email into the system for notification purposes.

3. A8 - Generic Task List Assignment

   • Description: Assigns tasks related to the workflow. This may involve listing tasks for review or approval.

   • Wait Time: It waits up to 3 months before automatic retries.

4. A21 - Approve TimeCards

   • Action: Executes the main logic for approving timecards using C# code.

   • Details: It updates relevant records in IFPYWfMaster and IFPYTcImp tables to mark timecards as approved.

5. A23 - Get Approver Notes

   • Purpose: Collects any notes from approvers related to the decision-making process.

   • Details: These notes are stored and can be used for future reference.

6. A14 - Entry Clerk Approval Notify

   • Action: Sends an email notification to the entry clerk to inform them that their timecards have been approved.

7. A13 - Entry Clerk Rejection Notify

   • Action: Sends an email notification to the entry clerk, stating that corrections are needed in their timecards.

   • Details: It includes notes for the necessary changes.

8. A24 - Get Rejection Notes

   • Purpose: Gathers notes explaining why timecards were rejected.

   • Action: Appends these notes to rejection notifications.

Transition and Decision Points

• From Start to A22: Triggered if the approval code indicates initial submission.

• From A22 to A8: Proceeds to task assignment if the email address is successfully loaded.

• From A8 to A21: Advances to approve timecards.

• From A21 to End: Ends if no further actions are required, or continues to notification steps based on entries.

• Rejection Handling: Moves to A24 if timecards are not accepted. This step gathers and actions based on rejection notes.

• Finalization: Either ends the workflow after notifications or loops for further actions if needed.

Error Handling

• Error Activity: Catches errors in the workflow and provides a trace for debugging. It does not interfere with regular processing unless a critical error is detected.

Closing Activities

• End Activity: Marks the completion of the workflow. It doesn't perform any additional tasks but functions as a logical endpoint.

Design Aspects

• Positioning: Activities and transitions are visually placed with specific coordinates (xPos, yPos) to represent their role in a graphical interface.

Summary

This workflow is structured to efficiently handle timecard approvals with multiple checks and balances, ensuring all processes are accounted for, and stakeholders are informed through notifications. Its design is robust, with a focus on reducing redundant processing and preventing conflicts within the workflow system.