Workflow Studio — 独自の承認ルートを構築する

Workflow Studio is a Railbase module, not a separate product. It configures supported workflows inside your Railbase installation.

Workflow Studio is the process editor inside Railbase Studio. Use it to build your own supported coordination and approval routes, or adapt an available Product process. Business Suites add ready-made domain workflows and expert workspaces; they use the same organization, authority, documents and evidence foundation rather than a separate approval system.

Two kinds of work

Adapt a Product process. An authorised company administrator uses the extension points supplied by the Product: permitted participant slots, evidence, routing, conditions and other declared settings. The underlying business action and its mandatory rules remain protected.

Create a coordination process. A company can organise human work, documents and decisions using the supported coordination model. This does not grant arbitrary business-record writes or permission to author executable domain logic.

From draft to published process

1. Open the process library in your company context and select an available process or permitted coordination template.
2. Inspect its purpose, route, participants, evidence and locked requirements.
3. Create a draft and select participants from the server-provided company sources. If a required position or body is missing, complete its governed organisation change first.
4. Change the permitted settings. Recheck dependent selections after a parent value changes.
5. Validate the route and resolve missing participants, evidence or policy conflicts.
6. Submit through the required approval/publication path. Review the published revision before starting new work.
7. Run the process with the affected roles and inspect its recorded outcome.

Drafts do not silently change active company behaviour. Running processes retain their pinned effective revision. Updating a Product must check compatibility with the company's published configuration.

Boundaries

Studio cannot weaken mandatory segregation of duties, evidence, company/object access, licence conditions or protected business rules. It does not replace a Product release, implementation acceptance or an authorised human decision.

Follow the workflow lifecycle · Plan implementation

Publish Acme's first route

Prepare a supported coordination route for the Acme training request: Tom submits the quotation and project reason; independent assigned reviewers can return it and decide the corrected version. Validate and publish before starting. This Core exercise coordinates a decision; it cannot author an arbitrary AP posting or Treasury payment. Later Accounting work uses the Product's prepared domain workflow and protected actions. Keep the published revision pinned to the request.