SR-B50458 · Issue 306818
Bulk Action select fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
When using the Microsoft Internet Explorer 11 browser, clicking on the 'Select All' check box of the bulk action screen would select all of the assignments and then reset the flags to blank. This was an issue with select All property value being lost on refresh in Microsoft Internet Explorer 11, and has been resolved with an added Post value for the select All property in the pyBulkProcessingAssignDisplay section.
SR-B65922 · Issue 314665
Corrected Property type validation in Complex Question
Resolved in Pega Version 7.3.1
While creating a Complex Question with Property type Value list and referring an embedded property of type text in the Value list field, the validation message was not shown and system allowed the Complex Question to be saved successfully. Referring a top level property of type text (.ResponseText) showed the validation message (.ResponseText is not a valid Value List), but referring an embedded property type of text (.SurveyResponses(CEP).ResponseText) did not show the validation message. This was caused by missing handling, and has been corrected by modifying the ValidateSurveyEmbedPropertyMapping activity to check the last property mode for valuelist type.
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
SR-B49479 · Issue 305656
Values localized in Data Migration Wizard final review
Resolved in Pega Version 7.3.1
Values were not getting translated in Data Migration Wizard in the final review screen. This has been fixed.
SR-B69082 · Issue 317647
Support added to data import wizard for Enhanced Work ID prefix/suffix
Resolved in Pega Version 7.3.1
While creating work objects using the data import wizard, the pyID did not include a suffix that had been added to the work object ID. This was due to custom logic for generating workId being called in DataImportUtilsImpl rather than reusing the existing activity GenerateID in Work- class. In the custom logic, suffixId is not used and therefore was not passed. To improve flexibility, changes have been made in the import code to call the activity GenerateID for generating the WorkID using both the prefix and the suffix ID.
SR-B64134 · Issue 313542
Workaround added for Oracle 4000 character column value max
Resolved in Pega Version 7.3.1
Due to an Oracle limitation, RD on a clob column fails if the column value is of length greater than 4000. To work around this, support has been added to retrieve data from a clob column of length greater than 4000 characters using report definition based on DASS setting "reporting/retrieveFullClobContent" defined on "Pega-RULES".