SR-D33491 · Issue 511727
Code fragment removed to resolve CookieDisabledException
Resolved in Pega Version 8.2.4
After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.
SR-D43811 · Issue 511921
Code fragment removed to resolve CookieDisabledException
Resolved in Pega Version 8.2.4
After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.
SR-A99155 · Issue 253246
Mobile dirty page handling corrected
Resolved in Pega Version 7.2.2
When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.
SR-A92403 · Issue 264239
CustomApp login fixed for Sales Automation Portal
Resolved in Pega Version 7.2.2
When logging in for the first time using a custom app via the Sales Automation Portal, the progress bar would flow to the end but the portal would not open and errors were logged on the console. This was traced to a logic error in the HCLoadManager getOfflineStorageCount API call, and has been fixed.
SR-D18853 · Issue 503275
Visibility on client check removed to enable Pulse on click
Resolved in Pega Version 8.2.4
When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.
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.
SR-A91240 · Issue 259814
Corrected mobile app login load stream error
Resolved in Pega Version 7.2.2
In some circumstances, a "Failed to load stream" error was appearing when attempting to log in on the Mobile App. To fix this, the login process has been made more robust with the addition of the isSyncProcessingInProgress function to check sync progress, and a check has been added for the panel harness being set in the HCLoadManager js.
SR-A91327 · Issue 259570
Modified cookie name handling to clear operator sync between logins
Resolved in Pega Version 7.2.2
Full sync was happening only at the very initial time the user tried to login and not at every login, creating a scenario where an operator was given a synchronization package for the last logged user. This was an error with part of a session cookie name being hardcoded and not being cleared when the previous user logged out, and the logic has been corrected.
SR-D37757 · Issue 507967
Pulse delete icon repaired
Resolved in Pega Version 8.2.4
After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.