Issue  

Editing conditions and When rules in App Studio cause performance problems and nodes become unresponsive. There are several areas within Pega Platform™ where this functionality can be found, including Assignment routing, decision steps and setting conditions in Pega Customer Service. 

Symptoms and Impact 

• App Studio screen becomes unresponsive. 

• Nodes become unresponsive. 

Steps to reproduce 

To reproduce the issue using Assignment routing logic: 

1. Launch App Studio. 

2. Navigate to the Case Types tab and open a Case Type. 

3. Select a Step in the Case Type. 

4. In the right-hand pane, navigate to "Route to", select "Use business logic" and click the gear icon. The system hangs and there are multiple null pointer exceptions in the event viewer. 

Root Cause 

System performance is impacted in the following scenarios: 

• There is a large number of relevant records in an application. 

• There are Page or Page List properties that require multiple iterations through the class structure. 

Solution 

The performance impact of this limitation was reduced in version starting in Pega Platform ‘24.1. 

Further improvements to the Condition Builder functionality are planned in upcoming Pega Platform patch and major releases. 

Perform either of the following actions to mitigate the behavior:  

• Review the relevant records in the application and remove the ones that are not used.

  • In Dev Studio, click Configure > Application > Inventory > Relevant Records to view the list for the selected class. 

• Reduce the amount of nested fields being fetched. Apply the following local change: 

  • Save the @baseclass pySetWhenGadgetContext data transform rule in the your application ruleset. 

  • Update property "pyNestedLevels" setting value to 1 

  • Update property "pyFilterByContextClass" setting value to true. 

References 

 Configuring business conditions 

Configuring custom business logic-based routing  

Business conditions