In ReadiNow, a Process Run represents an active or completed instance of a Process execution. When a Process is launched—either manually or through automation—it creates a Process Run record that tracks the state and progress of that particular execution.
Key elements of a Process Run include:
- Instance Tracking:
- Each run is a unique execution of the defined Process structure (stages, blocks, steps).
- It captures all user inputs, task completions, and transitions.
- Launch and trigger details
- Launch Source: Manual or Triggered
- Initiating Person: The person who launched the Process
- Launched Date: The date the Process Launched
- End Date: The date the process completed its final step or was cancelled.
- Statuses:
- Running: Active process with steps still pending.
- Complete: All steps are completed or skipped.
- Error: A step or action encountered an issue.
- Cancelled: Processes that have been cancelled mid-run
- Not Started: The run exists but hasn't executed any steps yet.
- Components Within a Run:
- Run Steps: The specific steps executed during this run.
- Run Actions: The user actions taken during the step (e.g., submit, approve).
- Run Status: Derived from the most recent action or failure in the step sequence.
- Visual Indicators:
- Users can see the progression through chevrons or step lists, with indicators like “In Progress,” “Done,” or “Error.”
- User Experience:
- Users only see steps/tasks assigned to them.
- When their tasks are done, they see a “You’re All Done” or “You’re All Caught Up” message.
- Debug and Admin Controls:
- Admins can launch runs in debug mode to test processes step-by-step without actual assignments.
These runs allow auditability, traceability, and user accountability throughout business workflows.
Process Runs Screen
The Process Runs screen shows a list of all Process Runs within the tenancy.
Individual Process Runs can be viewed by selecting them from the list to view mode details