Support Article

Operator ID page does not populate on all threads

SA-53806

Summary



The Operator ID system page has properties and values in the STANDARD thread. However, it is empty in all other threads created for a requestor. This causes issues while creating and updating work objects.
This occurs when accessing the system using custom authentication.



Error Messages



Not Applicable


Steps to Reproduce

  1. Create an authentication service.
  2. In the authentication activity, perform an obj-open and open an operator.
  3. Add an obj-save in the activity.
  4. Open the URL: http://<hostname>:<portnumber>/prweb/PRWebLDAP1. Operator ID page is missing in the threads other than STANDARD thread.


Root Cause



Operator page must be created at the requestor level. Operator ID page creation is considered as part of engine code during authentication of the requestor. However, when the operator record is saved from custom authentication activity, operator record save triggers the UpdateOperatorID declare trigger defined on it. UpdateOperatorID trigger has the UpdateOperatorID activity which performs the page-copy of the primary page to the OperatorID page. Due to this reference to the OperatorID page, the OperatorID page is created at the thread level and authentication process skips the creation of the OperatorID page at the requestor level.


Resolution



As a local-change, include a Java step with the below code before performing the operator save.

tools.getRequestor().getPage("OperatorID");


 
Suggest Edit

Published September 29, 2018 - Updated October 8, 2020

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.