BPM Platform

A form can present the fields, lists and attachments required for a specific case. The data shown and editing rights can depend on the user's role and the current stage, so the right information is available before a decision.

A responsibility matrix can select the recipient or approver from case data such as category, business unit or value. Routing follows current assignments and rules, which designated users can maintain.

Approvals can be collected in sequence or independently from several people. A stage can require every response or a decision from an authorised member of a group, based on clear accountability rules.

An incomplete case can be returned for correction or consultation. The comment explains what is missing, and the response remains with the case. The process configuration defines the recipient and the route back for another decision.

The case owner, contributor and observer can have different rights to view, edit or decide, based on the document category, business unit and an agreed role model. Time-limited cover can be restricted to selected processes and a defined period without widening access for every participant.

Dates and statuses can show when a response, signature or action before the end of a document's validity period is required. A reminder reaches the designated recipient in the context of the case. This mechanism depends on accurate dates, statuses and assignments.

A configured link can connect an amendment to a contract, an invoice to a purchase order, or a preparation task to an onboarding case. Selected data can be reused when identifiers and relationships are set up correctly. Users can see the context and outcome of related work without searching separate folders.

An agreed, current template can be populated with case data to prepare a document, such as a PDF. Selected workflows can also organize scans. This helps reduce manual document assembly, while the responsible person reviews the completed document before it is used.

A case can be routed to a business unit based on its data, intake channel, or the user's selection. Shared rules can operate alongside unit-specific routing and access. If the information does not identify a unit clearly, the case can be sent to a designated person for resolution. This setup depends on a current organizational structure and routing rules.

An import can create a set of separate cases, and selected actions can be run across a group when supported by the action and the available tool. Each item keeps its own status, so users can distinguish completed cases from those that need correction or review.