Custom activity in the Service package

General
, , ,
1

Hello,
We are having the custom activity in the service package to do the requestor authentication where we are creating the operator ID Dynamically and then setting it to the pyOperPage through java function in Pega 8.2.2.

When this pyOperPage set function executes, sometimes we are noticing it updates to the operator ID instance in the database.

Issue is with one client id having access to different API’s which needs different access Groups to set in the Operator ID, so we are looking to set the Operator ID Access Group runtime and set that Service Requestor context executes that API request with that AG.

Please respond if anyone has any idea or faced this kind of issue/scenario.

2

Hi Satish,

May I know which function you are using for setting the pyOperPage ?

3

Thanks Mahesh for the response. Setting through this java step:

tools.getParameterPage().putObject(“pyOperPage”, myStepPage);

Does anyone know when we set the pyOperPage will it update the OperatorID data instance?

4

Can you please try to create a function below function

try{

tools.putParamValue(“pyOperPage”,PropertyInfo.TYPE_TEXT, myStepPage)

}

call the above function to set the pyOperPage

@function(tools,nyStepPage)

Before calling the function copy the Operator details into the step page

5

Upon reviewing the associated Support Case, this was resolved by you being able to figure out the incorrect implementation on Custom authentication.

6

@MarissaRogers - Could you let me know how this issue was resolved as I have similar issue.

7

Hi @AmalaM64! I’m not sure exactly how they resolved this. @satsihc6 could you share the resolution to help them out?

Thanks!