NewSAPUI5 and OpenUI5
Domain Integration & Messaging

Today
1 change
Destinationscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the entry is in the graph, so the name links to it and not to its repository (WRITING section 3.6).Capability,
Mon 19
1 change
Destinationsecosystems revisedui5-middleware-destination was staged in intake-20261019-bestofui5 under ui5-build-tooling; its drafter left out a destinations edge because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Sat 17
1 change
Configure Journal Entry Posting Approval from Store Template in Build Process Automationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,

Sun 27
1 change
Destinationscore coverage revisedP1 backfill 2026-09-27: the paragraph shared no page with the runtime edge because it had no page at all. capire documents the connectivity component under Outbound Authentication; the paragraph now rests on it and on the pages the edge cites.Capability,
Sat 26
1 change
Configure Journal Entry Posting Approval from Store Template in Build Process AutomationpublishedWalks through deploying SAP's Journal Entry Posting Approval template from the SAP Build Process Automation Store against an on-premise S/4HANA system that has no Secure Network Connection: destinations for S/4HANA via Cloud Connector, for SAP Document Management service, integration option to hold the approval's supporting documents, and for the BPA service and its SMTP mail. It then swaps the template's SNC action groups for basic-connection BAPI calls and deploys the approval's UI5 applications so the task lands in My Inbox, with a Desktop Agent registered to run the unattended document-check and document-post automations.Blog,
The last 30 days. Older changes stay in each entry's history.