SR-A18600 · Issue 249163
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 250181
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 249161
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 250180
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A20539 · Issue 244590
Refresh condition rendering fixed for pyCaseManager7 Harness
Resolved in Pega Version 7.2.2
The Refresh Condition for pyPortalContent in pyCaseManager7 harness was not rendering Case Manager properly even when the Refresh Condition for pyPortalHeader and pyPortalNav worked as expected. This was an issue with the Screen Layout iframe height being set to 150px when size to content was unselected, and has been fixed with an added style in pzbase-div-layouts.CSS to consider CT div while setting height to 100%.
SR-A11347 · Issue 250646
Updated authorization logic for Stream Assembly
Resolved in Pega Version 7.2.2
Triggering stream assembly was resulting in an "unauthorized"or "rule not found" exception relating to the rule existence validation code executed in the pzValidationSections RUF. This has been resolved with the addition of logic to the Stream Assembly function that runs a validation check for database authorization before opening the activity.
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.