JE APRV

JE APRV

1. Start

• The beginning point of the workflow.

2. District Name Fetch (A19)

• Looks up and stores the required District Name from an internal codes table.

3. User Approval (A1)

• The journal entry creator must review/approve the entry.

• Waits 1 day (retries every 2 days).

• If approved: continues; if not, triggers specific handling.

4. Budget Approval (A3)

• The person “BSI” (likely a budget supervisor or system user) reviews the batch for budget approval.

• Waits 1 week (retries every 2 weeks).

• If approved: moves to End. If not: typically would be handled (possibly not detailed here).

5. Business Office AD Approval (A13)

• Reviewed by a business office admin director.

• Waits 1 day (retries every 2 days).

6. Email Creator Notification (A9)

• If an entry is NOT approved, this step sends the creator an email that their journal entry was not accepted.

• The email explains the batch, the creator, and the reason (inserts NAUID and NANOTE).

7. Not Accepted Handler

• If a journal entry is explicitly rejected (“not accepted”), this activity fetches the user and note from history and stores them in variables.

8. Error Handler

• Catches any errors and notifies the workflow admin of problems with details.

9. No Transition Handler

• If the workflow reaches a state where no valid next step exists, notifies the admin indicating “No Transition”.

10. End

• Marks the completion of the workflow.