TestingOps.ai

Process models (BPMN) · Native connection

SAP Signavio and TestingOps: test scenario candidates from Process Manager models

Process Manager is often where an organisation keeps its approved processes. TestingOps reads those BPMN models through an API user and gives testers and agents the paths through each process as scenario candidates.

  • Native connection
  • Available
Request a demo
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

SAP Signavio and TestingOps in short

The SAP Signavio connection signs in to Process Manager with an API user's e-mail and password and finds BPMN 2.0 models by walking the folder tree, shared folders first.

A linked model is exported as BPMN 2.0 XML only when its revision changed, and each process in it becomes a knowledge-base document with steps by lane, gateway outcomes, boundary events and bounded paths from start to end, marked as candidates for review.

TestingOps only reads Process Manager models; Process Intelligence and Journey Modeler data are not part of this connection.

What it does

What it does for your testing

  1. 1

    Approved models become test design input

    Input
    BPMN models in Process Manager folders
    TestingOps
    Lists them from the folder tree, shared folders first and trash skipped, for linking to a project
    Output
    Scenarios based on the model the business approved, not on a copy
  2. 2

    Pools and lanes become actors

    Input
    Collaboration diagrams with pools and lanes
    TestingOps
    Names each process after its pool and writes the lane next to every step
    Output
    Scenarios that switch roles where the process hands work over
  3. 3

    Revisions decide when to re-read

    Input
    The model's revision in Process Manager
    TestingOps
    Checks the revision on each sync and exports the BPMN only when it changed
    Output
    Candidates that follow model updates without downloading unchanged models

Step by step

How it works

  1. Prepare an API userUse a technical user with an API Edition licence in Process Manager. With SAP Cloud Identity Services, give it a separate API password.
  2. ConnectUnder Integrations → Platforms → Process models (BPMN 2.0) → SAP Signavio, enter your region's API address (for example https://api.eu.signavio.cloud.sap), the API user e-mail and password, and the workspace ID only if the user is in several workspaces.
  3. Pick modelsTest connection lists BPMN models from up to 24 folders. In the project's Knowledge tab, add a source under Process models (BPMN 2.0): pick a model or paste its Signavio model link.
  4. SyncEach sync checks the model's revision and exports the BPMN 2.0 XML only when it changed. Requests are spaced about 1.25 seconds apart to stay under Signavio's request limit.
  5. Review the candidatesAgents and AI case generation read the process documents from the knowledge base; scenarios are written from the candidates you keep.

Connect

Setup

  1. In SAP Signavio, prepare a technical user with an API Edition licence; with SAP Cloud Identity Services, give it a separate API password.
  2. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → SAP Signavio and enter the API address of your region, the API user e-mail, the password and, if needed, the workspace ID (Help → Workspace information). Select Test connection, then Save.
  3. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0) and pick a model, or paste its model link (https://editor.signavio.com/p/hub/model/…).
  4. Select Sync now. Automatic syncs export a model again only after a new revision.
Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → SAP Signavio

Use cases

Use cases

Derive end-to-end scenarios from an order-to-cash model

Trigger
A team links the Process Manager model of its order-to-cash process
Uses
Gateways with named flows and the lane of each step
Agent activity
Writes one scenario per path, naming the role and decision at every step
Result
Draft end-to-end scenarios for review
Condition
A model with more than 30 paths lists the first 30

Retest after a process change is approved

Trigger
A linked model gets a new revision
Uses
The re-exported BPMN on the next sync
Agent activity
Searches the existing scenarios before writing scenarios for new or changed paths
Result
Scenarios for what the revision changed
Condition
TestingOps does not mark which existing cases a model change breaks

Plan handover tests between departments

Trigger
A collaboration diagram with several pools
Uses
Each pool's process and its lanes
Agent activity
Writes scenarios per pool and notes where work moves to another lane
Result
Handover scenarios per process
Condition
Message flows between pools are not parsed, so cross-pool messages are added by the tester

Capabilities

Capabilities and limits

What is read

  • Process Manager models in the BPMN 2.0 stencil set, found in the folder tree (shared folders first, trash excluded): name, revision and the BPMN 2.0 XML export
  • Per process (named after its pool when there is one): start, end, intermediate and boundary events with their type, such as timer, error or message; tasks, including user, service, script, business rule, manual, send and receive tasks; call activities, without following the called process; sub-processes, ad-hoc sub-processes and transactions with their inner steps; exclusive, inclusive, parallel, event-based and complex gateways; sequence flows with their name or condition; lanes; documentation; inline form fields such as camunda:formField
  • Not parsed: message flows between pools, data objects and data stores, text annotations, the DMN tables behind business rule tasks, linked forms, and timer or expression details beyond the event type

What is produced

One knowledge-base document per process: steps with kind, lane and documentation, decisions with their outcomes, exceptions from boundary events, form fields, and numbered paths from start to end marked as test scenario candidates

Where it can write

Nothing in SAP Signavio: models are only listed and exported

How it connects

The SAP Signavio API of your region, signed in as an API user with e-mail and password; TestingOps signs in again when the session expires

Account and permissions

  • A technical user with an API Edition licence; with SAP Cloud Identity Services, a separate API password
  • The workspace ID only if the user belongs to several workspaces
  • A user for whom single sign-on is enforced cannot be used

Limits

  • Paths are bounded: at most 30 per process and 60 steps per path; a loop is followed once and the path ends with "back to" the step it returns to; each outgoing branch of a gateway, parallel and inclusive ones included, becomes its own path, so branches are not combined
  • Paths are candidates for review: no TestingOps scenarios or cases are created from them automatically
  • The list walks up to 24 folders and 500 models; other models can be added by their link
  • Requests are spaced about 1.25 seconds apart, so listing a large workspace takes a while
  • Only Process Manager BPMN models: Process Intelligence, Journey Modeler and other model types are not read
  • Up to 12,000 characters per process section and 200 processes per model; files and exports up to 15 MB

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A finance team links the approved Invoice handling model from Process Manager. The document shows lanes for Accounts payable and Approver, an exclusive gateway "Amount above approval limit?" and an error boundary event on the posting task.

The paths list a direct posting, an approval round and a posting failure. An agent drafts a scenario for each with the role that acts at every step, and the team adds the supplier notifications, which travel as message flows the parser does not read, by hand.

Frequently asked questions

Which Signavio user does TestingOps need?

A technical user with an API Edition licence, signed in with e-mail and password; with SAP Cloud Identity Services, a separate API password. If single sign-on is enforced for the user, or the user has no API licence, Signavio refuses the sign-in.

Does TestingOps read Process Intelligence or Journey Modeler?

No. Only Process Manager models in the BPMN 2.0 stencil set are read. Process mining data, journeys and other model types are not part of this connection.

Why are some models missing from the list?

The list walks up to 24 folders and 500 models, shared folders first, to stay within Signavio's request limits. Any other model can be added by pasting its link.

Are message flows between pools used?

No. Each pool's process is read with its lanes, but message flows between pools are not parsed. Add cross-pool messages to the scenarios yourself.

How often are models read again?

On Sync now and on the automatic syncs. A model is exported again only when its revision changed, so an unchanged model costs one revision check.

Next step

See your approved processes as scenario candidates: request a demo and bring one Process Manager model.

Request a demoMore process models integrations