Checking the Connection
Every app shows a warning strip with the first problem it finds for what it shows; assistants read the same checks; a broken destination never blocks the subscription.
Draft brief for authors. Replace with the final text; keep the task-page structure.
Page type: Task · Audience: Administrator
Contains
- The status strip in Manage Master Data Objects, Staging Records and Monitor Mass Changes: what each app checks (the family on screen, the Task's table, the family the Monitor was opened for, else every licensed family); the strip disappears once the check passes.
- The checks list: both destinations complete, the same system, the communication user authorized for every interface (the scenario named), Connectivity on premise.
- Assistants: Check SAP Connection (every licensed family, one family, one table).
- A broken destination never blocks the subscription; fix it and the next read or run uses it; background runs re-check at every start, the apps within minutes.
Related information: messages-connection, verifying-the-setup.
Source in the product repository: customer guide §3 "How to check the connection", srv/lib/tenant-destination-status.js (D28).
Last updated: