SR-A3992 · Issue 211563
WSDL generation updated
Resolved in Pega Version 7.1.9
A coding error for the constants used in generating WSDL was creating a problem for some installations with the resulting data. This has been corrected.
SR-A4918 · Issue 211744
Reverted WSDL naming convention to previous style
Resolved in Pega Version 7.1.9
In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.
SR-A5413 · Issue 212956
Null check added to ParseXMLSAXRuleWrapper
Resolved in Pega Version 7.1.9
Thread lock error messages were being generated in the clipboard when trying to access a property pyNote whose value has been initialized with XML content. This was traced to ParseXMLSAXRuleWrapper adding a null value to the Clipboard Value list, and a null check has been added to prevent this.
SR-A959 · Issue 205668
Enhanced locking for EmailListener to detect and process auto-reply
Resolved in Pega Version 7.1.9
Due to thread locking timing, the EmailListener was not detecting 'autoreply' emails, causing infinite loops. This has been fixed by adding code to look for DSS Email/AutoReplySubject. If present, it will lock the requestor before getting the custom AutoReply setting and processing as expected.
SR-A4056 · Issue 211550
Corrected validation error for Extract rule field length
Resolved in Pega Version 7.1.9
A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.
SR-B47810 · Issue 306944
Data transform made consistent between desktop and mobile
Resolved in Pega Version 7.3.1
Data transforms were being evaluated differently on a desktop browser versus offline on mobile app, evaluating an 'undefined' property as equal to string "0" when offline. To correct this, the removeQuotedNumbers method has been reworked to not remove the quotes as "0" is different from 0 and the expression should not be modified.
SR-B66424 · Issue 314758
Backwards compatibility added for Stream datasets
Resolved in Pega Version 7.3.1
In order to ensure backwards compatibility for the Data-Admin-DataSet-Stream property pyKeys (formerly pyPartitionKeys), logic has been added to handle stream datasets created in previous releases: if pyKeys (the new property) is empty and pyPartitionKeys (the deprecated property) is not empty, then pyPartitionKeys will be used.
SR-B69030 · Issue 317845
Retry will auto-populate page list properties
Resolved in Pega Version 7.3.1
Page list properties were not being loaded during retries. This was due to the system using Obj-Open, which disables the auto-populate property before saving the import data in batches. That led to a condition where if the commit failed while batch saving, the retry committed the data one-by-one while auto-populate property was still disabled. To ensure expected behavior, Auto-populate property will be enabled before retrying committing the data one-by-one.
SR-B66457 · Issue 315578
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time
SR-B66457 · Issue 315580
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time