SR-B72326 · Issue 325267
EmailListener handling updated for addressee errors
Resolved in Pega Version 7.3.1
When messages are handled by the EmailListener with more than one recipient (more than one TO: header and even sometimes more than one CC: header), the EmailListener activity will create a (sub-)case for each of these recipients, based on their email addresses from the TO: or CC: list. If an error was generated by one of the recipient email addresses in one of the groups (TO: or CC:) being invalid, only the invalid address was returned to the EmailListener for further processing. This meant the other addresses in the same group were ignored and no (sub-)case created for them. To address this issue, the handling has been changed: If an exception occurs while processing a recipient's name, the system will iterate through the Message to get recipients one by one. If the Address is valid it will be added to the list, and if it's invalid then extractEmailAddress API will be used to attempt to extract a valid email address and add it. If the extraction did not obtain a valid email address it will be logged and ignored. Please note that all this processing will be done if FailOnAddressException DSS is set to false (the existing behavior).
SR-B73213 · Issue 322353
CMIS-GetPropertiesResponse property mapping fixed
Resolved in Pega Version 7.3.1
The CMIS properties' data was improperly mapped to a "pyProperty" Page List property which was not part of the CMIS-GetPropertiesResponse data model, rather than mapping the data into the proper "pyProperty" Page List properties in the CMIS-GetRepositoriesResponse data model such as pyPropertyBoolean, pyPropertyInteger. This was caused by a defect in the Pega engine's CMISConnector module caused by changes made to simplify and consolidate the "map Properties" logic. The CMISConnector module has been repaired so that it correctly derives data type when giving a pointer to a PropertyDataObject:
SR-B57614 · Issue 322754
PegaMobile honors prompt for password check
Resolved in Pega Version 7.3.1
The Pega Mobile App option to 'Always prompt for password on start' was not saving the selected choice. This was caused by a conflict with "Do not save property data" in the persistence section of the property advanced settings, and has been fixed.
SR-B67236 · Issue 325268
Resolved infinite loop in offline app
Resolved in Pega Version 7.3.1
Pressing "Next" was causing an offline app to go into an infinite loop. This was found to be caused by two issues: there was a problem with back processing when deeply nested subprocesses were configured, and the handling was not working with a subprocess that had more than one 'from-connectors'. This has been addressed by modifying the implementation logic in process_flow.
SR-B69404 · Issue 320544
Map include enhanced with fallback "Show user location" function
Resolved in Pega Version 7.3.1
When Map was included in a section by checking the "Show user Location" option, the pxRequestor.latitude and pxRequestor.longitude options were empty in the clipboard. Also, in Microsoft Internet Explorer the user location was not shown and the default Boston location was given. This was traced to a null pum.GeolocationMarker.position in Microsoft Internet Explorer, and a fallback approach has been inserted to set the position from the existing previous value.
SR-B72669 · Issue 326687
FinishAssignment updated for offline mobile reports
Resolved in Pega Version 7.3.1
When a submitted report was saved in offline mode and then retrieved from the client store, the system seemed to only retrieve the N-1 version of the work object. Analysis showed that the call to open the object after being submitted only opened the first transaction and not the last transaction recorded for the case, and the issue was traced to Finish Assignment not saving the updated work-object to the client-store. To fix this, the system will call saveWorkAndAssignment in gotAFlow defined inside finishAssignment when "no next action".
SR-B36794 · Issue 322533
Added reindex check to RuleCheckin
Resolved in Pega Version 7.3.1
After creating new proposition data and saving it, pyPropertyReferences were changing on save of the Decision Data rule. Analysis identified the issue as happening when a rule was privately edited from a locked ruleset version and then checked in into another ruleset/version: rule references were created for the privately edited copy but when the privately edited copy was deleted at step 29, the references were also deleted and since the item being checked in was deleted in the same transaction the commit did not trigger reindexing and the references were not created again. To handle this edge case, a step has been added to the RuleCheckIn activity to reindex if .pzIsPrivateCheckOut == "true" && .
SR-B51112 · Issue 307512
Silverlight MSI file rebuilt without registry keys for bulk installation use
Resolved in Pega Version 7.3.1
MS Word Compatibility for 2016 Office 365 was generating messages like "Error in updating the Registry Key of (AllowLaunchOfElevatedTrustApps): Object reference not set to an instance of an object." This was due to a newly-added registry keys inclusion feature on Silverlight prerequisites that not supported for installing multiple systems. To address this, the Silverlight prerequisites MSI file has been re-built without the inclusion of registry keys
SR-B52083 · Issue 315414
Scrolling does not select checkboxes/buttons
Resolved in Pega Version 7.3.1
Radio buttons and checkboxes were becoming selected inadvertently while scrolling due to a touch events error. This has been fixed by setting the system to ignore a touch event when target is radio or checkbox while scrolling.
SR-B57228 · Issue 325976
Timer exit error fixed for STS SOAP
Resolved in Pega Version 7.3.1
If STS was enabled for a SOAP Connector and if a valid STS token was already available, hundreds of error messages about attempting to stop the timer were logged. This was traced to a step order error which started the timer and then exited before stopping it, and the missing step has been added.