Skip to main content

In IAM Models and Branches kan be cleaned up by using the delete button. If you accidently had selected a model instead of a branch, the whole model is deleted including all branches.

If all groups and roles are implemented in the SF a sync could fix the mistake. If not you're left with restoring the IAM database.

Today I accidently removed a model instead of a branch this way. I now depend on IT to restore the database. Luckily it was no production IAM.

My idea: present the user with a popup and having him/her selecting wether to delete a model with all branches or not. If it is up to me, deleting a model that has branches shouldn't be possible at all.

 

 

Hi @htimmermans,

The way we will handle the state of an application and its associated model/branch will undergo significant changes in the upcoming platform release.

You can find some information on this in my response to this idea:

Further details will, of course, be provided then in the release notes.

One effect of this change is that it will no longer be possible to delete a branch if it’s still in use by an active application. This will also extend to the model level; deletion will only be possible once none of the associated branches are used by an active application.

This isn't the exact solution you proposed, but it will likely help prevent this issue in many cases.

I can open your idea for voting, but this will then be scoped specifically to the only situation where your issue could still occur: when there’s a model with branches that aren’t used in any active application. I can also understand if you find the upcoming solution sufficient.

Please let me know your thoughts on this.

New→Needs feedback

Ok… I'll be more carefull until the next release then (I assume 2025.01). Thanks for your reply.

We had the same experience last week. The production application was deleted when we deleted the a model/branch accidently. 

It should not be possible to delete a model as long as it has related applications.

 

 

Needs feedback→Next release
Terms & ConditionsCookie settings