Best Practice: Governance/Approvals for "Platform Host" Architecture Type in EA workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello experts,
I have a requirement to restrict APM Analysts from independently setting the Architecture type to "Platform Host" on Business Application records. Our EAs want to implement a "gate" or approval process before an application is designated as a Platform Host to ensure CSDM integrity and proper hierarchy.
Before I jump into a technical build, I’d like to gather insights on:
Commonality: Is it a standard practice to gate this specific attribute, or is it typically handled through post-update audits?
Implementation Path: Rather than using a Client Script (which is easily bypassed), what is the recommended OOTB approach?
Should I use a Data Policy to make it read-only and trigger a Flow Designer approval?
Alternative OOTB Features: Are there any existing Governance or Assessment features within Enterprise architecture that I might be overlooking for this specific use case?
I want to avoid technical debt while ensuring our Application Portfolio remains a "single source of truth" that the EAs can trust.
Thanks in advance for your guidance!
