SR-A34 · Issue 204505
Pega Lookup JSP tag correctly retrieves Chinese characters
Resolved in Pega Version 7.1.9
When the pega:lookup JSP tag did a field value lookup on pyCaption to retrieve the field value consistent with the locale, any Chinese characters embedded in the HTML pages used to generate the PDF rendered correctly but '?????' appeared in the PDF content instead of the Chinese characters configured in the Field-Value pair. This was caused by an issue in the code which caused the system to incorrectly identify NVARCHAR columns as being VARCHAR columns. This has been fixed., and the encoding for TestDatabaseNew has also been set to be UTF-8 to ensure the Non-ASCII characters in the tests are handled properly in all workspaces.
SR-A3428 · Issue 212424
Modified ClassName pass method for external DBs
Resolved in Pega Version 7.1.9
When DB2 is used as external DB (external table has a date column) and PRPC is hosted on a DB other than DB2, performing an obj-save into an external DB2 database failed with an SQL error. This issue occurred when a class was mapped to a table in an external DB which was not same as Pega hosting DB. In class PageDatabaseMapperImpl.java , function getDatabaseTypeFromEngine is used to check the database type when column type is Date, but the function was using a hardcoded value of class to determine the database type. This has been changed to pass className as parameter and use it to determine database type.
SR-A3744 · Issue 209253
Resolved Vtable NPE during engine start
Resolved in Pega Version 7.1.9
If a Rule-Access-When was defined on the class Data-Admin-System-Settings, search was initialized before the VTable is initialized. While initializing search, a DASS was set and a save operation was performed on the DASS which then tried to perform a security check and attempted to retrieve the Rule-Access-When from the unpopulated VTable cache. This led to an NPE. To resolve this, changes have been made so that search will be initialized after Vtable is populated.
SR-A940 · Issue 205402
Locking issue resolved for importing PUI jars
Resolved in Pega Version 7.1.9
Errors were being generated when importing PUI framework jars. This was an issue where the savepoints created in Saver.executeUpdate needed to be explicitly released on PostgreSQL to avoid locks from accumulating for each of the nested transactions, and the problem has been resolved.
SR-A990 · Issue 205075
Post-upgrade deferred list mapping reference inserted for new classes
Resolved in Pega Version 7.1.9
After migrating, the processing of the deferredlist while performing an updatestatus operation generated an exception from pzMapCases. This was caused by a class mapping issue where the new classes (InsertRuleSummary, UpdateRuleSummary, DeleteRuleSummary) added in DeferredOperationsImpl did not have interfaces in DeferredOperation. This has been corrected.
SR-A4056 · Issue 211550
Corrected validation error for Extract rule field length
Resolved in Pega Version 7.1.9
A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.
SR-A9147 · Issue 220746
Documentation updated for command-line BIX extractions
Resolved in Pega Version 7.2
The documentation for "Using a stand-alone command-line BIX extract process" has been updated to refer to the BIX 7.1 User's Guide regarding configuring the necessary database connection properties set (prbootstrap, prconfig, etc.).
SR-A5258 · Issue 213386
Documentation updated to reflect change to read-only getProperty pages
Resolved in Pega Version 7.2
In recent versions of the system, getProperty() was modified to support the creation of a property on a read-only page. However, even though the property has been created, it is not possible to set its value. This was not clearly indicated in the documentation, and read-only exceptions were being generated when putString() or setValue() attempted to give a value for the property on a read-only page. The documentation has been updated to clarify this use case.
SR-A6768 · Issue 215093
JDBC connection URL documentation updated for JBOSS installation
Resolved in Pega Version 7.2
An error was found in the JBOSS installation document: the JDBC connection URL defined inside the standalone-full.xml should not have forward slash (/) before the database name, i.e. the format below is incorrect: jdbc:oracle:thin:@//localhost:1521/dbName Instead, the forward slash before data name should be changed to a colon (:), for example: jdbc:oracle:thin:@//localhost:1521:dbName This documentation issue has been resolved by adding a section clarifying the necessary connection information and the method for creating a connection string, along with updating all connection-url steps to either include this information or a pointer to the new section.
SR-A5730 · Issue 213019
Namecase check added to DB2/ZOS split schema installation
Resolved in Pega Version 7.2
An omission in the documentation for the installation wizard guiding the creation of a split schema on DB2/ZOS failed to specify that the database username on the UI screen or in the setupDatabase.properties file as well as the properties in the DB2SiteDependentProperties file are required to be in all upper case. As a result, some installations experienced a runtime exception and an unexpected process termination due to name mismatch. The documentation has been updated. and a check has been added which will take a supplied mixed/lower-case user name and uppercase the value used to set the currentSQLID parameter.