SR-A1273 · Issue 197681
PRPCTask is now tenantized
Resolved in Pega Version 7.1.9
On a multi-tenant environment with HTTP event, it was not possible to see the options for warm\blind transfer with interaction from a tenant layer. This was an issue with the task taking the user ID information but not taking the tenant information, so the acceptance of the interaction on the portal was not getting delivered to the desktop. To correct this, PRPCTask is now tenantized.
SR-A3149 · Issue 209034
Added handling for Oracle functional indexes of length '1'
Resolved in Pega Version 7.1.9
The SchemaChangeUtils class was throwing a java.lang.StringIndexOutOfBoundsException when an administrator attempted to view the "Missing PRPC Shipped Schema" section of the "PRPC Schema Report" page after upgrade (System -> Release -> Upgrade -> PRPC Schema Report). This appeared to lead to the message "Can not render section" in the PRPC schema report UI. The StringIndexOutOfBoundsException was due to Oracle functional indexes of length '1' which were not handled while doing a substring in schemaChangeUtils class: this handling has now been added.
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-D62754 · Issue 559848
PrepareResponse updated to explictly close Input Handler
Resolved in Pega Version 8.2.7
When using prpcServiceUtils to export a product in a Windows+Weblogic environment, attempting to export repeatedly using the same archiveName with the intention of overwriting the older product with the newer one in the ServiceExport directory failed with a FileNotFoundException. Investigation showed that the product file that was created by the pzExport REST call was not being released by the Weblogic File Handler process. Due to this, the next time the call was invoked the system tried to create the same file in the directory but failed due to the earlier File handle lock. To resolve this, the system has been updated to explicitly close the InputStream using try-with-resources.
SR-D78274 · Issue 544092
Handling added for dual privileges with MSSQL
Resolved in Pega Version 8.2.7
After setting up dual privileges, the Admin user was able to create a table but the base user received an "insufficient privileges" error. Investigation showed this was an issue when using MSSQL: the generated grant statements used the server login name as the user in the grant statement, instead of the database user. For all other databases, the username passed into the connection is the correct user to use for grants. Only MSSQL has a distinction between this connection user name (the login) and the database user, and since the login did not exist in the user table, the grant failed. To resolve this, when MSSQL is used, the system will fetch the underlying database user when determining the user for grant statement generation.
SR-D84190 · Issue 547173
Post-Import Migration Agent query optimized
Resolved in Pega Version 8.2.7
A Post-Import Migration agent belonging to the Pega-ImportExport Ruleset and set to run every 60 seconds by default triggered the SQL query "select ASTERISK from pegadata.pca_CWT_CXP_Work_Interaction" which ran for an excessive amount of time, caused a utilization spike, and then crashed the utility nodes. Investigation showed the excessive run time and load was caused by the query fetching a very large number of results. To better handle this scenario, the query usage has been updated.