Workflow Management
Bonita
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Bonitasoft SAS · www.bonitasoft.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Bonita at a glance
- Vendor
- Bonitasoft SAS
- Headquarters
- Not stated on the vendor’s pages as of 28 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 28 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 28 Oct 2026
- Panel verdict
- The AI panel rates Bonita 2/5, the mean of 6 judges. The bench scores Bonita strongest at process design, clustering at 6-7: the captured clinical use-case page documents BPMN 2.0 modelling with deviation paths, escalation rules and approval chains, plus a rules engine encoding protocol requirements and decision criteria per trial phase. how scores are made
- As of
- Vendor pages captured 28 Oct 2026; evaluated by the panel 29 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The bench scores Bonita strongest at process design, clustering at 6-7: the captured clinical use-case page documents BPMN 2.0 modelling with deviation paths, escalation rules and approval chains, plus a rules engine encoding protocol requirements and decision criteria per trial phase. Governance and audit clusters at 4-5 on an execution trail that logs every step, clinical action and deviation with timestamp and full context, generating FDA, EMA and hospital accreditation records in real time. Run reliability sits at a flat 4 — governed error paths and an execution log, with no public information on retries, failure alerting or a status page. The weakest scores are in hosting and portability and sovereignty, both spanning 0-2, and the judges split over thin evidence: for hosting, one credited BPMN 2.0 as a documented notation while the rest found no public information on hosting regions, self-hosting or export; for sovereignty the only fact on record is AI steps naming OpenAI and Mistral, judged differently. Integrations and connectors hold a flat 3, connectors claimed by category only; the pricing page states no prices.
Speaks for it
- BPMN 2.0 modelling with deviation paths, escalation rules and approval chains is documented, alongside a rules engine encoding protocol requirements and decision criteria per trial phase
- Every protocol step, clinical action and deviation is logged with timestamp and full context, with FDA, EMA and hospital accreditation records generated in real time
- Every protocol deviation is logged, escalated and resolved through a governed path
- Lab results, sample tracking and clinical observations feed into the process automatically
- Intelligent document processing extracts and classifies data from clinical forms, lab reports and regulatory submissions before injection into governed workflow steps
Held against it
- Connectors to lab information systems, electronic health records and clinical data platforms are claimed by category, with no connector named by its triggers and actions
- We found no public information on hosting regions, a self-hosted or on-premise edition, the engine's licence, or export of workflow definitions
- We found no public information on roles and permissions, single sign-on, where connection credentials are stored, or separate environments
- We found no public information on automatic retries, failure alerting, runtime or rate limits, or a status page
- No sovereignty attributes are on record, with AI steps naming OpenAI and Mistral and no public information on a data processing agreement or subprocessor list
Best for
- You run clinical trial protocols and need BPMN 2.0 modelling with governed deviation paths and automatic escalation
- You must generate FDA, EMA and ICH compliance records in real time as every step executes
- You need an execution log of every clinical action and deviation that an auditor or works council can inspect
- You want lab results, sample tracking and clinical observations flowing into the process automatically rather than by manual transfer
Avoid if
- You need connectors documented by name into systems such as Microsoft 365, SAP or DATEV, or a public API to start and query workflows
- You must know where workflows and execution logs run, or need a self-hosted edition — we found no public information on hosting or an on-premise option
- Your clinical data may not reach a US model provider without a data processing agreement — AI steps name OpenAI and Mistral, and we found no public information on subprocessors
- You need role-based permissions, single sign-on and separate environments documented before signing — we found no public information on these
The scores
| Criterion | Panel median |
|---|---|
| Process design, forms & approvals | 3 of 5 |
| Connectors, API & on-premise reach | 1.5 of 5 |
| Execution, error handling & monitoring | 2 of 5 |
| Governance, credentials & audit trail | 2 of 5 |
| Hosting options & portability | 1 of 5 |
| European sovereignty | 1 of 5 |
Process design, forms & approvals
Show reasoningHide reasoning
How this is scored
Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.
0 — No human steps at all: neither forms nor approval steps, only machine-to-machine automation.
3 — A visual builder with branching and a simple approval or form step.
5 — A visual designer with conditions and parallel paths, forms and approval steps assigned to roles or groups, and deadlines or reminders for open tasks.
8 — BPMN 2.0 modelling or an equivalent documented notation, versions of a process kept with running instances on their original version, substitutes and escalation chains, multi-stage approvals with four-eyes rules, forms in German with validation and file upload, a task inbox for participants, and a test or simulation mode before publishing.
10 — The process is a governed asset: version history with diff and rollback, migration of running instances to a new version documented, process analytics on cycle time and bottlenecks per step, and the design documented well enough that a business team can maintain it without the vendor.
The Process Owner
The captured clinical use-case page documents BPMN 2.0 modelling with approval chains, deviation paths and escalation rules, so the deadline-then-escalate pattern I need is supported on paper. We found no public information on approvals assigned to roles rather than names, substitutes when an approver is on holiday, or how a changed process version treats the forty requests already in flight. 2
The Integration Engineer
The clinical use-case page documents BPMN 2.0 modelling with deviation paths, escalation rules and approval chains, plus a rules engine enforcing protocol thresholds per trial phase — a real notation with governed exception paths, not just branching. I found no public information on forms, substitutes, keeping running instances on their original version, or a test mode before publishing. 2
The Operations Analyst
BPMN 2.0 modelling of clinical protocols with approval chains, deviation paths, escalation rules and a business rules engine is documented, with exception handling designed in before deployment. We found no public information on forms, task inboxes, substitutes, or versioning of a process that is already running. 2
The Head of IT
BPMN 2.0 modelling with deviation paths, escalation rules and approval chains is documented explicitly, which clears the notation bar I insist on. We found no public information on versioning of a running process, substitutes, forms, a task inbox or a simulation mode, so whether a business owner can change a process without breaking the instances in flight stays open. 2
The Data Protection Officer
BPMN 2.0 modelling of clinical protocols with deviation paths, escalation rules and approval chains is documented, plus a business rules engine encoding regulatory thresholds per trial phase and exception handling built in before deployment. I found no public information on forms, substitutes, task inboxes or versioning of processes that are already running, so I place this between the mid and high anchors. 2
The Skeptic
BPMN 2.0 is the documented notation, with deviation paths, escalation rules, approval chains and a rules engine encoding thresholds per trial phase — more than a generic visual builder. We found no public information on versioning of processes already running, substitutes, forms with validation, a task inbox, or a test mode before publishing. 2
Connectors, API & on-premise reach
Show reasoningHide reasoning
How this is scored
Reaching the systems a European company actually runs: maintained connectors judged by name rather than count, a generic HTTP and webhook step, custom connectors, and a way to reach systems behind the firewall without opening it.
0 — No connectors beyond email, and no API or webhook step.
3 — A catalogue of connectors to common SaaS tools, or webhooks and an HTTP step to call other systems.
5 — Named connectors with their triggers and actions documented, including Microsoft 365 or Google Workspace, a generic HTTP/REST step with inbound webhooks, and an API to start or query workflows.
8 — Connectors to an ERP or accounting system common in DACH (e.g. SAP, DATEV, Microsoft Dynamics), custom connectors buildable from an OpenAPI description or code, an on-premise agent or self-hosted runner reaching internal databases and file shares, SOAP and database steps, and connector maintenance ownership (vendor, partner or community) stated.
10 — Integration is engineered: a versioned public API with a deprecation policy, connector changelogs, rate limits per connector published, event-driven triggers rather than polling where the source allows it, and the vendor maintaining the German-market connectors (DATEV, SAP, ELO or d.velop) itself.
The Process Owner
The pages show connectors for laboratory information systems, electronic health records and clinical data platforms, and AI steps via OpenAI and Mistral. We found no public information on connectors to Microsoft 365, SAP or DATEV, on a generic HTTP or webhook step, or on a documented API to start or query workflows, which is what my approvals would need to reach our ERP. 2
The Integration Engineer
Integration is claimed by category — lab information systems, electronic health records and clinical data platforms feed the process automatically, and OpenAI and Mistral are named for AI steps — but no connector is documented by name with its triggers and actions. I found no public information on a generic HTTP or webhook step, an API to start or query workflows, custom connectors, or an on-premise agent reaching systems behind the firewall. 2
The Operations Analyst
Connections to lab information systems, electronic health records and clinical data platforms are claimed, plus intelligent document processing and OpenAI and Mistral behind AI steps. We found no public information on named connectors with documented triggers and actions, a generic HTTP or webhook step, a workflow API, or a way to reach systems behind the firewall. 2
The Head of IT
The captured page documents connectors to lab information systems, electronic health records and clinical data platforms, plus AI providers OpenAI and Mistral — but these are categories, not named maintained connectors. We found no public information on a generic HTTP or webhook step, a public API, custom connectors, or any reach to ERP or accounting systems common in DACH. 2
The Data Protection Officer
The captured page shows connectors into lab information systems, electronic health records and clinical data platforms, and AI steps through OpenAI and Mistral. I found no public information on documented triggers and actions, a generic HTTP or webhook step, an API to start workflows, or any on-premise reach. 2
The Skeptic
The only integration evidence is a category claim — lab information systems, electronic health records and clinical data platforms connected into one workflow — plus AI steps naming OpenAI and Mistral. No connector is named with its triggers and actions, and we found no public information on a generic HTTP or webhook step, a public API, or a way to reach systems behind the firewall. 2
Execution, error handling & monitoring
Show reasoningHide reasoning
How this is scored
What happens when a step fails at 3 a.m.: retries, error paths, alerting, an execution history someone can search, limits on runtime and throughput, and a status page that admits incidents.
0 — Nothing runs unattended: the product executes no automated workflows whose runs could fail or be monitored.
3 — Failed runs marked with a notification, and a history of recent executions.
5 — Automatic retries or an error path, an execution log with input and output per step, failure alerts by email or chat, and runtime or rate limits documented.
8 — Configurable retries with back-off and replay of a failed run from the failing step, queueing and concurrency controls, execution history retention stated per plan, monitoring exportable to the customer's own tools, and a public status page with incident history and an uptime commitment.
10 — Operations are designed for production: an SLA with service credits, horizontal scaling or high-availability setup documented for self-hosted installs, dead-letter handling, end-to-end tracing across workflows, and post-incident reports published.
The Process Owner
The captured pages promise full exception handling built in before deployment and a record of every protocol step and deviation with timestamp and full context, which reads as designed-in error paths and an execution log. We found no public information on automatic retries, alerting when a run fails overnight, throughput or runtime limits, or a status page with incident history. 2
The Integration Engineer
Deviation handling works as a governed error path — every deviation logged, escalated and resolved — and the audit trail records every step with timestamp and full context in real time, which functions as an execution log. I found no public information on retries with back-off, replaying a failed run from the failing step, failure alerts by email or chat, runtime or rate limits, or a status page. 2
The Operations Analyst
Deviation paths, escalation rules and full exception handling are built in before deployment, and every step is logged with timestamp and full context, so a failed run has a governed path and a record. We found no public information on retries, replay from the failing step, alerts reaching a chat channel, runtime or throughput limits, or a status page. 2
The Head of IT
Every protocol step, clinical action and deviation is logged with timestamp and full context, and exception handling with escalation is built into the model before deployment — that is a real execution trail and a process-level error path. We found no public information on automatic retries, operator alerting when a run fails, runtime or throughput limits, retention of the history, or a public status page. 2
The Data Protection Officer
Every protocol step, clinical action and deviation is logged with timestamp and full context, and each deviation is escalated and resolved through a governed path — that is an error path with a traceable execution history. I found no public information on retries, failure alerts, runtime or rate limits, or a public status page. 2
The Skeptic
Exception handling is designed in before deployment, deviations are escalated through a governed path, and every step is logged with timestamp and full context — a real error path and execution log. We found no public information on automatic retries, failure alerting, runtime or rate limits, retention of execution history, or a status page. 2
Governance, credentials & audit trail
Show reasoningHide reasoning
How this is scored
Keeping automation from becoming shadow IT: roles and permissions, SSO, where connection credentials are stored, separate environments with controlled publishing, an audit trail of changes and approvals, and what the execution log retains of the payload. An approval record is also a record of employees' behaviour (BetrVG § 87 (1) 6), so what the trail captures matters to a works council.
0 — No user management: one account per person or one shared login, with no team workspace.
3 — Admin and member roles with shared team folders or workspaces.
5 — Role-based permissions per workflow or folder, SSO via SAML or OIDC, credentials stored encrypted and usable without being revealed, and an audit log of workflow changes.
8 — Separate development, test and production environments with a publishing approval, SCIM provisioning, external secret stores supported, payload redaction or logging off per workflow, configurable execution data retention, and the audit trail exportable — with the fields it records about users described.
10 — Governance a works council and an auditor can both sign off: field-level masking of personal data in logs, delegated administration per department, a central inventory of every workflow and connection with its owner, certifications published (ISO 27001 or SOC 2), and documentation of what the platform records about individual users.
The Process Owner
The execution audit trail is the strongest part: every protocol step, clinical action and deviation is logged with timestamp and full context, and compliance records for FDA, EMA and hospital accreditation are generated in real time. We found no public information on role-based permissions, single sign-on, where connection credentials are stored, separate environments with controlled publishing, or what the trail records about individual employees — the question my works council will ask first. 2
The Integration Engineer
The trail itself is the strength: every protocol step, clinical action and deviation logged with timestamp and full context, with FDA, EMA and hospital-accreditation records generated in real time — exactly the record of employee behaviour a works council cares about. I found no public information on roles and permissions, SSO, where connection credentials are stored, separate environments with publishing approval, export of the trail, or security certifications. 2
The Operations Analyst
Every action generates a compliance record to FDA, EMA and ICH standards, and each step is logged in real time with timestamp and full context — an execution trail a works council could inspect. The documentation stops at the trail itself: we found no public information on role-based permissions, SSO, credential storage, separate environments, or log retention and export. 2
The Head of IT
The audit trail is described in exactly the compliance terms a works council would probe: every action logged with timestamp and full context, with FDA, EMA and hospital accreditation records generated in real time rather than assembled afterwards. We found no public information on SSO, role-based permissions, separate test and production environments, where credentials are stored, or export of the audit trail — so the governance half of my checklist is undocumented. 2
The Data Protection Officer
The execution trail records every step, action and deviation with timestamp and full context and generates FDA and EMA records in real time, and AI steps are described as running in fully auditable execution paths — that is the record a works council and an auditor will read. But "full context" means the log keeps a copy of the payload, and I found no public information on masking, retention, roles, single sign-on or where connection credentials live. 2
The Skeptic
The execution audit is the strongest evidence on the pages: every step, clinical action and deviation logged with timestamp and full context, with FDA and EMA records generated in real time. We found no public information on roles and permissions, SSO, where connection credentials are stored, separate environments, or how long the log is retained. 2
Hosting options & portability
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Where the engine runs and whether the workflows can leave: cloud regions, self-hosted or on-premise editions, the licence of the engine, and export of workflow definitions in a format another tool or a later version can read.
0 — Workflows cannot be exported in any form and live only in the vendor's cloud.
3 — Cloud hosting with the region named, and workflows exportable as a file the same product can import.
5 — An EU cloud region available, workflow definitions exportable as documented JSON or BPMN 2.0, and an API to read definitions and execution history.
8 — A self-hosted or on-premise edition with its system requirements documented, workflow definitions versionable in Git, the engine's licence published, and a documented migration path between cloud and self-hosted in both directions.
10 — The customer owns its automation: an open-source or source-available engine, definitions in an open standard executable elsewhere, air-gapped installation supported, and a stated exit process that hands back definitions, credentials metadata and execution history in documented formats.
The Process Owner not rated — no public information
We found no public information on where the engine runs, a self-hosted or on-premise edition, the licence of the engine, or export of workflow definitions in a format another tool could read. The captured pages are the vendor home page and a clinical use-case page, and neither addresses hosting or portability. 1 2
The Integration Engineer not rated — no public information
We found no public information on hosting or portability: nothing on cloud regions, a self-hosted or on-premise edition, the engine's licence, or export of workflow definitions in a format another tool could read, on either captured page. 1 2
The Operations Analyst not rated — no public information
We found no public information on where the engine runs, a self-hosted or on-premise edition, the engine licence, or export of workflow definitions in a format another tool or a later version could read; the captured pages were the vendor home page and a clinical use-case page. 1 2
The Head of IT not rated — no public information
We found no public information on cloud regions, a self-hosted or on-premise edition, the engine's licence, or export of workflow definitions in BPMN or documented JSON. Both pages we read were silent on hosting and on any exit path for the definitions and history, so this dimension is unknown rather than answered. 1 2
The Data Protection Officer not rated — no public information
We found no public information on hosting regions, a self-hosted or on-premise edition, the engine licence, or export of workflow definitions in any format. The pages we read list product modules but say nothing about where the engine runs or whether workflows can leave it. 1 2
The Skeptic
Process definitions are modelled in BPMN 2.0, a documented standard notation, and that is the only fact touching portability. We found no public information on hosting regions, self-hosted or on-premise editions, the engine's licence, or export of workflow definitions in any format. 2
European sovereignty
panel opinion
n/r
n/r
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where workflows execute and where execution logs with their payload copies are stored, and who the subprocessors are — including the AI model providers behind any AI steps. Independently sourced by the sovereignty pipeline. A self-hosted edition counts only for the data that actually stays on the customer's servers.
0 — Proven non-EU throughout: non-EU vendor and contracting entity, execution outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, while an EU contracting entity and EU execution are not shown, or an EU region is an option under a non-EU contracting entity.
5 — EU execution and log storage stated (as standard or selectable) and an EU contracting entity or EU representative, with a data processing agreement; parts of the chain such as AI steps, support access or telemetry may run outside the EU.
8 — EU execution on named infrastructure, EU contracting entity, subprocessor list published with locations including AI providers, a DPA covering execution payloads, and a self-hosted option that sends no workflow data to the vendor.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, AI steps runnable on European or self-hosted models, certification published, and a self-hosted edition that works without any call home.
The Process Owner
The only fact bearing on sovereignty is that AI steps run on the named model providers OpenAI and Mistral, with no locations or stated role in the processing chain. We found no public information on where workflows and their execution logs are stored, the contracting entity's location, a data processing agreement, or a published subprocessor list. 1 2
The Integration Engineer not rated — no public information
No sovereignty information is on record from the captured pages: nothing on the contracting entity's location, where workflows and execution logs are stored, subprocessors, or a data processing agreement. The nearest detail is that OpenAI and Mistral are named as AI connector providers, with no locations or processing terms given. 1 2
The Operations Analyst not rated — no public information
No sovereignty attributes are on record: the captured pages give no contracting entity, execution region, log storage location, subprocessor list or data processing agreement. The only adjacent detail is AI steps naming OpenAI and Mistral, with no locations or terms attached. 1 2
The Head of IT
The only fact bearing on sovereignty is that AI steps run on OpenAI and Mistral; no locations or processing terms are given for them. We found no public information on the contracting entity, where workflows and execution logs run, a data processing agreement, or a published subprocessor list with locations. 2
The Data Protection Officer
The only fact bearing here is that AI steps are offered through OpenAI and Mistral for a clinical use case — clinical data sent to a non-EU model provider is precisely the transfer a works council will ask about. I found no public information on where workflows and their execution logs are stored, the contracting entity, subprocessor locations, or a data processing agreement, and no sovereignty attributes were on record. 2
The Skeptic
The one proven fact is that AI steps use OpenAI and Mistral — one US and one French provider — so a buyer at least knows where AI payloads can go. No sovereignty attributes were on record: we found no public information on the contracting entity's location, where workflows and logs execute, a data processing agreement, or a subprocessor list. 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the monthly cost of their own processes from public pages alone: what the billing unit is (task, operation, execution, run, user or flow) and what counts as one, the allowance per tier, overage prices, and the cost of premium connectors, self-hosting, environments and AI steps.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one tier priced, with the rest on request.
5 — Prices public for each tier with the billing period, the billing unit named and the allowance per tier given.
8 — Every tier priced publicly with its unit defined (what counts as one task or execution), allowance and limits, overage priced per unit, premium connector and add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.
10 — Complete price computability: the monthly cost derivable for a given number of workflows, runs and steps per run, with a published calculator or worked examples, every add-on and overage on a public page, and the effect of loops and retries on the count explained.
The Process Owner
A free start is offered and a pricing link exists, but no price figure for any paid tier appears in the captured pages — no billing unit named, no allowance per tier, no term or VAT treatment. As the person releasing the invoices, I cannot even begin to compute the monthly cost of my approval flows without a sales conversation. 2
The Integration Engineer
The captured page shows a pricing link but states no figures, and the only public price point is a "Start for free" entry, with the rest behind a demo request. A buyer cannot compute any monthly cost from what is public here — no billing unit, allowance, overage or add-on prices appear. 2
The Operations Analyst
A pricing link and a "Start for free" option are shown, but the captured page states no prices, and no tier, billing unit or allowance appears on the pages we read. From this alone a buyer cannot begin to compute the monthly cost of their own processes. 2
The Head of IT
The captured pricing page states "Pricing link present; no prices stated on this page", and the surrounding call to action is "Ask for a demo" alongside a free start. No tier, billing unit, allowance or overage is priced publicly, so a buyer cannot compute a monthly cost from what we read. 2
The Data Protection Officer
The captured pricing page shows a pricing link with no prices stated, and beyond a free start everything goes through asking for a demo. No monetary tier, billing unit or allowance is public, so a buyer cannot compute a monthly cost from the pages read. 2
The Skeptic
The captured pricing page shows a link but states no prices, and the only commercial signals are a free start and a request for a demo. No billing unit, tier allowance or overage price is public, so a buyer cannot compute even a rough monthly cost from these pages. 2
Questions about Bonita
Is Bonita European?
Not determined: the vendor’s pages as captured do not say where Bonita is based.
Where does Bonita store data?
Not stated on the vendor’s pages as of 28 Oct 2026.
Does Bonita have a free plan?
Not stated on the vendor’s pages as of 28 Oct 2026.
What are the best alternatives to Bonita?
As of 28 Oct 2026, the panel rates Tray.ai (3/5), Frends (3/5) and Appian (3/5) highest among the other 19 Workflow Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Frends (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Bonita alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 28 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 21 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (2)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.bonitasoft.com Checked 28 Oct 2026 Details →
- 2 Process design, forms & approvals — found from sitemap www.ofelia.com Checked 28 Oct 2026 Details →