| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Robotic process automation | IT operations and endpoint | 0% | 14 of 68 | 0% | 6 | under 10 labels · led by Microsoft Power Automate at 51% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 1 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 1 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 1 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Deep SAP ERP integration; workflow + RPA in one platform.” GLM 4.7 FlashX · RPA · negative prompt · alternative
“If you're SAP-centric | Limited outside SAP ecosystem” Kimi K2 · RPA · scale prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 10 of the 11 answers that named SAP Build Process Automation and are not a share of its labels.
Thirty-nine of the thirty-nine domain citations in answers naming SAP Build Process Automation came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What SAP Build Process Automation's own pages state, read October 5, 2026: developers.sap.com/tutorials/spa-add-sub-process-automation, sap.com/products/technology-platform/build-process-automation-process-editing.html, sap.com/products/technology-platform/build-process-automation-form-generation.html, sap.com/products/technology-platform/build-process-automation-process-generation.html, sap.com/products/technology-platform/build-process-automation-decision-generation.html. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when SAP Build Process Automation's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as SAP Build Process Automation, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for SAP Build Process Automation by email, built from the raw record of the edition. It shows: