Allow model builders to differentiate models by changing the color of the "Anaplan" blue header bar
We have many different models our team of builders uses, all of which have a slightly different name, but sometimes that's not exactly obvious if one is working in the Revision 1 model, or the Revision 2 model, Staging, or Production etc.
I would like the ability to alter the color of the blue anaplan header bar so that I can tell very easily "oh this is red, i.e. the color used for the Staging model, or "oh it's blue, I know at a glance that this one is the Production model"
Comments
-
Status changed to: In Review0
-
Status changed to: In Review1
-
I think it would be very useful if as a model builder I could customise the colour of the Anaplan banner on a model by model basis, helping me to differentiate models that are in different stages of ALM.
i.e. I could change my DEV model banner to Red, TEST to Yellow and Live to Blue.
I think, even if a coloured tag was placed at the front/end of the name to help differentiate the models in ALM, it would certainly be a more obvious visual cue rather than just the name (I have lost myself working between tabs before and I am sure I will do it in the future, but no doubt this will help to stop this!)
6 -
Great idea @CallumW !
1 -
Status changed to: In Review1
-
Yes please. I know other platforms has this as a feature.
1 -
This has been a very common complaint from our testers/admins who see very similar data that may not represent our production model.
1 -
+1, for us this would be very useful for differentiating between DEV, QA, and PROD versions of models
1 -
Requesting the ability to change the color of the model banners at the workspace level by the Tenant Administrator. This will significantly help our super users recognize what workspace they are in. When we have multiple Anaplan sessions in different workspaces going, we all get confused as to what workspace we are presently working with.
We had an issue 2 months ago where test data was entered into a PROD workspace model instead of the QA workspace model. Fortunately, this error was realized quickly and we were able to reverse the test data out of the PROD model. Had it not been caught, our end users would have been confused and concerned by that data. If the PROD workspace were a different color from the QA workspace, the chance of this happening would have been nil.
2 -
Yes please! This would be very helpful!
0 -
Agreed that this will be a huge help to minimize errors.
0
Get Started with Idea Exchange
See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!