计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
btp-build-work-zone【效率与协作】SAP Build Work Zone (advanced edition) — workspace configuration, content federation, UI integration cards, workspace templates, SAP Mobile Start, role-based homepage. Use when configuring SAP Build Work Zone, federating SAP content, or building workspace templates.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
name: btp-build-work-zone description: > SAP Build Work Zone (advanced edition) — workspace configuration, content federation, UI integration cards, workspace templates, SAP Mobile Start, role-based homepage. Use when configuring SAP Build Work Zone, federating SAP content, or building workspace templates. trigger:
Central entry point for SAP business applications — unified shell for Fiori, CAP, custom UIs, and external content.
AuthGroup_SpaceAdminSAP_APP_FND_LAUNCHPAD_CONTENT_MANAGERSAP S/4HANA or SAP BTP ABAPPrincipalPropagation authenticationSAP BTPhttps://my-app.cfapps.us10.hana.ondemand.com)app/ directoryCreate a card manifest JSON file:
{
"sap.app": { "id": "my.card", "type": "card" },
"sap.card": {
"type": "List",
"header": {
"title": "Open Purchase Orders",
"icon": { "src": "sap-icon://purchase-order" }
},
"content": {
"data": {
"request": {
"url": "{{destinations.s4}}/sap/opu/odata/sap/Z_PO_SRV/PO_HEADER?$top=5"
}
},
"item": {
"title": "{PurchaseOrder}",
"description": "{Supplier}",
"info": { "value": "{NetAmount}" }
}
}
}
}
Deploy via:
# Upload card via Admin Console → UI Integration Cards → Import
# Or deploy via MTA with card resource type
mbt build && cf deploy mta_archives/my-workzone-content.mtar
Sales_Manager sees different tiles than Employee)| Cause | Solution |
|---|---|
| Federated content not appearing after fetch | Content cache has up to 5 min delay. Wait, then click Refresh in Content Manager. Verify destination has PrincipalPropagation auth type. |
| CORS error on card data source | Card data sources must have CORS configured. Add Access-Control-Allow-Origin header on the backend OData service or use a BTP destination with HTML5.DynamicDestination=true. |
| Card shows no data / blank | Check the {{destinations.<name>}} placeholder matches a destination configured in Admin Console → Destinations. Verify the OData service path is correct. |
| Workspace member limit exceeded | Max 5000 members per workspace. Split large orgs into multiple workspaces or use role-based membership rules. |
| Cards not refreshing in real-time | UI integration cards refresh on user interaction, not real-time. Configure auto-refresh interval in card manifest (refreshInterval in seconds, min 30). |
| Mobile Start content missing | Ensure content is published (not just saved) in Admin Console. Check that the user's role includes the catalog/group assignments. |
# Check content provider status
curl -s https://<workzone-host>/api/v1/contentproviders \
-H "Authorization: Bearer $TOKEN" | jq '.[].status'
# Verify card endpoint resolves
curl -s "{{destinations.s4}}/sap/opu/odata/sap/Z_PO_SRV/PO_HEADER?\$top=1" \
-H "Authorization: Bearer $TOKEN" | jq '.d.results[0]'
# Confirm workspace template is active
curl -s https://<workzone-host>/api/v1/workspacetemplates \
-H "Authorization: Bearer $TOKEN" | jq '.[].status'
Checklist:
ACTIVE in Admin Console