Ability to add folder structure in model management

Description of the enhancement required:

Create folders and keep the models in various folders

How would it help their business process:
We have about 15 modellers working on different models. Wed like to be able to organise them better. Sometimes we might forget the names of models they are creating. In windows, they can access different excel sheets from folders which is how they are organised.

Comments

AnaplanIdeas

Status changed to: In Review

clarissa

This would be very helpful for us because we have ~30 models for one use case, and among these 30 there is a segregation between DEV, UAT, and PROD. Having folders for each category would help prevent admins from accidentally opening a PROD and making an update to data when we are testing a change that was synced to UAT.

This would extend the need for folders to the Frontdoor level, as models in the same category may exist in multiple workspaces.

mark_johnston

Even as a basic requirement it would be helpful to be able to sort the models by name / size in the model management window.

ArdenMiller

This is crucial for organization and adoption. It is very frustrating to scroll through an unorganized list of models.

Should be able to create folders and organize and expand/collapse.

Also need to be able to apply SECURITY by these folders!

PLEASE add this feature ASAP!

praveenvenkatesh

Yes, I agree with the viewpoints of @clarissa and @ArdenMiller. We should have the folder structure in Model Management.

Quick Links

New ideas

Anaplan Color Pallet
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: The Anaplan Color pallet should be consistent across all forms. Text Pallet is different Action Icon Default Colors, and different…
Workflow: Continue Workflow after Decision Task Rejection
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: Currently a workflow ends if a decision task is rejected and it is not possible to add workflow steps after the rejection. I want to…
Allow non-WSAs to view source module name in UX.
When a user clicks the ellipsis in a grid card they should be able to see the name of the source module. This empowers end users with the ability to connect to the source data they see in the UX to the module in the backend. It also enables end users to pull the data into Google Sheets or Excel.