SR-123712 · Issue 184471
Resolved schema qualification for dedicated tables
Resolved in Pega Version 7.1.8
When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.
SR-123717 · Issue 192182
Purging of covered objects improved
Resolved in Pega Version 7.1.8
When purging a Cover item, the history of certain covered objects was not purged. This happened when the Cover and Covered classes belonged to different class groups. This happened because the 'getHistoryKeys' function tries to fetch the history details of a given key by looking into its history table. This was using the class group information from the archive configuration, which was not always the same for covered objects. To resolve this, the classgroup info will be fetched from its key - looking up Class map using the constructed class name will give the actual History Class name.
SR-123724 · Issue 184667
Updated RDEs invoked by collection rules
Resolved in Pega Version 7.1.8
Collection Rule was not invoking an RDE when the RDE is configured to be "When applied by a Rule Collection". However, it worked fine when the RDE is configured to fire "Whenever inputs change". This was found to be a problem with declare expressions not fired a second time. The RDE is configured with change tracking "when applied by a rule collection". In certain cases the system will try to avoid caching auto chaining status on to property as YES, so chaining is skipped the second time. Because this was not leading to the desired results, the code has been changed to cache the auto chain status for RDEs for collections.
SR-123741 · Issue 186119
Collapsible header text updated for accessibility
Resolved in Pega Version 7.1.8
When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."
SR-123750 · Issue 189489
Smoothed multiple portal tabs handling
Resolved in Pega Version 7.1.8
After opening the Case Manager developer portal, if a user portal was opened in a second tab using the 'Switch Portal' option shown in operator menu, returning to the developer portal tab caused that tab to be refreshed and the user portal tab to close. Previously, attempting to open a second portal session in a tab of the same window resulted in a 'Multiple sessions running' error. This limitation was removed in Pega 7.x. However, in this case the 'ShowDesktop' activity could not determine the 'ThreadName' parameter and defaulted to the 'Standard' thread and this change caused the refresh. The logic for determining the thread name has been updated to remove this issue.
SR-123776 · Issue 187714
Corrected assembler issue with XML header parsing
Resolved in Pega Version 7.1.8
An assembler issue after upgrade was causing SOAP services to have issues parsing the request header. By the time the parsing is completed, header properties in the clipboard page were missed. There was a workaround of dynamically switching to the old assembler, but this has been fixed.
SR-123785 · Issue 184291
"Required" checkboxes now working properly with Firefox
Resolved in Pega Version 7.1.8
When using Firefox, putting focus on a field which has "Required" checkbox checked and clicking "Enter" button caused the flow to ignore the checkbox and move forward without showing any error on the screen. This was an issue with the browser not supporting the event prevention code, and the system has been updated to ensure expected behavior.
SR-123809 · Issue 185686
Report schedule icon display fixed for SQL
Resolved in Pega Version 7.1.8
When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.
SR-123815 · Issue 188298
AddTime calendar function corrected for calculating expiry times
Resolved in Pega Version 7.1.8
Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.
SR-123820 · Issue 185192
Fixed truncated custom datetime in RD
Resolved in Pega Version 7.1.8
If a report was created on work objects that used a property of type DateTime in Report definition output, custom datetime settings were truncated. This was a problem with the grid implementation where the modified GenerateGridHTML. "D" was set always to propTypeForFormatting even for DateTime. It has bene fixed.