btp-build-work-zone
Skill1 starsChanged 4 months agoMITView on GitHub
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.
In this repository413 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .cursor/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- sap-router-skillCopilot instructions
- .cursor/rules/sap-router.mdcCursor rule
- abap-cloud-migrationSkill
- abap-cloudSkill
- abap-code-patternsSkill
- abap-code-reviewSkill
- abap-docs-referenceSkill
- abapgitSkill
- abapSkill
- abap-snippetSkill
- abap-sql-amdpSkill
- abap-system-infoSkill
- abap-unit-testingSkill
- arc-1-skillsSkill
- atc-cloudificationSkill
- authorization-iamSkill
- automation-pilot-catalog-explorerSkill
- automation-pilot-command-generationSkill
- automation-pilot-command-reviewSkill
- automation-pilot-content-management-via-apiSkill
- automation-pilot-debuggerSkill
- automation-pilot-executions-apiSkill
- automation-pilot-executor-executescriptSkill
- automation-pilot-executor-httprequestSkill
- automation-pilot-mcp-server-generationSkill
- automation-pilot-scheduled-executions-apiSkill
- badi-enhancementSkill
- btp-abap-environmentSkill
- btp-best-practicesSkill
- btp-business-application-studioSkill
- btp-ciasSkill
- btp-cloud-foundrySkill
- btp-cloud-identitySkill
- btp-cloud-loggingSkill
- btp-cloud-platformSkill
- btp-cloud-transport-managementSkill
- btp-connectivitySkill
- btp-developer-guideSkill
- btp-diagram-generatorSkill
- btp-integration-suiteSkill
- btp-job-schedulingSkill
- btp-master-data-integrationSkill
- btp-service-managerSkill
- cap-add-remote-serviceSkill
- cap-developerSkill
- cap-triviaSkill
- capture-answerSkill
- cap-upgradeSkill
- cds-view-entitiesSkill
- claude-abap-skillsSkill
- claude-memSkill
- clean-abapSkill
- context-modeSkill
- cpi-iflow-developmentSkill
- engine-cap-developmentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
Ensure CAP app has Fiori launchpad plugin manifest in app/ directory
- Distinctive: line 48
Create a card manifest JSON file:
- Distinctive: line 89
Add widgets and apps to the template layout
- Distinctive: line 95
Ensure Work Zone content is published (apps, cards visible in Content Manager)
- Distinctive: line 103
Add sections: visualizations, cards, app launcher tiles
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SAP Build Work Zone (Advanced Edition)
Central entry point for SAP business applications — unified shell for Fiori, CAP, custom UIs, and external content.
Prerequisites
- SAP BTP subaccount with SAP Build Work Zone, advanced edition entitlement
- Admin role assigned:
AuthGroup_SpaceAdmin - Content manager role:
SAP_APP_FND_LAUNCHPAD_CONTENT_MANAGER - BTP destinations configured to backend systems (S/4HANA, CAP apps, etc.)
- Principal propagation enabled on destinations for federated content
Steps
1. Federate S/4HANA Fiori Apps
- Open Work Zone Admin Console → Content → Content Providers
- Click Add Content Provider → Type:
SAP S/4HANAorSAP BTP ABAP - Select the BTP destination pointing to your S/4HANA backend
- Configure: Destination with
PrincipalPropagationauthentication - Click Fetch Content → catalogs and groups auto-discovered
- Navigate to Content Manager → assign catalogs/groups to roles
2. Federate CAP Applications
- Content Provider → Type:
SAP BTP - Enter CAP app URL (e.g.,
https://my-app.cfapps.us10.hana.ondemand.com) - Ensure CAP app has Fiori launchpad plugin manifest in
app/directory - Fetch content → apps appear in Content Manager
3. Create a UI Integration Card
Create 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.mtar4. Configure Workspace Templates
- Admin Console → Workspace Templates → Create
- Select template type:
- Project Workspace: tasks + documents + team
- Department Workspace: KPIs + apps + news
- Process Workspace: workflow steps + approvals
- Add widgets and apps to the template layout
- Save and assign to roles for self-service workspace creation
5. Enable SAP Mobile Start
- Admin Console → Settings → SAP Mobile Start
- Ensure Work Zone content is published (apps, cards visible in Content Manager)
- Configure push notifications via SAP Notification service binding
- Mobile users: install SAP Mobile Start app → scan QR code from Work Zone
- Offline-capable cards require marking them as offline-enabled in card manifest
6. Configure Role-Based Homepage
- Admin Console → Home Page → Edit Layout
- Add sections: visualizations, cards, app launcher tiles
- Assign visibility by role (e.g.,
Sales_Managersees different tiles thanEmployee) - Save → users see personalized homepage based on their role assignment
Pitfalls
| 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. |
Verification
# 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:
- Content providers show status
ACTIVEin Admin Console - Federated Fiori apps appear in Content Manager and are assigned to roles
- UI Integration Cards render data correctly in preview
- Workspace template is published and self-service creation works
- Mobile Start app shows Work Zone homepage after QR scan
- Role-based homepage shows correct tiles for each test role
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

