Approves expense reports within policy by rule and routes the exceptions to the manager and then finance, with the decision returned to Workday within seconds.
Workers, organisations, positions, time off and expense reports are read in place through Workday's SOAP and REST web services and through Reports-as-a-Service for lists. The rows stay in Workday.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Expense report | Resource_Management: Get_Expense_Reports | Expense_Report.Status (status) · Expense_Report_Line.Expense_Item (policy) · Expense_Report.Total_Amount (amount) · Expense_Report.ID (number) | live through the API |
| Employee | Human_Resources: Get_Workers · RaaS worker report | Worker.Employee_ID (id) · Worker.Legal_Name (name) · Worker.Supervisory_Organization (org unit) · Worker.Position_ID (position) | live through the API |
| Cost center | Financial_Management: Get_Cost_Centers · Get_Organizations | Cost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company) | live through the API |
| Budget line | Financial_Management: Get_Budgets · Get_Budget_Amendments | Budget.Budget_Structure (object) · Budget_Line.Amount (amount) · Budget.Fiscal_Year (year) · Budget.Budget_Name (version) | live through the API |
In plain words: An expense report submitted in Workday whose lines carry a policy flag, or whose total is above 1,000.
The criterion runs in Workday through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.
# start criterion in Workday fields Expense_Report.Status = 'submitted' and (Expense_Report_Line.Expense_Item = 'exception' or Expense_Report.Total_Amount > 1000) # the same criterion in canonical fields {expense.status} = 'submitted' and ({expense.policy} = 'exception' or {expense.amount} > 1000)
Writes go through the released web-service operations (for example Submit_Expense_Report, Request_Time_Off, Hire_Employee) under an integration system user with the security groups the operation needs. Each call returns the Workday ID, and the app records it beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Expense report | approval, return or rejection written to the Workday business process step with the note; the report moves to payment or back to the traveller | Submit_Expense_Report · Approve_Business_Process |
Each write stores the identifier Workday returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in Workday.
The screens read through handlers that leave the rows in Workday. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.