Read the request context
Read the form record that launched the workflow and its required parameters. Identify the author, entity, category and other fields needed for subsequent checks.
Illustrative use case
Check expense requests automatically
Collect the request details, check required fields and conditions, and pass the request to the next step. Data Bridge connects these actions to your company’s rules and systems.
UBC AnalyticsBudget dataSQLEmail
HOW THE WORKFLOW RUNS
UBC AnalyticsBudget dataSQLEmail
01Read the request context
02Enrich and validate
03Choose the next action
04Record the result
THE CHALLENGE
What slows the work down
A request may arrive with missing information, an incorrect category or no clear connection to the budget. A controller manually checks fields, asks for corrections and forwards the record to the responsible person. The same rules may be applied differently across authors and departments.
Financial controllers, expense-process owners and operations teams.A PRACTICAL EXAMPLE
Illustrative scenario: saving a request in a UBC Analytics form triggers a workflow that adds reference information, checks required fields and compares agreed measures. An incomplete request receives a defined status, while a prepared request moves to its next corporate-process action.
HOW THE WORKFLOW RUNS
From the first step to the right action.
Enrich and validate
Match fields to reference data and available budget information. Apply agreed formulas and checks to the prepared dataset before deciding which route it should take.
Choose the next action
Route data according to configured conditions. Update a defined status, prepare a notification or call a subflow that handles a reusable part of the process.
Record the result
Write the prepared changes to the authorised form or system and review the run history. Use the corporate application’s appropriate capabilities for long-running approvals.
VALUE FOR THE TEAM
Make the work repeatable.
- Required information and business rules become a visible route that the process owner can review.
- Reusable checks help departments prepare similar requests consistently before passing them to the next stage.
- Forms, roles, conditions and subflows connect data entry with a defined follow-on action.
Keep control of the result.
- Check author and reviewer permissions, including access to target fields in the corporate application.
- Agree budget-data freshness and handling of concurrent changes before relying on a comparison.
- Distinguish workflow preparation from final approval and verify the capabilities needed for the complete business process.
THE WORKFLOW OUTCOME
Each request receives defined preparation and a clear next step. The process owner can inspect the rules and their execution results.
Capabilities behind this workflowFROM IDEA TO WORKING FLOW
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.