SR-133734 · Issue 205290
Added handling for remaining character count inconsistency with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.9
In ie browser, new line is interpreted as "\r\n". This caused the remaining character count of a text area control to be inconsistent in the Microsoft Internet Explorer 8 browser due to the browser sometimes calculating the size of a new line character as one instead of two(\n\r). To handle this, the logic for remaining character count has been updated in the text area JS.
SR-A1538 · Issue 209276
prvisiointerface.cab unblocked
Resolved in Pega Version 7.1.9
Effective with earlier ML versions of Pega7, several OCX functions were intentionally deprecated and replaced with Silverlight functions: Prbatchscanning prDeveloper prpackagecominterface prvisiointerface. However, it was found that there are two Word features around the embed merge function requiring prvisiointerface.cab that will produce some visual problems on the screen referring to the missing cab break if the files are ported from an earlier version of PRPC and prvisiointerface.cab is unavailable. Therefore, prvisiointerface.cab has been unblocked and restored for use.
SR-A2027 · Issue 205651
Reworked decision table conflict check logic for combined rows
Resolved in Pega Version 7.1.9
In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. This has been fixed by adding a new property pyColumnDataType for Decision tables which will hold the data type of the expression/function/property mentioned in the column during FUAssembly, and then using it in the testConsistency code instead of the existing design.
SR-A204 · Issue 205451
Resolved sporadic NPE on TransferAssignment
Resolved in Pega Version 7.1.9
A null pointer exception was sporadically being being generated by the pxTransferAssignment activity. This was found to be an issue where a previous step to open the work object failed and the TransferWorkPage was therefore not created, followed by the absence of that page leading to the failure of the WHEN condition that was using the Rule-Utility-Function hasMessages. The handling has been updated to avoid this issue.
SR-A2047 · Issue 205630
Resolved AddWorkHistory length error
Resolved in Pega Version 7.1.9
The "AddWorkHistory? activity was generating an error when the property pyInstructions contained more than 64 characters and was copied into pyLabel without taking care of the length restrictions imposed on these properties. This has been resolved by implementing the required length restrictions before copying.
SR-A2353 · Issue 206676
Adjusted process timing to address resolve error
Resolved in Pega Version 7.1.9
When a Payment case created as the child of a Supplier claim case was resolved, a processing error was generated. This was traced to a timing issue where the Resolve activity removed pyWorkCover from the clipboard before the Supplier Claim Wait assignment was fully completed. A check has been added to ensure necessary elements have been passed before clearing the clipboard.
SR-A2425 · Issue 209338
Improved RD requestor response time
Resolved in Pega Version 7.1.9
D_ManagerWorkGroups is loaded using Report Definition. Some installations were reporting an excessive load time due to referring data page activity; to improve performance, the extra processing has been moved to post activity.
SR-A3072 · Issue 206962
Attachment visibility fixed for mobile devices
Resolved in Pega Version 7.1.9
When attachments were uploaded to a mobile device, they were not immediately visible and required a refresh to be displayed. This was found to be an issue in the signature control and Attach content control where the data page referred to in the attachments display was not removed when a new attachment is added. For this release, the data page removal part has been moved to the saveattachment activity. In the next release, all attachment controls will call an API designed for that purpose.
SR-A3670 · Issue 207984
Added trim function for Operator full names exceeding max length
Resolved in Pega Version 7.1.9
If an OperatorID has a full name that exceeded 64 characters, the error ".pyWorkParty(Creator).pyLabel: "Ms [-------------------Operator Full Name--------------]" is too long, maximum length allowed is 64" appeared. To avoid this issue, the pyLabel will trim the full name to 63 characters.
SR-A3773 · Issue 210780
SLA rule form corrected to allow 3 digits in days field
Resolved in Pega Version 7.1.9
Due to an error, the SLA rule form had a limitation of 2 characters for entering the number of days for goal/deadline/passed deadline options. This has been corrected.