Question
Lloyds Banking Group PLC
GB
Last activity: 11 Nov 2022 8:56 EST
AsyncDeclarativePool service package access group
We have a number of DP's in our app that are invoked asynchronously via Load-DataPage method and this works in our v7.3.1 environment but fails after we upgraded to a v8.7 environment.
However, if I update the access group in the AsyncDeclarativePool service package in 8.7 env to point to our app specific AG instead of the PRPC:Administrators AG that comes with the product then it starts working.
We obviously didn't need to update the access group in this SP in v7.3.1 and it made sense to not to and assumed the spun off requestor used the context of the user from which the Load-DataPage was called from but doesn't appear to be the case in 8.7.
Is this a change in design or does this appear to a bug?
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 11 Nov 2022 8:56 EST
Lloyds Banking Group PLC
GB
This apparently is a bug in 8.7 and fixed in 8.7.4. Although as a workaround, we have been asked to set the EnableRequestorPools DSS (introduced in recent versions of pega) to true. This setting is by default false for non-pega cloud deployments and setting this to true helped fix the issue.
Infosys Limited
IN
By default, AsyncDeclarativePool service package has the PRPC:Administrators accessgroup. Did you change any access roles? Could you please compare the accessroles of your access group with this accessgroup?
Lloyds Banking Group PLC
GB
@P.Siva.Praveen No changes to the OOTB access group
Accepted Solution
Updated: 11 Nov 2022 8:56 EST
Lloyds Banking Group PLC
GB
This apparently is a bug in 8.7 and fixed in 8.7.4. Although as a workaround, we have been asked to set the EnableRequestorPools DSS (introduced in recent versions of pega) to true. This setting is by default false for non-pega cloud deployments and setting this to true helped fix the issue.