From Process Configuration to Documentation and Test Scenarios

A process definition evolves during implementation and later improvements. When its description and test plan are maintained separately, the team has to keep checking whether they still match the system. AMODIT starts from the current configuration: stages, forms, rules, roles, permissions and available transitions.

AI prepares a draft. The administrator and project team review it, add implementation-specific context and approve it. People remain responsible for the final documentation, test scope and release decision.

The actual configuration is the source

The assistant reads the current process definition in AMODIT. Documentation and test scenarios therefore refer to the same stages, fields, rules and permissions that the team is configuring.

This is particularly useful while a workflow is still changing before production. After a configuration update, the administrator can generate a new draft that reflects the current definition and then review the changes with the team.

AI prepares a process documentation draft

The generated documentation can reflect the elements present in the process definition, including form fields, the process diagram, stages, standard business rules, roles, permissions and reports.

The document provides material for a pre-production review. It can also support handover to process maintenance or audit once the responsible people have checked it and added the organization-specific context.

Test scenarios cover the main path and exceptions

AI uses the same configuration to prepare a structured set of test cases. The set covers the main path, alternative paths, exceptional situations and permission checks.

Each case can identify:

• the category or path,
• the test title and tester role,
• input data,
• steps to perform,
• the expected result.

The output is an editable worksheet. Testers can work from it, while the project team adds cases, test data and assumptions specific to the implementation.

Roles and permissions become testable conditions

The process administrator or designer prepares the draft from the configured workflow. The implementation team and testers then use it during review and execution.

Permissions are also part of the test design. One case can verify the action available to an authorized user, while another checks that a different role cannot access that action. The review can therefore cover both the route through the workflow and access to actions or fields.

AI prepares; people approve

The AI output is a working draft. Before using it, the team:

1. checks it against the current configuration,
2. reviews the main path, exceptions, roles and permissions,
3. adds implementation-specific cases,
4. approves the documentation and test scope,
5. executes the tests and evaluates the results.

This approach combines fast draft preparation with the knowledge of administrators, implementation teams and testers. AMODIT uses configured AI capabilities while the human team remains in control of approval.

Who benefits from this capability?

• Process administrators gain a starting point for documenting the current solution after configuration changes.
• Implementation teams can review the workflow before production and extend the scenarios for the agreed project scope.
• Testers receive a worksheet with roles, input data, steps and expected results.
• Maintenance and audit stakeholders can work with reviewed material based on the actual process definition.

Explore the wider AMODIT BPM platform and the product approach to AI-driven workflow.

Frequently asked questions

Does the team need to write the documentation first?

The actual AMODIT process configuration is the starting point. AI prepares the documentation draft, and a person reviews, completes and approves it.

What is included in the test scenarios?

The scenarios cover the main path, alternative paths, exceptions and permissions. A case can include the tester role, input data, steps and the expected result.

Does AI approve the process for production?

The administrator and project team approve the material and the test scope. They execute the tests and make the release decision.

Can the team add implementation-specific cases?

Yes. The worksheet is a structured starting point that the team extends with cases, data and assumptions relevant to the organization.