Better control of redefinitions of entities in project hierarchy

In our organisation, we want to forbid the redefinition of an entity in the hierarchy of projects (entities of same name in the same tree of projects). This was a key feature of Pacbase to allow the administrator to forbid such redefinitions.

To do that, we have enabled the deliver precondition to forbid entities redefinition at deliver time. This precondition is based on the server indexes, which are not refreshed immediately when a change is delivered. For this reason, in some cases, the precondition makes a wrong diagnostic : if a user moves up or down an entity in the hierarchy of projects, deleting it in one project, creating a new one with same name in another upper or lower project, the precondition will reject the deliver because the deletion is not yet taken into account in the server indexes (the deleted entity still exists in the indexes that have not yet been refreshed).

This problem forces the user to bypass the deliver condition, which is not recommended in our organisation. The user can also trigger a manual incremental reindexation of the server, but this is not practical.

To help us control the redefinition, we have two requests :
1- After a deletion of an entity has been delivered, an automatic incremental reindexation of the server should be trigerred. The user should not have to trigger it manually in this case.
2- Another deliver condition should be provided based on the content of the local workspace :
In our organisation, we do not use the sparse loading. All entities are loaded in each user's workspace. So, we have all information in the local workspace to be able to check for redefinitions.
So, we request to have a new deliver condition to reject the delivery of redefinitions based on the local content and not based on the server content. We understand it is not a full garantee, in case the user hasn't refreshed his workspace with latest changes made by other users. But we consider this new type of control is able to work most of the time in our organisation (in replacement for the existing control based on server indexes).