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

 anand managoli (Anand Managoli) Adqura Business Architect
Adqura
IN
Anand Managoli Member since 2014 15 posts
Adqura
Posted: Jun 14, 2021
Last activity: Jun 14, 2021
Posted: 14 Jun 2021 14:28 EDT
Last activity: 14 Jun 2021 15:02 EDT
Closed

NBA Designer V2 upgrade issue

Appreciate if someone could help on this.

I got a vanilla installation of Pega 8.6, Pega CDH 8.6 and wanted to do explore the capabilities with a sample application did the following.

Created a new CDH application pointing to OOTB PegaMKT-Data-Customer class.

Then went ahead with configuring the Taxonomy, created some issue some groups, added offers, configured the action flows, contact policy, some eligibility rule, basic channels to test and scheduled the batch.

Batch ran and I could see the offers I expected and also returning for the inbound channel via postman.

After couple of runs and tests introduced a new customer class and changed the context of the application and saved. The context was saved file without any errors.

After saving the context, the NBA Designer screen came up with a note to upgrade NBA Designer version.

 

Error Screen1

After logout-login, saw the upgrade now button on the NBA designer screen and clicked on it.

It took some time and later failed.

 

Screen 2

Show More

Appreciate if someone could help on this.

I got a vanilla installation of Pega 8.6, Pega CDH 8.6 and wanted to do explore the capabilities with a sample application did the following.

Created a new CDH application pointing to OOTB PegaMKT-Data-Customer class.

Then went ahead with configuring the Taxonomy, created some issue some groups, added offers, configured the action flows, contact policy, some eligibility rule, basic channels to test and scheduled the batch.

Batch ran and I could see the offers I expected and also returning for the inbound channel via postman.

After couple of runs and tests introduced a new customer class and changed the context of the application and saved. The context was saved file without any errors.

After saving the context, the NBA Designer screen came up with a note to upgrade NBA Designer version.

 

Error Screen1

After logout-login, saw the upgrade now button on the NBA designer screen and clicked on it.

It took some time and later failed.

 

Screen 2

Failure Step

Tried again and it failed at the same step with the below Error log

Caused by: com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Unable to execute the Activity 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.execute(ActivityProcessor.java:65) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.run(ActivityProcessor.java:110) ~[pega-executor.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1380) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1123) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1004) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImplForModules.doWithRequestorLocked(PRSessionProviderImplForModules.java:83) ~[prprivate-session.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.run(ActivityProcessor.java:101) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:110) ~[pega-executor.jar:?] 
        ... 13 more 
Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: No such Access Group: POC:Administrators for thread STANDARD 
        at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getBasicApplicationContext(GlobalContextCache.java:438) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(GlobalContextCache.java:449) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(AuthorizationContextManagerImpl.java:120) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:485) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:429) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.setAvailableAccessGroups(SessionAuthorization.java:523) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.Authorization.setAvailableAccessGroups(Authorization.java:758) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.authorization.Authorization.setAvailableAccessGroups(Authorization.java:750) ~[prprivate-session.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityExecutor.setContextToAccessGroup(ActivityExecutor.java:77) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityExecutor.switchContext(ActivityExecutor.java:69) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityExecutor.executeActivity(ActivityExecutor.java:48) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.executeActivity(ActivityProcessor.java:73) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.execute(ActivityProcessor.java:59) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.run(ActivityProcessor.java:110) ~[pega-executor.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1380) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1123) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1004) ~[prprivate-session.jar:?] 
        at com.pega.pegarules.session.internal.PRSessionProviderImplForModules.doWithRequestorLocked(PRSessionProviderImplForModules.java:83) ~[prprivate-session.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.run(ActivityProcessor.java:101) ~[pega-executor.jar:?] 
        at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:110) ~[pega-executor.jar:?] 
        ... 13 more 

=========================

Verified that my operator has Admin role and HasPrivilegeToManage when rule also returned true.

Why does the upgrade process fail after 75% if it is because of Access Group issue?

The upgrade option showed up only after we changed the context to our custom customer class. Is this expected?

 

Show Less
To see attachments, please log in.
Pega Customer Decision Hub Decision Management Cross-Industry Business Architect

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