Enterprise Process Automation (WorkFlow)
A multi-step process with human approval along the way is defined, run and tracked here, and it can coordinate with payments, messages or inquiries.
- Domain
- Enterprise process automation
- Target customers
- Operations managers, internal approval units, process-oriented teams
- Main capabilities
- Multi-step process execution, human approval work queue, graphical process view, integration with platform services
WorkFlow is the engine that runs and monitors the organization's multi-step processes. Any process that has several steps, passes through several people or services and needs human approval along the way is defined, run and tracked in this service. Examples include multi-step approval of a request, routing of work between units, or a chain of actions that must be coordinated with other platform services (such as payment, SMS or inquiry).
The design rests on the principle that each domain's business logic stays in its own specialized service (for example, SMS logic in Pulse and external inquiry logic in ExternalApi). WorkFlow manages only the sequence, timing, waiting for an event or a human decision, and status recording. This separation means that changing an organizational process does not require touching the specialized services.
End users reach this product through the platform's main dashboard: a list of running processes, a work queue page for human tasks to approve or reject, and a graphical monitoring page for each process. A separate section called Studio also exists. It is a technical tool for designers and the technical team, and it is not part of the final product for the business user.
To be candid, the current state of this product is “graphical display and execution of processes,” and it is not yet a complete no-code process builder. The graphical display of an already-defined process, the palette of permitted activities and the panel showing each step's properties are ready and live. Capabilities such as creating a new process from the page, dragging and dropping components onto a canvas, editing fields, and saving and publishing a new version have not been implemented yet. Defining new processes is today the work of the technical team, and not of the business user.
Key capabilities
Execution of multi-step processes
Start a defined process and track it to completion, including waiting for an event, timers, messages to other services and decision branching (yes/no).
Human approval work queue
Every step that needs one person's decision creates a task in the work queue. Claiming, approving or rejecting, and releasing a task follow clear ownership rules (only the user who claimed the task can decide), and decisions are safe against repeated clicks.
Graphical process view
A page that shows the exact map of a process (steps, paths, variables). What you see is exactly what is executed, with no intermediate translation layer.
Behavioral classification of steps
Each step is color-coded by its actual behavior: waiting for a human decision, waiting for an event or external callback, sending a message without waiting, a decision branch, process end, or a synchronous call to another service.
Integration with other platform services
Custom steps to call ExternalApi, Pulse and AccountingCore as part of a process, without separate coding in each service.
Event recording, message queue and error handling
An event inbox and an outgoing message queue for coordination with other services, along with display and limited retry of failed items (incidents).
Permission-based access control
Each section (viewing definitions, work queue, designer) has its own separate permission, and all requests pass through the platform's secure path (authentication, current-company check, request-forgery protection). The browser never contacts the execution engine directly.
Business value
Organizations with multi-step processes usually track their status in email, messages or on paper, and management cannot tell exactly which step a request is stuck at right now. WorkFlow provides a single place to see the live status of each running process, the tasks awaiting a decision, and the history of each step. Because each domain's specialized logic stays in its own service, this product can build processes that connect several platform services without involving every technical team.
What sets it apart
- The map the user sees is exactly what the engine executes, with no intermediate conversion or translation.
- Human decisions are safe against operational error: each task can be decided only once, and task ownership is checked explicitly.
- Each domain's specialized logic stays in its own service. WorkFlow manages only sequence and monitoring, and it holds none of the business rules of payment or SMS.
- All traffic passes through the platform's secure path, and the technical design tool (Studio) is fully separate from the end-user product and limited to admin access.
See this module on demo data
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.