INC-143260 · Issue 599304
Overlapping columns fixed in ReportViewer
Resolved in Pega Version 8.2.8
When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.
INC-152084 · Issue 620951
Handling added for cross-origin DOM exceptions
Resolved in Pega Version 8.4.4
When an openURLWindow action was used to open any other domain, DOM exceptions were generated related to cross-origin iFrames communication and the UI became unresponsive. This has been resolved.
INC-144387 · Issue 605342
Support added for allow list for LaxRedirectStrategy
Resolved in Pega Version 8.4.4
When using Connect REST with POST to access a third-party service deployed on multiple nodes, the load balancer sometimes replied 302 with Location header. The ability to allow the REST connector to automatically follow these redirects even in the case of POST messages is supported by Apache http client via LaxRedirectStrategy, but REST Connectors need both rule and engine enhancements to allow for this. To support this use, an allow list has been implemted for hostnames. This will allow the connector to be configured to follow the LaxRedirectStrategy only when the hostname of the redirect location is in the allow list. The default will continue to block the redirect.
INC-132771 · Issue 584958
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.2.8
On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.
INC-145939 · Issue 606898
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.4.4
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-148375 · Issue 607798
"Today" will set date-time in the respective operator timezone
Resolved in Pega Version 8.4.4
When a Date was entered using the "Today" option in Datetime control, the Date set used the system date and Time was taken from Timezone specified for the operator. This created issues for a scenario such as operator being set to America/New_York/ EST while the application was accessed in another country such as India or Japan. This was a missed use case and has been resolved by adding code to get the date-time in the respective operator timezone and setting it on click of date-time controls.
INC-134412 · Issue 577541
Proposition filter maintains eligibility criteria
Resolved in Pega Version 8.2.8
Eligibility details were occasionally lost when updating Offers. This was traced to a configuration that could cause individual criteria rules to be deleted when rows were added in the middle of the list. To resolve this, validation has been added to each eligibility criteria row to ensure that all expected values are entered for each row, and validation has been added to the logic string when advanced mode is used for offer eligibility criteria.
INC-150222 · Issue 612576
Custom client-side future date validation works on mobile
Resolved in Pega Version 8.4.4
After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.
INC-148817 · Issue 604971
Added check for ABAC policy to getassignmentdetailsinternal
Resolved in Pega Version 8.4.4
When an attribute based access control (ABAC) policy was defined on a particular class, the policy was properly applied when browsing instances of the class and directly opening the work object. However when an associated assignment was processed via the DXAPI (using the assignments service) the security was not applied and users who should not have access were able to progress the case. This has been resolved by adding a check in the pzgetassignmentdetailsinternal activity to check for work object opening security.
SR-D96430 · Issue 561525
Updated visibility condition expression handling for decimal values
Resolved in Pega Version 8.4.4
After upgrade, any visibility condition expression failed to evaluate decimal values that used precision. When 0 (zero) was entered as a value in the input field, a button that was configured to show was visible as expected. When the value was entered as 0.0, the input failed and the button did not show. The problem did not happen "Run visibility condition on client" was enabled. Investigation showed this was an issue with how the When expression was evaluated and calculated within JspWhenEvaluate, and has been resolved.