Workflows — from request to recorded result

A workflow owns the whole process. A work item is a participant's assignment inside it. Documents preserve the exact evidence; the timeline connects requests, decisions and results.

Complete a process

1. Sign in to your company workspace and open the permitted start action.
2. Choose an available process. Review the company and object context supplied by the server.
3. Provide the requested facts and documents, then submit once. Follow the started process rather than creating a duplicate after a slow response.
4. The assigned participant opens the work item, reviews the request and evidence, and uses the permitted decision or action.
5. If correction is requested, the requester follows the return path and supplies the revised evidence.
6. A successful business action is recorded with the workflow transition. Both participants can inspect the result allowed by their scope.

The exact action labels and route belong to the selected process. An approval is not a generic promise that every later step has already succeeded.

When the path changes

Cancellation follows the process policy. An already applied business action may need a linked compensating process. A retry uses the existing process and its permitted recovery command. Missing participants, evidence, permissions, capacity or dependencies appear as an actionable blockage; a hidden button is not the access-control mechanism.

Changing company, object or a parent selection may invalidate dependent choices. Review the recalculated options before submitting. If there are no permitted options, ask your company administrator to correct the assignment or configuration.

Administration

Railbase Studio manages supported company process configuration. Installation work uses separately authorised system workflows. A deployment operator does not receive company decision authority merely by administering the server.

First-process acceptance

Use separate requester and reviewer accounts. Verify submit, return, resubmit, decision, cancellation, denied access and recovery. Record the role, actions, visible result and persisted business outcome. A completed page load alone does not prove the process works.