SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.
SR-119869 · Issue 176176
Access Role Editor link errors fixed
Resolved in Pega Version 7.1.7
When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.
SR-117114 · Issue 171740
Added localization formatting for date values (YYYY-MM-DD)
Resolved in Pega Version 7.1.7
In Sweden, dates are given with a hyphen "-" and not slash "/" as the date separator as per ISO-8601. The SV localization has been changed to follow this style.
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.