Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Shourav Ushank (SUSHANK2011)
Societe Generale Global Solution Centre

Societe Generale Global Solution Centre
IN
SUSHANK2011 Member since 2011 1 post
Societe Generale Global Solution Centre
Posted: Dec 23, 2022
Last activity: Dec 27, 2022
Posted: 23 Dec 2022 9:23 EST
Last activity: 27 Dec 2022 7:09 EST
Closed

The default operator ID (which should stay neutral) is automatically saved each time an API call is received.

We have a scenario where some users who do not have an operator ID in the application must be able to call some of our APIs. 

In our custom authentication activity, if we notice the API caller is not supposed to have an operator ID, then we open a default operator ID, we set the user name and details on the operator ID, and then we set the operator page on Param.pyOperPage.

We notice that Pega will then try to save the default operator ID with the names and other info we have set on the page.

We do not want the default operator to be saved in DB for security reasons.

Could you please let us know if there is a way to bypass the OOTB auto-save of the operator ID for this particular operator ID (but keep the behavior for any other Operator Id)?  

***Edited by Moderator Marissa to add Capability tags***
To see attachments, please log in.
Pega Platform 8.3.4
Dev/Designer Studio
Data Integration
Financial Services

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice