I'm presently working on a requirement where I need to allow user to modify instances of Data-Admin-Operator-ID (via activity) but restrict them from directly saving changes made on Operator ID form. I'm thinking to remove/disable Save & Save As buttons in the toolbar only on Operator ID form & keeping the buttons active in the toolbar on any other rule form (like activity rule).
Disabling/Hiding Save/SaveAs buttons for Operator rule will be a good way to restrict the rule modification directly.
You can go ahead with this approach. Let us know if you need any help related to this.
Instead of hiding the buttons directly by overriding the section for Operator rule, there is an activity (WBToolbarSettingsDefault) that can be overridden in Operator ID class to set properties which will automatically hide buttons.
Let us know if this helps :)
Posted: 5 years ago
Posted: 27 Feb 2017 7:28 EST
ABHISHEK SHARMA (ABHISHEKS7672)
An alternative to that, you can consider restricting edit by imposing Access Roles which will be defined at the Operator's access group.
We have similar case, we create the Operator ID as part of the SSO Log on and while we create the Operator we we assign certain Operator ID fields. We have restricted the Delete/Update/Creation of Operator ID instances using Access Role Names.