Start A Process
Start a process step by step
- Open Start a Process from the Processes area.
- Choose the design that matches the record and business purpose.
- Enter the entity ID exactly as it appears in the source application.
- Create the process, then open it to review the initial state and work.
The entity ID identifies the authoritative record. PROCESS coordinates its lifecycle and does not become the owner of that underlying record.
When a start is unavailable
The design may not be active for the tenant, your role may lack start permission, the design may lack a valid initial state, an administrator may have configured it to start automatically, or an active duplicate may already exist for the same design and entity. Locate the existing process before starting another. Starting a second case to bypass a waiting case loses the history that makes the process useful.
Start after the source record contains enough information for the first owner. Add supporting context immediately. Ask an administrator to configure recurring starts from another Velosity module.
Choose Start a Process to create a process for an existing business record. Select an active process design and enter the authoritative entity ID from the source application.
PROCESS checks that the design is available to the tenant, that you can start it, and that an active duplicate is not already running for the same design and entity. On success, the new process begins in the design’s initial state.
Before starting
- Confirm the entity ID belongs to the correct source record.
- Use the design whose entity type and purpose match the work being coordinated.
- Check whether a current process already exists for that record.
- Start a process only after the source application has performed its own business validation.
Administrators configure which roles can start each design. If no start roles are configured, any active tenant member can start it.
Automatically Started Processes
Some recurring work starts on an administrator-defined daily, weekly, or monthly schedule. A scheduled design does not appear under Start a Process, because creating it manually could duplicate the scheduled case, its tasks, and its notifications.
When its scheduled time arrives, PROCESS creates the case in the same initial state as any other process and creates the configured first-state work. The process history identifies the automatic start and its scheduled occurrence. Find the resulting case under All Processes or find work assigned to you under My To-Do.
If an expected scheduled process is missing, do not substitute another design or create an unrelated case. Ask a process administrator to review the schedule status and execution history. Administrators can run a schedule immediately when recovery is appropriate.
Choose The Correct Design
Read the design name and purpose before entering an entity ID. Similar designs may coordinate different entity types, regions, approval levels, or business outcomes. Starting the wrong design can create tasks and notifications for the wrong team. If the correct design is unclear, confirm it with the process owner before creating the case.
Copy the entity ID from the source application when possible. Do not substitute a display name, customer name, or informal reference unless that value is the documented authoritative identifier. After creation, use the link back to the source record to verify that the new process points to the intended entity.
What Happens After Creation
PROCESS records you as the initiator, selects the configured initial state, and creates any work associated with entry into that state. This can include role tasks, direct assignments, timers, and notifications. Open the new process immediately and check that its first owner has enough context to begin.
Starting a process does not itself approve, validate, or change the source record. Those outcomes occur through the configured lifecycle and the connected application’s own business rules.
Troubleshoot A Failed Start
If PROCESS reports a duplicate, search by entity ID and design and continue with the existing active case. If the design does not appear, confirm that it is published, active for the tenant, and applicable to your role. If creation succeeds but expected work is missing, review the initial state and contact an administrator with the process ID, design, entity ID, and expected assignment. Those details allow the configuration to be investigated without creating another case.