SR-A7590 · Issue 216110
Corrected parameter page used when Flowproblems restarts
Resolved in Pega Version 7.2
Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.
INC-160767 · Issue 628374
Email headers correctly mapped when using MSGraph
Resolved in Pega Version 8.5.3
The value of "Send Date" was not correctly populated when using MSGraph instead of IMAP, causing the Email Listener to fail. Microsoft populates the "sendDateTime" field in the JSON with the value of the RFC 822 email header "Date:", but this value was not being passed to Java object of type "Message" as part of the query. To resolve this, ReceivedDateTime and SentDatetime have been added in the select filter of getMessagebymessageID.
INC-160767 · Issue 628373
Email headers correctly mapped when using MSGraph
Resolved in Pega Version 8.6
The value of "Send Date" was not correctly populated when using MSGraph instead of IMAP, causing the Email Listener to fail. Microsoft populates the "sendDateTime" field in the JSON with the value of the RFC 822 email header "Date:", but this value was not being passed to Java object of type "Message" as part of the query. To resolve this, ReceivedDateTime and SentDatetime have been added in the select filter of getMessagebymessageID.
INC-174267 · Issue 657129
Wait action persists when using Urgency Adjustment
Resolved in Pega Version 8.5.5
When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.
INC-174267 · Issue 669672
Wait action persists when using Urgency Adjustment
Resolved in Pega Version 8.6.2
When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.
SR-B71077 · Issue 326659
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
SR-A6223 · Issue 214939
Resolved WSDL SOAP exception when using target namespace
Resolved in Pega Version 7.2
When adding a well-defined XML ParseRule as a Request Header, saving and checking in the rule caused the Deployment results link to generate the error "Caught exception while creating WSDL for service package: : com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException Header message is included with method namespace instead of targetnamespace" This was an error in the code handling a target namespace for Request Headers (configured on the Service Soap -> Requests tab), and has been fixed.
SR-A10189 · Issue 222038
Handling added to set baseclass when using Bulk as Update
Resolved in Pega Version 7.2
The use case was missing to properly handle setting the baseclass when Bulk action was selected as an Update process. This has been added.
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-D81532 · Issue 544429
Corrected case-mismatch when using Top Ranked in a subreport
Resolved in Pega Version 8.3.2
Incorrect SQL Generation was seen when using the combination of Union ALL (more than 1 distinct tables) and Rank in Sub report. The sub-report had a ranking logic to pull records with greatest “pxUpdateDateTime”, but when executing the main report definition rule, Oracle responded with the error "There was a problem getting a list." Investigation showed that the query generated was not able to match the columns because they were given as pxUpdateDateTimeR1 in one and PXUPDATEDATETIMER1 in another. This only happened when display Top Ranked was selected in the subreport, and was due to Oracle being case-sensitive. This has been resolved by updating the system to get the correct column alias for rank in a subreport.