SR-A18998 · Issue 236896
Document updated for WAS JNDI dataSourceAdmin binding identifiers
Resolved in Pega Version 7.2.1
Page 80 of the Pega 7.2 Platform Upgrade Guide describes the procedure to create the JNDI binding identifiers for dual-user configuration. In that description, the String value for the following identifiers is not correct. prconfig/database/databases/PegaDATA/dataSourceAdmin prconfig/database/databases/PegaRULES/dataSourceAdmin The string value should be the "the JNDI name of the Admin data source for the data/rule schema" instead of "the schema name of your data/rules schema" The same issue is present in the Pega 7 Platform Installation Guides for WebSphere, and both documentation areas have been updated.
SR-A19075 · Issue 236452
Corrected class structure created by SOAP Integration Wizard
Resolved in Pega Version 7.2.1
An issue was found in the class structure created by the SOAP Integration wizard after upgrade. This has been fixed by updating the pyCreateGenerationRequest data transform to append servicename.
SR-A19079 · Issue 237094
Made date-time control height consistent
Resolved in Pega Version 7.2.1
Control height was inconsistent for date time controls that did not allow text entry, depending upon the control type and presentation setting. This was particularly noticeable when dynamic layout was configured with "inline double" or "inline triple". Extra padding of 2px was found in the non-text-entry control, and this has been removed to make it align to what it is in the text-entry-allowed date time.
SR-A19104 · Issue 237289
Ability added to set TTL on data sets
Resolved in Pega Version 7.2.1
An enhancement has been added to Data Flow datasets to allow setting the Time To Live (TTL) on DDS stores from the canvas. This allows setting an expiry date on cached data, which is essential when working with large streams of data.
SR-A19159 · Issue 237816
Enabled custom parameter input for PushBodyCountVar
Resolved in Pega Version 7.2.1
After importing custom markup language based on JSP 2.0 tlds and mustache templates and writing a custom HTML rule to generate JSP, the error s were generated relating to the default value of aTagPushBodyCountVar parameter. To enable the custom input, the generateCustomStart() method has been modified to use a passed-in parameter by way of aTagPushBodyCountVar instead aVisitor.getPushBodyCountVar().
SR-A19167 · Issue 242469
Modified decision table handling for Connect-REST
Resolved in Pega Version 7.2.1
Authorization problems in opening the pyOutboundIdentifierDecoder decision table were causing Connect-REST failures. While it is recommended to only initialize the decision tables for legacy mapping DSS(json/legacyMapping) and not initialize the decision tables for normal JSON mapping, ServiceHelper and RulegeneratorREST have been updated with a check to properly handle the presence of decision tables.
SR-A19172 · Issue 236714
Managed unique constraint violation error for BIX
Resolved in Pega Version 7.2.1
When running multiple extracts using agents and pxExtractDataWithArgs at the same time, a unique constraint violation error was produced in the logs. This occurred when the extracts had the same time stamp down to the millisecond and an entry is added to the pr_log table when each extract starts. The pzInsKey for two extracts that run at the same time was identical, thus leading to this error. To resolve this, the thread name will be appended when the extract is run from an activity.
SR-A19181 · Issue 240871
dropdown menu item names correctly persist after click
Resolved in Pega Version 7.2.1
Once a dropdown was selected from a number of menus in the user portal, the name of the clicked menu disappeared upon recheck. The API has been updated to read the tooltip from the icon element if it is not already present.
SR-A19219 · Issue 237911
RACache performance improved
Resolved in Pega Version 7.2.1
Pega0005 alerts were appearing during system startup, and queries were taking an excessive amount of time. Bind variables are now used in the RACache loading query at server start up to improve performance.
SR-A19242 · Issue 235997
Default team label localized in MyTeams screen
Resolved in Pega Version 7.2.1
Localization has been added to the default team label in the My Teams screen.