SR-A14336 · Issue 230881
Resolved NPE when @checkForSubstitute used
Resolved in Pega Version 7.2.1
If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.
SR-D46681 · Issue 514435
SnapStart supports SAML2 Authentication
Resolved in Pega Version 8.1.8
When using an HTTP Post to SnapStart into Pega using PRCustom style or PRAuth style SAML authentication, the login was looping back to the login request. Investigation showed that the Pega ACS was posting data properly back to the RelayState URL, however the login activity was not getting the SAMLResponse and simply sent a SAML Login Request again. This has been fixed by updating reqContextURI in case of SAML2 Authentication service so pyActivity=value will be passed.
SR-A11447 · Issue 243018
Importing an archive no longer fails when using DynaTrace
Resolved in Pega Version 7.2.1
Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.
SR-A12357 · Issue 230904
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A12357 · Issue 231872
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A14004 · Issue 231765
Flow designer XML fixed when using copy/paste
Resolved in Pega Version 7.2.1
Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.
SR-A21835 · Issue 243872
Flow names can now be found when using duplicate search mechanism
Resolved in Pega Version 7.2.1
When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.
SR-A18902 · Issue 237052
Updated tab generation for failed 'when'
Resolved in Pega Version 7.2.1
When visible 'whens' were configured on accordion, the content was not properly displayed below the header if the 'when' condition was false. This was caused by an error in the generation of defaultTab based on visible 'when's, and the GenerateTabbedSectionLayout RUF has been updated.
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.
SR-A22016 · Issue 242244
Removed screen flicker when editing WorkObject
Resolved in Pega Version 7.2.1
Whenever a DynamicContainer action was invoked from the master details of an RDL row, a new harness was opened and dismissed, causing the RDL to momentarily appear on the screen. This has been fixed.