SR-A15710 · Issue 236472
Improved BIX extract handling for multiple active agents
Resolved in Pega Version 7.2.1
When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.
SR-A16337 · Issue 232778
OCXinstaller install.bat script for Windows explicitly sets .cab file path
Resolved in Pega Version 7.2.1
The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.
SR-A16582 · Issue 233320
Improved BIX extract handling for multiple active agents
Resolved in Pega Version 7.2.1
When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.
SR-A16736 · Issue 232994
Query table counts updated for IIF file with nulls
Resolved in Pega Version 7.2.1
While importing a jar through Import wizard in Designer Studio for a DB2 database, any Alter queries with SET NOT NULL or SET NULL fired the query 'CALL SYSPROC.ADMIN_CMD' to re-organize the altered table. That query generated the error "The number of host variables in the EXECUTE or OPEN statement is not equal to the number of values required" due to it not including the table names, and this has been fixed by populating the parameters in the place of '?' when downloading the SQL.
SR-A17544 · Issue 236778
Removed pagination size restriction on listview if page size is set
Resolved in Pega Version 7.2.1
When an application had more that 50 data-types, not all data-types were shown in the application packaging wizard due to the page size being set to 50 while the list view function was set to return a maximum of 50 results if pagination was enabled. The pagination size limit on listview has been disabled in cases where page size is set in order to remove this conflict and display the results as expected.
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-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-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.