We have a requirement where we want to set multiple accessgroups for an operator by multiple applications administrators when an email is triggred to each of these administrators. After receveing the email each app admin will try to update their application specfic access groups in the requested opearator profile.
How ever we would like to implement locking on the operator profile so that it will not over write other apps admin changes.
We tried a custom subcalss for Data-Admin-Operator-ID with locking enabled on the new class and it worked fine.The new sub class is mapped to pr_operators table.All the operators created in the applications are instantiated for the sub class.
Is there any problems with this approach or suggest any other approach.