SAP Build Code with Joule and the CAP, UI5 and Fiori MCP Servers

Keep this: job aid

Generated CAP and Fiori apps: review card

• Check entitlements first: build-code or build-default plan, AI features enabled, Build Code Developer role.
• No personal data in project files; Joule uses them as context.
• Model checklist: cuid keys, managed, compositions for items, enum status, @mandatory and @assert, @requires or @restrict.
• Ask for edge-case sample data; check plausibility against real prices and limits.
• UI: review LineItem, SelectionFields, HeaderInfo, Facets and labels; authorization lives in the service.
• MCP servers: approve centrally, pin versions, know network calls and telemetry, review .mcp.json like code.
• Rules file: use CAP model search first, run npm test after changes, stop before authorization edits.
• Tests: add negative, boundary, state, authorization and composition tests; break the code to prove each one.
• Label generated code in pull requests; Nadia approves authorization changes.
• Same route as all code: CI pipeline, CMC_DEV to CMC_TEST to CMC_PROD, Priya forwards after sign-off.