SR-124683 · Issue 191853
Null check added to portal resizeActionIFrame API
Resolved in Pega Version 7.1.8
In some instances, the error "Unable to get property 'scrollHeight' of undefined or null reference" appeared when using a portal. This was due to a missing null check in the harness for the resizeActionIFrame API, which has now been added.
SR-124691 · Issue 186750
Resolved lost transaction ID while adding and deleting attachments
Resolved in Pega Version 7.1.8
When a file was attached and another one deleted at the same time from a work object, the session transaction was lost. Trying to approve the item generated the message "This action is not allowed as it is outside the current transaction". This was due to a stale transaction ID within the frame, and the FromFrame API has been updated to handle the delete attachment activity so the transaction session of parent frame does not get invalidated.
SR-124700 · Issue 187999
Removed white space from edit data table
Resolved in Pega Version 7.1.8
The pop up to edit data table was displaying white space at the top left corner due to the CSS style pageTabLeft in file listvieweditor.CSS using a background-image with a width of 12px while the area to cover is 27px. This has been corrected.
SR-124760 · Issue 186202
Corrected timing for change action on autocomplete
Resolved in Pega Version 7.1.8
When a Data Transform was configured on an autocomplete to clear properties, the DT fired on load of the section itself and caused inconsistent behavior depending on timing. This was a case of the generation not honoring the "Run data transform" option available in the section include property panel, and has been corrected.
SR-124868 · Issue 187837
Localization Wizard expanded to collect all applicable rulesets
Resolved in Pega Version 7.1.8
A large inconsistency was seen in the number of Strings Exported after selecting all Application rulesets and proceeding with the localization wizard depending on whether or not the top app RS were selected. The pyWorkPage.pyRuleSets page list is intended to be a list of ruleset names on which localization wizard to be executed, but only the selected first application ruleset was added. To correct this, the precondition in "GenerateRulesetList" activity has been updated to include all rulesets.
SR-124873 · Issue 187569
Updated accessibility for operator profile checkbox
Resolved in Pega Version 7.1.8
Focus was not moving to the checkbox "Operator is available to receive work" in the operator profile form when using tab control in accessibility mode. To enable this, the logic of inclusion of accessibility styles in the WorkformStyles HTML fragment has been enhanced.
SR-124877 · Issue 186909
Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.
SR-124919 · Issue 188505
Handling added for invalid event object in Dynamic Select
Resolved in Pega Version 7.1.8
When there are two DynamicSelect controls in a section, the value selected in the first causes the list of choices in the second to be filtered. If there is an invalid but non-null event object, selecting a value in the first dropdown generated the JavaScript error "Member not found". This has been resolved by adding a condition in the reload API to handle the non-null invalid object.
SR-124930 · Issue 186906
Inserted validation for reversed availability dates
Resolved in Pega Version 7.1.8
In Developer portal-> administrator -> profile -> availability , entering UnavailableFrom and To dates for the schedule where the From date is in the future of the To date was submittable without triggering error messages. The root cause of the issue was a skipped activity step. The validation step is looped only for specific embedded pages, and was not being called in this case. This datetime error has been corrected.
SR-124971 · Issue 188628
Button type filter added to Report Browser
Resolved in Pega Version 7.1.8
After navigating to the Report Browser and then back to another tab, clicking on any input field and clicking enter caused the columns filtering pop-up to appear even if the user was not on the Report Browser tab. This issue only occurred with the FireFox browser due to FireFox treating elements as the 'default action' of the form and using them as submits, causing a press of the enter key to fire off the onclick event for those buttons. In order to correct this, the type='button' attribute has been added to the filter