SR-A18100 · Issue 234215
BIX documentation updated for new "-J" timezone conversion option
Resolved in Pega Version 7.2.1
A -J option has been added to BIX to allow the specifying the timezone for datetime properties to be converted to when written to the XML output file. The documentation is as follows: A new command line option J is being added to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified timezone is not valid, it defaults to GMT example :How to specify this option: "-J" "UTC+5:30"
SR-A18333 · Issue 237135
Corrected JSON page group handling
Resolved in Pega Version 7.2.1
If DataSet-Execute method was used to cache a CustomerPage from Clipboard, using the same DataSet-Execute method to retrieve it from the cache using the "Browse by key" operation was not working correctly: If the page contained a page group property, then the retrieved CustomerPage contained additional invalid entries that led to errors in the mapping logic. This was an issue with the Clipboard page JSON converter not properly handling page groups, and has been corrected.
SR-A18550 · Issue 234678
Strategy and data flow behavior more consistent
Resolved in Pega Version 7.2.1
Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.
SR-A18657 · Issue 239739
property-ref mapped table updated during optimization
Resolved in Pega Version 7.2.1
On optimizing any top level property after upgrade, the existing values present in the reference property columns were getting reset. This has been corrected.
SR-A18716 · Issue 234856
Corrected Hotfix Manager mismatch between 7.2 versions
Resolved in Pega Version 7.2.1
The version of 7.2 used in the Hotfix Catalog was different from the version used in Hotfix Manager when installing DLs. An update to the HM code was made to correct this mismatch.
SR-A18766 · Issue 235529
Documentation updated to reflect MaxRecords blank value = 0
Resolved in Pega Version 7.2.1
The developer help for the Max Records field on the Schedule tab of the Agents rule form states "If this field is blank, the default value is 50.". In actuality, a blank value in Max Records behaves the same as a value of 0, i.e. "process all entries in its queue before sleeping". This was a documentation error, and the help topic in question has been updated to reflect the actual results of the blank field.
SR-A18909 · Issue 235146
Strategy and data flow behavior more consistent
Resolved in Pega Version 7.2.1
Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.
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-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-A19355 · Issue 235876
Landing page Header correctly displays VBD Planner
Resolved in Pega Version 7.2.1
The Pega Marketing portal header was overlapped by the VBD Planner header, creating problems accessing the buttons on the portal header. The newly developed VBD Planner client, running as a control, did not take portal layout into consideration, and the header has been adjusted so the portal header is exposed properly.