Question
US
Last activity: 17 Aug 2025 22:51 EDT
Dynamically Changing AG Not Properly Setting Application Context
I have a Pega instance with two applications. App-1 is built on top of App-2. Operators should have access to App-1 and App-2
- App-1 has an AG of App1:AccessGroup and has its own Authentication service rule with custom post processing
- App-2 has an AG of App2:AccessGroup and has its own Authentication service rule with custom post processing
The issue I am having, when an operator has both access groups on their Data-Admin-Operator-ID record. When they are defaulted to App1:AccessGroup and they hit the URL for App-2 authentication service, we are successfully setting the new default access group to App2:AccessGroup but the operator is in the context of App-1 still.
Online I have seen mention of pxUpdateOperratorContext but I cannot find that rule in my Pega instance. I also was trying to figure out to use the SwitchApplication function but cannot find the syntax of how to call it from the function method activity.
In short: Operators will have both AGs, based on the auth service they hit dynamically sets the Default access group and app context. The AG is setting but the application context looks to be set prior to the post auth activity running and is not refreshing.
HCA Healthcare
US
don’t flip the operator’s default AG in post-auth; Pega resolves application context before your post-auth runs. Instead, for each Authentication Service, set its Access group directly to the target AG (App1:AccessGroup for App-1 URL, App2:AccessGroup for App-2 URL). In your post-auth activity, switch only the requestor context: set a parameter to the target AG, call pxSetActiveAccessGroup (switches AG for this session without saving the operator), then call pxSwitchApplication with the target application name and version to rebuild the ruleset list and app context. After that, redirect to the app’s portal (use the app alias URL like /prweb/app/<alias> or do a Show-Harness to pyPortal). If you must also persist the new default AG, save the OperatorID after login, but still do the two calls above for this session. If you can’t find pxSwitchApplication in your version, use the public API step (Java) to switch the application on tools.getRequestor(), then redirect. This pattern avoids caching issues and cleanly puts users in the right app based on the auth URL they used.