What do you like best about SAP Build?
Rapid test tooling without waiting on backend teams. With Build Apps I can drag-drop a small UI, bind it to an OData/REST service, and ship a functional “test harness” in an afternoon. Our “Return Order Generator” for QA came from this, zero boilerplate, just data variables and logic canvas.
Process Automation that stitches end-to-end flows. Timers, webhooks, approvals, and RPA steps let me seed data, kick off background jobs, and verify statuses before CI starts UI runs.
Reusable artifacts & clean promotion. Pages, data models, and automations are reusable across projects, and promoting between dev -> test -> prod via transports keeps things consistent.
Governance that doesn’t get in my way. Role-based access, change history, and environment-scoped credentials make audits easy while still letting me iterate quickly.
Observability when something breaks. Run logs, input/output traces, and retry queues make it straightforward to pinpoint flaky integrations during test setup.
Tight fit with SAP ecosystems. OData bindings and BTP integration reduce glue code, which means fewer failure points in test scaffolding. Review collected by and hosted on G2.com.
What do you dislike about SAP Build?
Debugging complex flows can feel opaque. Step-through is limited, errors sometimes read like “node X failed” without enough context.
Versioning & reviews aren’t as natural as Git. Collaborating and doing code-style PRs is clunkier in a low-code canvas.
Custom code escape hatches exist, but feel bolted on. Great for 90% cases; the last 10% needs more ergonomic extensibility. Review collected by and hosted on G2.com.