When releasing a project copy as master for a existing document the system should validate if the master revision number is smaller than the project copy revision number.

Considering we may have several projects updating the same document, the newest file might not be the one with the greatest revision number.

We used to have a script that would do this verification and give an error message to the user, but as we are migrating to the cloud version, we were not able to keep the script.

Attached an example of revision staking that should not be allowed by the system.

imagem (13).png

Attachments Open full size