SR-B56835 · Issue 312521
Checked in SLA values updated by delegated use
Resolved in Pega Version 7.3.1
Once checked in to the application, the SLA value was not being properly updated when edited by an delegated operator and instead retained the value given by the Case Manager. This was a clipboard handling issue, and has been fixed.
SR-B4768 · Issue 276160
Global DB Trace timestamp uses UTC
Resolved in Pega Version 7.3
When running Global DB trace, recorded timestamps were not following the 'set timestamp' setting. Timestamps instead corresponded to the requestor context. DB Tracer logging has been updated to ensure appended timestamps are passed as "UTC".
SR-123977 · Issue 185468
Optimized regex decision tree for property and when values
Resolved in Pega Version 7.1.8
A regex expression run against long property names was resulting in system slowdown and stuck requestor threads. A similar issue was encountered with When rules. To resolve this, the decision tree has been optimized.
SR-B65837 · Issue 317187
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
SR-B67171 · Issue 317155
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
INC-193700 · Issue 685077
Support added for calling Strategy rule from When Rule
Resolved in Pega Version 8.8
An enhancement has been added to support manually referencing Strategy rules in the When rules using Dev studio.
SR-A2 · Issue 203635
Updated use and edit of the 'Search for work' rule
Resolved in Pega Version 7.1.9
After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.
SR-A5110 · Issue 214245
Fixed exception generated by 'getclassname' used with autocomplete
Resolved in Pega Version 7.2
An issue was found in some new installations using autocomplete where trying to set and execute 'getclassname' after a name change caused a conflict between the old and new values. The problem was traced to a function that set the new value and then repeated a call to the old one, nullifying the change. This did not effect upgraded systems due to a difference in the storage stream versions, and the conflict has been resolved by updating the logic
SR-B34135 · Issue 291962
Existing Org Names used in new layer
Resolved in Pega Version 7.3
In the Advanced configuration section, existing Organization Names were not being used while creating a new framework on top of an existing framework/application. This was an issue with the framework ruleset prerequisite preparation logic incorrectly setting the ruleset version for the dependency of the framework integration ruleset, and has been fixed.
SR-D17987 · Issue 494485
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.4
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.