Block ALM

Hi Team

There are instances where we do not want the production model to be updated using ALM.

This is required when we have any model developers working on the same model, and don't want any of them to accidentally move changes to PRO.

With this option we are better prepared for risks that may occur for data loss or restoring models.

Thanks

Kudi

Comments

rob_marshall

@Kudiarasu

Just a suggestion, you can remove the model builders WSA/Full Access role from Prod. This will prevent them from doing any model syncs.

david.savarin

@rob_marshall @Kudiarasu : same : mb as developers shouldnt have wa rights on a production model, and should probably limited to a release admin for deployment.

Though it would be easier if roles segmentation between mb and wa would be in place

Kudiarasu

Thank you for the suggestion, we dont want to take this approach esp. if this scenario is frequent. It would be much easier to have something like a locked status which will allow users to use the model but not allow any Design changes.

david.savarin

So it would be a new mode between the locked mode (cannot do anything) and the deployed mode (can interact and change prod data as well as deploy changes) ?

That would be interesting.

I would like additional secure options to also prevent models from accidental deletion (e.g. it s easier to delete models than to change their mode).

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.