SR-121200 · Issue 184842
DB2 DateTime conversion fixed
Resolved in Pega Version 7.1.8
After inserting date values in DB2, using the select command and retrieving the above date values using RDB-List returned the date as one day earlier. The root cause of this issue was the logic used for reading and writing date columns in DB2. The logic was implemented in order to ensure that the values in the column were both saved and retrieved in GMT time zone. However, when a java.sql.Date object was retrieved from the JDBC metadata, it was returned as the date value at the time of Midnight, and the time zone was set to the local time zone by the metadata (instead of the expected GMT time zone). When preparing to return this value, the Date object was formatted with reference to GMT, which causes the Date object to have an hour subtracted and report a date value that was one day less than expected. To fix this, the datetime logic for the Date columns has been modified to use a DateFormat object in the system's local time zone.
SR-120412 · Issue 178850
Flow actions 'ResumeProblemFlow' and 'RetryProblemFlowFromstart' have been correctly marked as being unavailable for bulk processing
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.8
The Flow Problems flow actions 'ResumeProblemFlow' and 'RetryProblemFlowFromstart' are marked as being available for bulk processing which gives the impression they could be used to perform a bulk process operation when actually it is not possible. Each of these flow actions reference the same HTML Work- ActionDisplayError instance which is configured on the expectation that a specific value for pyFlowInError will be present on the newAssignPage, and this is the case when using the bulk processing approach via the portal. Therefore, this configuration has been marked as unavailable for bulk processing to avoid any future confusion. There is an alternative and recommended means by which bulk operations can be performed on assignments in the FlowProblems flow by using the "Flow Errors" list under the "Process and Rules category ? Processes" landing page. Please review the PRPC Help topic "Help: Working with the Flows with Problems report" for additional details.
SR-122313 · Issue 183428
Database Class Report properly populating Ancestors column
Resolved in Pega Version 7.1.8
When running the Advanced->Reports->Database Class Report, the "Ancestors" column was not populated for tenant level classes. The problem was with the method used to create the report querying the ClassMap using normal, tenantized APIs instead of Shared, so no data was returned. This has been corrected and the class ancestor values are now properly populated in the generated csv file.
SR-122313 · Issue 181185
Database Class Report properly populating Ancestors column
Resolved in Pega Version 7.1.8
When running the Advanced->Reports->Database Class Report, the "Ancestors" column was not populated for tenant level classes. The problem was with the method used to create the report querying the ClassMap using normal, tenantized APIs instead of Shared, so no data was returned. This has been corrected and the class ancestor values are now properly populated in the generated csv file.
SR-122641 · Issue 182813
Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.
SR-122641 · Issue 181600
Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.
SR-123051 · Issue 182680
LogOut' function corrected in the out-of-the-box operator menu
Resolved in Pega Version 7.1.8
When using the out-of-the-box provided "pyCaseMgrOperatorMenu" navigation rule, the menu contains two items - 'Preference's and 'LogOut'. Clicking on 'Log Out' was not performing log out operation. This was an error in the logout item of the navigation rule PYCASEMGROPERATORMENU, which was using an old script. This has been replaced with the new out-of-the-box logoff action.
SR-123681 · Issue 187957
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-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-D89672 · Issue 550527
Custom error label styles work for 'required'
Resolved in Pega Version 8.4.2
When using the default 'required' error message, the class "labelError" is added when the required field is empty. However, when the default 'required' is replaced by a custom error message, a UI error was seen because the class "labelError" was not added when the field was empty. This was traced to an error in the non-template to template code transform, and has been resolved by updating webwb_pzpega_ui_dlcelltemplate_js to add the labelError class based on the presence of an error message.