1. Data sources can be exposed to Odata 2. The Odata built by the data source can be invoked by technical users 3. The data source cannot use the Odata editor, but you can directly create the Odata service of the Ticket object

Have you tried to put this script in the Customer Root-Event-AfterModify.absl to trigger?

It happened to me, too, but also not solve .you can set new object like NumberRange.ResetRange("TEST2") to Resetting NumberRange.

You can try to customize employee ovs to achieve this.

No and understand, it would be better if there were pictures to explain.It seems that you are troubled by the locking problem. You can consider not updating the custom bo data or consider judging the locked documents.