INC-231076 · Issue 738162
AddMessage function shows error on UI
Resolved in Pega Version 8.8
After updating from Pega 8.1 to 8.6, an addmessage function which previously displayed an edit validate rule error message was not working. This was an issue with textinput inside a grid, and has been resolved by adding a style to input text when it has a symbol left aligned and giving the error icon a z-index to show the message when the symbol is configured.
SR-125447 · Issue 191881
Email functions enhanced for customized authentication
Resolved in Pega Version 7.1.8
After upgrade, the system was not sending email from an account that did not specify a UserID or password. This was caused by PRPC requiring authentication. To allow for custom installations, the SendEmailMessage and EmailListener functions will check for the password; if it is null or empty, then it will set the authentication to false and will not try to authenticate.
SR-115104 · Issue 165556
IAC functionality enhanced for secure environments
Resolved in Pega Version 7.1.7
In order to ensure IAC functionality in a secure environment, the following updates were made: HTTPOnly support has been enabled for prGatewaySESSIONID cookies; encryption and obfuscation have been set up for web nodes; added a check for login-config.xml to add default-users.properties and default-roles.properties to the other application-policy.
SR-A2641 · Issue 207208
ActionAutoSubmit functionality updated for AJAX calls
Resolved in Pega Version 7.1.9
The ActionAutoSubmit functionality was not working when used in HTML due to the "Go Back" action only reloading a section (AJAX call) and not the whole page which would have called the doSubmit() function. This has been fixed by changing the submit implementation in order to force the function to be called even on AJAX reloads.
SR-A4515 · Issue 210886
Updated Outlook functions used by SendEmailMessage
Resolved in Pega Version 7.2
The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.
SR-A3548 · Issue 210897
Updated Outlook functions used by SendEmailMessage
Resolved in Pega Version 7.2
The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.
SR-A12537 · Issue 224734
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A10306 · Issue 221964
"isAvailableSpecificDay" function updated for time zones
Resolved in Pega Version 7.2
The out-of-the-box 'isAvailableSpecificDay' function was not consistent in routing work due to time zone conversion details that resulted in incorrect decisions. To correct this, the APIs used in time zone conversions have been updated to better handle offset DateTime formats.
SR-A12537 · Issue 224733
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A18466 · Issue 235142
Updated getDate function to use UTC
Resolved in Pega Version 7.2.1
Setting the system to the Brazil time zone ("UTC-03:00 Brasilia") with the operator set to Brazil/Acre caused a duplicate day to appear in October of every calendar year when the Microsoft Internet Explorer browser was used. This was traced to a difference in how the getDate function performed on the browser, and that function has now been updated to use getUTCDate() instead of getDate() to ensure cross-browser consistency.