In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
We are trying to export and document Anaplan New UX pages and model metadata for governance, audit, impact analysis, and knowledge management purposes.
Currently, there is no native option to export New UX page configurations, layouts, cards/components, context selectors, synchronization settings, linked modules/views, actions, or navigation details. This creates a documentation gap because important UX configuration details exist only inside the Anaplan interface and cannot be extracted in a structured format.
Specific examples include:
- Identifying which pages are connected to which models, modules, and saved views
- Reviewing which cards/components are used on each page
- Documenting filters, selectors, and context synchronization
- Comparing UX page configuration across development, test, and production apps
- Performing impact analysis before changing modules, views, actions, or lists
- Creating audit-ready documentation of UX design and configuration
For module metadata, there is a partial workaround by switching back to the Classic/Old Model Experience to export module information. However, this does not address New UX page metadata and does not fully support governance needs in the New UX experience.
Workarounds:
Current workarounds are manual and time-consuming:
- Taking screenshots of UX pages
- Manually documenting page layouts and cards
- Opening each page one by one to review settings
- Manually tracing source modules, saved views, actions, and context selectors
- Maintaining external documentation in Excel, Word, or SharePoint
- Switching to the Old Model Experience for limited module export options
These workarounds are not scalable, are prone to human error, and become difficult to maintain as apps, pages, models, and business processes grow.
How often is this impacting your users?
This impacts us regularly, especially during:
- New model or app development
- Production release cycles
- Model changes and impact assessments
- Governance reviews
- Audit or compliance documentation
- Knowledge transfer
- Support and troubleshooting
- Migration or environment comparison activities
For large enterprise environments with multiple workspaces, models, apps, and UX pages, this can impact users weekly or during every major enhancement/release cycle.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
This impacts multiple Anaplan roles, including:
- Model builders
- Solution architects
- Workspace administrators
- Tenant administrators
- Integration experts
- Business analysts
- Support teams
- Governance teams
- Documentation owners
- Business process owners
- Partners and implementation consultants
Business/end users may also be indirectly impacted because manual documentation and impact analysis can delay enhancements, issue resolution, and release timelines.
What would your ideal solution be? How would it add value to your current experience?
The ideal solution would be a native export capability for New UX Pages and New Model Experience metadata.
This should allow administrators and model builders to export structured metadata for:
- Apps
- Pages
- Page types
- Page layouts
- Cards/components
- Source models
- Source modules
- Saved views
- Actions
- Context selectors
- Filters
- Synchronization settings
- Navigation links
- Page access/security information
- Last modified details
- Owners or administrators
Please include any images to help illustrate your experience.
