INC-219310 · Issue 717115
WorkSearchGadget updated in Theme-Cosmos-02-01
Resolved in Pega Version 8.7.2
The search icon was not working in Cosmos after update, which was traced to the search icon not having an action set. This has been addressed in Theme-Cosmos-03-01, but in this scenario Theme-Cosmos-02-01 was set as the Application definition instead of Theme-Cosmos-03-01. To resolve this, Theme-Cosmos 02-01-01 has been updated to use the newest version of the @baseclass.WorkSearchGadget section.
SR-A100572 · Issue 270091
getThread API respects Never create flag
Resolved in Pega Version 7.2.2
When setting initialization/persistrequestor = Never, a new thread was created on every getThread call where thread validation checks were not done. This allowed vulnerable thread names that were not checked and allowed to pass through. This was due to the getThread API not respecting the aCreateIfNotInDB flag, and has been fixed.
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-211208 · Issue 709647
Added fallback handling for missing Google Maps marker value
Resolved in Pega Version 8.7.2
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 709282
Access group context handling updated for Mobile
Resolved in Pega Version 8.7.2
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-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.
SR-A87989 · Issue 255978
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.
SR-A87923 · Issue 257159
Improved logging for Data Flow exceptions
Resolved in Pega Version 7.2.2
When an error occurred on a source shape in data flow, the page information was not reported in the error report and log. This was due to a handling error that lost the reference of the original page in this scenario, and the system has been updated to improve troubleshooting by retaining the reference and including it in the error report as well as reporting it in regular logs.
SR-A100251 · Issue 271797
Editing a decision table works on hardened system
Resolved in Pega Version 7.2.2
After enabling URL Encryption and URL Obfuscation in the Production Environment per Pega best practice recommendations to secure/harden an environment, an HTTP 400 error was thrown when attempting to Edit a Decision Table in Pega Marketing. This was an error in the URL decoding for the DisplayModalDialog HTML rules, and has been fixed.