Understanding transactions
Transactions explained — definitions, examples, and equivalence to Skills created via Workflows studio
What is a Transaction?
A Transaction is a single, self-contained task that delivers a clear outcome. It's the smallest unit of work created using Workflows studio. This smallest unit of work is called 'Skills'.
Key characteristics:
- Runs end-to-end from trigger to completed outcome
- Operates independently without dependencies
- Produces a definite result (approval, confirmation, data update)
- 1 Transaction = 1 Skill created through Workflows studio
Every transaction has three components:
- Trigger — What initiates it (user request, scheduled job, system event)
- Workflow Logic — Business rules, validations, approvals, integrations
- Outcome — Final result delivered (confirmation, notification, data change)
Transaction vs Process
A Process is a collection of related transactions within the same functional area.
| Aspect | Transaction | Process |
|---|---|---|
| Definition | Single, atomic unit of work | Collection of related transactions |
| Scope | Narrow, single task | Broad, multiple tasks |
| Example | "Apply for Leave" | Leave Management |
| Granularity | 1 Transaction = 1 Skill | 1 Process = Multiple Transactions |
| Independence | Runs independently | Coordinates multiple transactions |
| Outcome | Immediate, definite result | End-to-end business objective |
Examples by Functional Area
HR
| Process | Transactions |
|---|---|
| Leave Management | Apply for Leave, Cancel Leave, Check Balance, Approve/Reject Leave, View History |
| Employee Onboarding | Generate Offer Letter, Collect Documents, Assign Equipment, Create Accounts, Schedule Orientation |
| Profile Management | Update Personal Info, Change Bank Details, Upload Documents, View Payslips |
Finance
| Process | Transactions |
|---|---|
| Expense Management | Submit Expense, Approve/Reject Expense, Check Reimbursement Status, Download Report |
| Invoice Processing | Submit Invoice, Validate Details, Route for Approval, Process Payment |
IT
| Process | Transactions |
|---|---|
| Incident Management | Report Issue, Check Ticket Status, Escalate Ticket, Resolve & Close, Provide Feedback |
| Access Management | Request Access, Approve Request, Revoke Access, Reset Password |
Procurement
| Process | Transactions |
|---|---|
| Purchase Requisition | Create Request, Approve Request, Convert to PO, Track Status, Confirm Receipt |
| Vendor Management | Register Vendor, Update Info, Evaluate Performance, Deactivate Vendor |
Best Practices
- Keep transactions as atomic as possible — One task, one outcome
- Define clear triggers and outcomes — Every transaction needs a start and measurable end
- Name from user's perspective — "Apply for Leave" not "LeaveRequestWorkflow_v2"
- Group logically — Organise related transactions into processes
- Design for reusability — Modularise common validations and integrations
Updated about 11 hours ago