Convert WebForm | Models\traveladvance.wdl

Convert WebForm | Models\traveladvance.wdl

Activities in the Workflow

Here is a simplified step-by-step path through the workflow:

1. User submits a travel advance request

• Starts with the "User Approves Travel Report" step, which usually means the person requesting creates and submits their request.

2. Approval Flows

• Departmental Approvals

  • Auth Signers: The request routes to specific authorized signers based on department/unit details.

  • Department Head/Principal Approvers: Range-based or department head approvals by principal approvers.

• User Name Approval: Specific users (like "CC05264", "DK05294", etc.) are assigned as approvers based on the requester's UserID.

3. Special Fund & Grant Checks

• Activities check fund and grant codes, ensuring budget codes match or are not excluded (e.g., funds 21, 82, 88).

4. Batch Posting

• Once approved, the workflow creates a batch in AP for payment, detailing the user, amount, travel number, and so on.

• Batch creation follows a sequence of database records:

  • OHHBatchMaster (batch header)

  • OHBirMaster (more batch details)

  • OHBBatchDetail (itemized amounts)

  • OHTextDetail (adds context like destination, return date, who receives payment)

5. Notifications

• If the advance is approved and ready, AP is notified that it’s time to post and pay.

• If something is rejected, or there’s no valid transition, the creator is notified via email.

• Error Handler: If any error happens in the process, the designated person(s) receives an error notification ("Error from Travel Request").

6. End

• The process finishes once all steps are complete or if a final outcome (success, rejection, error) is met.