Hi Anaplan,
The New UX currently lacks ALM capability like the old UX does.
The benefit of this would be managing updates to apps as you currenly can in the old UX.
It would great if the New UX had ALM capabilities like the old UX.
Thanks,
Usman
YES! ALM has greatly contributed to our reliability and the trust of end-users in Anaplan. It enables us to demo and test major changes before releasing them into production. The new UX has to offer similar features that allow a full DTAP street with critical models. We can not work without it.
Haven't explored the new UX yet, but that's a huge miss to not have ALM for apps!
I think it'd be a dealbreaker for our organisation to migrate anything substantial to new UX without this functionality... I remember the times before ALMs existed and that was terrible!
For cases when we have one development model to multiple PROD models (1 to 21 for example), we need a quick way to deploy New UX changes to the Apps simultaneously without having to do an individual copy of an APP for every application.
The logic we're looking for is similar to ALM for the core models.
We have now launched this capability for Anaplan's UX!
Here is a best practices link for more information: https://community.anaplan.com/t5/Best-Practices/Application-Lifecycle-Management-for-the-User-Experience/tac-p/74769
Thanks!
@ChrisM nice try! 😉 The current capabilities are a good start, no doubt! But it's still an administrative nightmare in "best practise" if you want to follow a full DTAP street. Looking forward to see further improvements coming in.
Hi @vicky_ascencio Could you please clarify why the status was change to delivered?
This point is still a high demand request and best practice workaround is just a workaround (admin nightmare workaround).
Could we please reopen this idea please?
Could we please have this reopened.
The current ux alm capability was a good start, but lots of things for a good alm feature is missing (revisions tracking being a key one)
The created XLSX file contains an index of template report names that quick link to the related report tab. Since templates may be used to create multiple different reports based on passthrough parameters, I believe it makes more sense for the index to reference the Description given in the report book rather than the Name.
In multiple Anaplan implementations across FP&A, S&OP, and operational planning use cases, a recurring design challenge is the overuse of hierarchical lists with Top Levels, especially on large transactional or operational lists. In many projects, hierarchies are introduced early with the intention of providing “future…
Phenomenon: When the page is opened after launching the browser, FY25 is selected in the selector, but the year displayed in the grid is FY24. Current Workaround and Impact: The grid will display FY25 if the user first changes the selector in the page header to FY24, and then changes it back to FY25. Currently, end-users…
