Velosity PROCESS
How PROCESS fits daily work
A process gives shared work one visible lifecycle. For example, a quote remains in CPQ while PROCESS tracks whether it is being prepared, reviewed, approved, released, or returned for changes. CPQ still owns quote data; PROCESS records the owner, next action, and decision history.
Use a process for work that crosses people or systems and needs clear ownership, a defined decision path, or a traceable outcome. The same pattern supports approvals, engineering exceptions, procurement requests, and service escalations.
A typical lifecycle
- Start a process for an authoritative record.
- PROCESS enters the initial state and creates its configured work.
- The accountable person completes tasks, records evidence, and takes an authorized transition.
- Each next state creates its own work until the case reaches a terminal outcome.
The current state answers where a case is now. A task describes work within that state. Completing a task records the work; a transition moves the lifecycle.
Choose A Workspace
Use All Processes for a complete case history and available actions. Use My To-Do for work assigned to you or your roles. Use Role Assignments to confirm workflow membership and Task Queue to review team work. Use the Operations Dashboard for current workload patterns and Variation Analysis for completed-case timing. Administrators manage the lifecycle in Process Design → Process Designs.
Record verified external outcomes before progressing a waiting process. A notification or webhook is a handoff attempt, rather than proof that another system or team completed its work.
PROCESS is the tenant-configurable orchestration layer for work that crosses Velosity applications, people, and external systems. It keeps each process in a known business state and allows it to move only through a configured, authorized transition.
Start here
| If you need to… | Go to… |
|---|---|
| Work a process assigned to you | My To-Do |
| Start a process for an existing record | Start a process |
| Inspect a running process | Running processes |
| Review team assignments or open task demand | Team Operations |
| Understand current workload and delays | Operations Dashboard |
| Arrange temporary coverage | Delegations |
Core concepts
- Process design — the reusable, tenant-owned definition of a lifecycle.
- Process — one running instance of a design for an authoritative entity.
- State — the current named business condition, such as
DraftorAwaiting Approval. - Transition — an allowed move between states, initiated by a person, event, or automation.
- Task — work assigned to a user or role while a process is in a state.
- Evidence — an attachment, reference, comment, or captured form data that supports a decision.
PROCESS owns the lifecycle and audit trail. The source application continues to own the business record the process relates to.
Understand What You Are Looking At
Every process page combines the definition of the lifecycle with the facts for one case. The design supplies the possible states, actions, tasks, rules, and forms. The running process supplies the actual entity ID, current state, assignments, evidence, and history. Two cases using the same design can therefore be in different states and show different work.
The current state is the best starting point when answering “what happens next?” Read the open tasks and available actions after it. Tasks tell you what work remains; actions tell you which outcomes you are currently authorized to record. If an expected action is absent, first check that required tasks and information are complete. A rule or role restriction may also apply.
Work With A Process Safely
Before submitting an action, confirm the entity, current state, and requested outcome. Record a short explanation and a durable evidence reference when another person may need to review the decision later. Refresh the page if you have kept it open while other people were working, because the state or assignment may have changed.
Do not create a second process to work around a delay in the first. Find the existing case, identify the missing work, and use its normal, rework, cancellation, or exception path. This keeps the complete business history attached to one process.
Common Questions
Why can another user see an action that I cannot? Actions depend on tenant membership, assigned roles, current state, configured rules, and sometimes task completion. Visibility can differ even when both users can open the same process.
Does completing a task move the process? Usually it records that a unit of work is finished. A separate transition moves the process unless the design explicitly automates that outcome.
Where should I correct source data? Correct the authoritative record in its source application. Then return to PROCESS to complete the work or record the lifecycle decision.