1) If we create an user entry in the PR_OPERATORS table from backend, will that create the operator ? Do we need add / update any other table ?
Answer : I never tried adding an operator id directly from database ( backend ) , but if your requirement of creating an operator from backend is to avoid creating multiple operator id manually, then I think you better check this post on pega Exchange : https://pdn.pega.com/community/pega-exchange/bulk-operator-load-for-process-commander This utility will allow you to quickly add users to your PRPC system via a comma delimited file using PRPC’s File Listener capabilities.
2) Can we disable / enable the Operator ? If so, what attribute should be updated ?
3) For deletion of the operator, can we simply remove the record from PR_OPERATORS table ? Is there any dependency on other table ?
Answer : I believe just deleting the operator id from backend will not help because there are multiple dependencies which are associated with the operator id.. Better you follow the approach as suggested in Answer of question number 2
4) Which column in the table PR_OPERATORS signifies the Operator Type ?
Question : Can you please elaborate what you mean by "Operator Type" ?
If I were to attempt to create operator records like this, in order to check whether I needed to update other tables, I would do a prpc trace of creating an operator record through the normal rule form, with all event types turned on, and then review the trace lines to see which details are being handled, such as cache tables, index tables, and particular attributes on the operator record itself.