Hello,

Microsoft will be removing their Basic Authentification for Outlook in October 2022.

Our project is still in version 7.3 so it is not compatible with OAuth 2.0 and we are planning to migrate to Pega 8 but only in 2023. So we are trying to find a solution to replace Basic Authentification on our apps.

Is any other project encountering this issue? If yes, have you found any solution apart from migrating to version 8?

Thank you,

Celine

Hi All, 

We are looking for an upgrade guide for 

Platform: Pega 7.3 to 8.7.1 

Customer Service: Pega 7.22 to 8.7.1 

Our targetted platform is: On-Prem to Client Managed cloud

On-Prem: Apache Tomcat / MS SQL  to Client-Managed Cloud: Apache Tom / Azure Managed SQL. 

We just want to be sure that we can upgrade Pega CS from 7.22 >> 8.7.1 without going through an interim version upgrade. 

Hello Everyone!

In our production environment we make use of several connectors throughout the customer service lifecycle. The problem we are facing is: Some of these connectors respond really quickly and others may take several seconds before responding.

As far as we know, the PEGA0020 threshold is global for all connectors, so we have many entries in the logs for the connectors that take a long time to respond, but can't increase the threshold, otherwise if one of the faster connectors starts experiencing problems, it won't show up in the logs.

Hi ,

Last week we installed hotfix for A22 security vulnerability after which few of our integrations stopped with below error:

"Java code injection pattern identified in the java source code .Vulnerable code detected."

Hence we tried to rollback the hotfix and perform a clean restart. However after restart the server is not coming up.

And in logs we could see the below error:

Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.pega.pegarules.common.PREngineProvider

Hi, I am using Pega 7.3 I have a DataPage configured as List 

What's the possible reason why Node Scope data got deleted and does not refresh.

I've been testing for quite a while, I've changed the Access Group, also added 24 hours to reload if page is older.

Here is the scenario.

I have a issus on Pega 7.3. I have to automate the check conflict on jenkins. For this, I use a http request authentification such as automate the PEGA-Unit. So I go to the PEGA-API, and use getconflict with returns a list of conflicts that would occur if that branch was merged. A url link is displayed (http://localhost:8081/prweb/api/v1/branches/{Id Branch}/conflicts), but when i use it, i'v got this error:

Use Case:

As per organization standards, an API needs to be exposed which will update an object using functionality similar to JSON MERGE PATCH. As per MERGE PATCH convention, if object already has a property called "type" with value as "Standard", to remove this property from the object, the incoming payload will be:

{     "data": {             "type": null     }

}

Problem statement: