Skip to main content
The extension hooks into BC’s standard Workflow framework to make three HR documents approvable: Overtime Journal, Salary Advance, and Loan Application. Everything below happens automatically — this page exists to demystify what was registered and to give you a checklist when something doesn’t appear where you expect it.

​
What the extension registers

On install (and on every upgrade), Workflow Setup Event HAC (Codeunit 70003105) subscribes to four standard BC workflow events and adds:

​
Three workflow categories

Categories are filters in the Workflow Templates page that let you find HR templates quickly.

​
Three workflow templates

Templates are read-only blueprints. To use one, you select it from Workflow Templates and click New Workflow from Template — that copies it into the active Workflows list where you can edit conditions and approvers.

​
Table-to-Approval relations

A relation between the Over Time Journal HAC table and the standard Approval Entry table is inserted, so that approval entries can be looked up from the document and vice versa.

​
Event-response predecessors

Five workflow events are registered for each of the three documents (send-for-approval, set-status-to-pending, cancel-all-approvals, open-document, create-approval-requests). This is the plumbing that lets the BC workflow engine know which response code to fire when one of the HR documents emits an approval event.

​
When this runs

You should never need to run this manually.

​
Approval User Setup

The workflow templates are useless until you have at least one Approval User Setup record. This is standard BC, not part of the extension, but it is a hard prerequisite.
  1. Open Tell Me → Approval User Setup.
  2. Click New and fill in:
    • User ID — the BC user who can approve
    • Approver ID — who approves on this user’s behalf when their own approval is needed
    • Approval Administrator — tick for at least one user (often the HR manager)
    • Salesperson Code / Substitute — optional
  3. Repeat for every user who will appear as an approver in HR workflows.
Without these records, sending a document for approval throws “Approver ID must have a value in Approval User Setup”.

​
Linking the workflow to a user

Each HR document type also relies on the employee’s Direct Manager to know whom to route the approval to. Verify on every employee card:
  • Direct Manager is filled in.
  • Related User is filled in — this is the BC user account that will receive approvals on the dashboard.
See Approvals for the end-to-end walkthrough.

​
Troubleshooting

​
Object reference