INC-152217 · Issue 613928
Activity updated for Mobile attachment access
Resolved in Pega Version 8.4.4
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-137966 · Issue 597738
Embed-ReportFilter supports pyDateproperties
Resolved in Pega Version 8.4.4
After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.
INC-211208 · Issue 709648
Added fallback handling for missing Google Maps marker value
Resolved in Pega Version 8.8
The Google maps location position control was not showing the marker if the marker source was a Property. No issues were seen if a data page was used as the marker source. This was due to the pega.util.Dom.getElementsByName(markerPropertyHandle) being returned as null. Since the property value was not found in DOM, the latitude and longitude values were not resolved for the marker object. This has been resolved by relying on the markerPropertyValue as a fallback in case the property bound to the marker is not part of the DOM.
INC-214160 · Issue 709283
Access group context handling updated for Mobile
Resolved in Pega Version 8.8
After update, a new mobile application for a specific access group was not applying the correct access group for an operator with multiple access groups but instead used the default access group. This has been resolved by moving the logic responsible for switching access groups for Pega Mobile Client from the Authorization.getInitialAccessGroup class to the SessionAccessgroupInfo class to ensure Authorization/SessionAuthorization gets the information about the default access group for the current context.
SR-A103018 · Issue 271159
Mobile Client Cache populated with pyWorkPage info
Resolved in Pega Version 7.2.2
While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.
SR- · Issue 270969
Mobile Client Cache populated with pyWorkPage info
Resolved in Pega Version 7.2.2
While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.
INC-144601 · Issue 602425
Empty addresses removed from email
Resolved in Pega Version 8.4.4
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
SR-D65034 · Issue 529564
Check added for malformed query on F5 refresh
Resolved in Pega Version 8.1.8
A 500 Internal Server Error occurred when F5 was clicked to refresh the screen. This was traced to a malformed URL that was missing the '?' before the query parameters, and has been resolved by adding a check in the pzpega_ui_dynamicContainer_lite js file replaceHistory method that will insert the question mark if it is not present.
INC-230826 · Issue 733552
Legacy hardcoded WorkPage removed from ReassignAssignment
Resolved in Pega Version 8.8
When there was a child case Task available, attempting to transfer the case caused the system to update the Parent case .pxFlow(CreateTask) instead of the Task case .pxFlow(CreateTask). This was traced to the pyReassignAssignment activity having a legacy hardcoded page pyWorkPage defined, and this hardcoded page has been removed to resolve this issue.
SR-A87989 · Issue 255973
DSM Operations Guide updated for Interaction History Database Tables setup
Resolved in Pega Version 7.2.2
The DSM Operations Guide has been updated to clarify that when setting up Interaction History Database Tables in a Dedicated SchemasetupDatabase.properties file, the argument should be dbDataSchema and not dbSchema as was given previously. Also, data.schema.name=PEGADATA entries will take precedence if already entered.