SR-132987 · Issue 205014
Enhanced Expression Builder icon availability
Resolved in Pega Version 7.1.9
Previously, the Expression Builder gear icon was only available for text type properties: this has been updated to make the EB icon visible for all property types.
SR-133079 · Issue 202877
Repaired column header labels in Decision Table
Resolved in Pega Version 7.1.9
Clicking on a column header and opening the property changer, then closing it using the X in the top-right corner of the popup caused the label to change to the label of the rightmost column. This was traced to incorrect behavior by the modal dialog where closing the window did not return the correct value from the previous launch. This has been corrected.
SR-133382 · Issue 205956
Updated paragraph styles in Security policy
Resolved in Pega Version 7.1.9
Using ie, the History tab and Policy Definition tab had incorrect content while viewing Security policy rules. This was found to be an issue with the styles present in the paragraph rule 'pzScriptSrcDescription', and the styles have now been updated.
SR-133382 · Issue 205957
Updated paragraph styles in Security policy
Resolved in Pega Version 7.1.9
Using ie, the History tab and Policy Definition tab had incorrect content while viewing Security policy rules. This was found to be an issue with the styles present in the paragraph rule 'pzScriptSrcDescription', and the styles have now been updated.
SR-133538 · Issue 205317
Smart Prompt fixed for DT column headers
Resolved in Pega Version 7.1.9
Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.
SR-133538 · Issue 204972
Smart Prompt fixed for DT column headers
Resolved in Pega Version 7.1.9
Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.
SR-129260 · Issue 196814
Improved passivation handling for long page names
Resolved in Pega Version 7.1.9
An issue where sporadic 'database serialization failed for requestor' errors were being logged was traced to certain page names that are very large. During passivation, if the pxInsName was larger than 128 characters, it did not fit in its associated column in the pr_page_store table and generated the error. It was also noted that while pzinskey is 255, pxinsname is 128. To resolve this error, pxinsname has been increased to 255, and DatabasePassivation will hash the page name for storage if it exceeds the maximum allowable length.
SR-129984 · Issue 203634
Error handling added for skin check-in
Resolved in Pega Version 7.1.9
A 'string index out of range' error when checking in a skin was causing the rule to hang. This was caused by an exception generated by the ordering of clipboard results, and handling for this has been added to resolve this problem.
SR-130496 · Issue 203385
Fixed ruleset cache population after passivation
Resolved in Pega Version 7.1.9
After a session was idled, a 'RulesetName not specified' error appeared during checkout when the session was resumed. This was an issue with SnapshotApplicationContext not being activated properly to populate the cache after passivation, and has been fixed.
SR-130754 · Issue 200600
Remove locale consideration from toDecimal string conversion
Resolved in Pega Version 7.1.9
The 'toDecimal' function was unable to convert the string to decimal properly when the user locale is set to Indonesia. As the 'toDecimal' RUF should not be doing localized conversions, this RUF has been updated to ignore user locale.