SR-B78964 · Issue 336274
Modified RuleFormToolBar for enhanced custom skin use
Resolved in Pega Version 7.4
A delegated decision table was not opening in a custom portal unless the sysadmin role was included in the access group. The root cause is that the custom CSS class 'hidden' is used by the system to hide the section 'pzRuleFormToolBarHotKeys', ensuring a section is generated (HTML generation) in the background but not visible to all users. Since this CSS class 'hidden' is available for out-of-the-box skins only, using a custom skin revealed the hidden class and made the hotkeys section visible. In order to allow the enhanced use of custom skins, the pzRuleFormToolBar has been modified to put a visible 'when' that will not display the hotkeys section if the rule is opened from delegation screen (Portals).
SR-B84781 · Issue 337707
Modified RuleFormToolBar for enhanced custom skin use
Resolved in Pega Version 7.4
A delegated decision table was not opening in a custom portal unless the sysadmin role was included in the access group. The root cause is that the custom CSS class 'hidden' is used by the system to hide the section 'pzRuleFormToolBarHotKeys', ensuring a section is generated (HTML generation) in the background but not visible to all users. Since this CSS class 'hidden' is available for out-of-the-box skins only, using a custom skin revealed the hidden class and made the hotkeys section visible. In order to allow the enhanced use of custom skins, the pzRuleFormToolBar has been modified to put a visible 'when' that will not display the hotkeys section if the rule is opened from delegation screen (Portals).
INC-192159 · Issue 691022
Handling added for designtime page used in runtime
Resolved in Pega Version 8.7
After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.
SR-120103 · Issue 183482
Headers auto-expanded when printing from portal
Resolved in Pega Version 7.1.8
When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.
SR-120103 · Issue 177698
Headers auto-expanded when printing from portal
Resolved in Pega Version 7.1.8
When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.
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-126181 · Issue 188742
Corrected tab display for failed visible when conditions
Resolved in Pega Version 7.1.8
When a repeating tab layout on a page group property includes "Body Visible When", tabs were displayed properly, but sections within were not being rendered for some tabs. To correct this, a visible when rule has been added to the outside content Div to handle situations where the when condition is not satisfied.
SR-B82049 · Issue 341054
pxCoverInsKey set in audit history when childcase created
Resolved in Pega Version 7.4
On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.
SR-B65131 · Issue 330322
Fixed 'when' rules for showing privileged escalation buttons
Resolved in Pega Version 7.4
Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.
SR-B95191 · Issue 342664
Conditional Required fields fixed when working with accessibility
Resolved in Pega Version 7.4
When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.