SR-A24147 · Issue 249164
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A67518 · Issue 251304
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A24147 · Issue 253601
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer , Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A67518 · Issue 251275
Google Chrome check added for character count
Resolved in Pega Version 7.2.2
Unlike Firefox and Microsoft Internet Explorer, Google Chrome considers new line/carriage returns as two characters. This resulted in different character count values on refresh than when entering the text on the text area. This also could cause unexpected truncation of the text due to exceeding the max character value. To account for this, a condition specific to Google Chrome has been added to the rule utility function pzGenerateTextArea to take into consideration two characters for a line break or a carriage return.
SR-A100118 · Issue 287256
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-A102237 · Issue 271876
Unmapped columns from an external table skipped in DDL query generation.
Resolved in Pega Version 7.3
The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.
SR-B40706 · Issue 297501
Unmapped columns from an external table skipped in DDL query generation.
Resolved in Pega Version 7.3
The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.
SR-B6704 · Issue 289314
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-B40801 · Issue 317066
Check added to ensure downloaded files match the extension type given
Resolved in Pega Version 7.3.1
In the remote application that provided functionality for downloading files, no validation was performed on the requested file extension or file name during the request; these values could be constructed in the file request. However, this could allow attackers to send malicious links to end users by forcing a file to have a specific file extension such as .exe, .html, or .bat . In order to prevent issues, a check has been added to see if the extension of the filename and the actual file extension match. If they do not, the file will not be downloaded.
INC-146174 · Issue 602868
Chevron vs Back button in screen flow made consistent
Resolved in Pega Version 8.4.4
When using the TabbedScreenFLow7 harness with the "Enable navigation Link" and "Only allow navigating back to step" settings for the flow along with client-side validations, the validations were ignored when using the back button but using the chevron displayed a validation error. Investigation showed that the case action area buttons and bread crumb navigation were out of sync during the back button operation. This has been resolved by updating the ProcessStep function in BreadCrumbTrial library to pass skipValidations while calling gotoprevioustask.