SR-D78274 · Issue 544093
Handling added for dual privileges with MSSQL
Resolved in Pega Version 8.5
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-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-A4589 · Issue 214117
Obj-Browse reads external mapping with external schema
Resolved in Pega Version 7.2
An Obj-Browse function missing the definition for the property/column lists was not reading the column-property mapping from the Class definition when using external schema. To correct this, getListSelectClause has been modified to use the property name as alias when external mapping is defined and a passed field value is a column name for classes mapped to an external table.
SR-A89295 · Issue 258931
Result count option added to Campaigns for performance tuning
Resolved in Pega Version 7.2.2
Slowness was seen when launching and running Field Marketing Campaigns. This was an issue with loading results using pxRetrieveReportData with paging enabled, as it fetched the total result count for each page. To resolve this, an option has been added to pxRetrieveReportData to disable fetching of total result count. This is available as Embed-QueryInputs property of type TrueFalse called 'pyReturnResultCount' when running report using pxRetrieveSearchData's pyReportParamPageName Parameter.
SR-D61094 · Issue 527341
Browser cache disabled to ensure fresh RAP file retrieval
Resolved in Pega Version 8.1.8
When using RAP download, reusing the same filename as a previous download caused the older file to be retrieved and not the newer version under that name. This was caused by RAP using the browser cache and downloading the same folder from service export directory. To resolve this, validation has been inserted to disable using the browser cache for the HTTP response.
SR-D32972 · Issue 513488
HTML entity handling added to URLObfuscation
Resolved in Pega Version 8.2.5
When URLObfuscation was enabled through the configuration settings, clicking on Operator -> Profile page generated an ArrayIndexOutOfBoundException. When obfuscation is used the decrypted string is parsed and the request map is populated, but HTML entities were not considered during this process. To resolve this, handling has been added for HTML entities and characters during obfuscation. Please note: URL Obfuscation is a legacy feature with many known limitations and it is no longer recommended that these settings be used.
SR-C6751 · Issue 349286
Corrected duplicate table names for DB2 z/OS import
Resolved in Pega Version 7.4
When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.
SR-C6751 · Issue 349078
Corrected duplicate table names for DB2 z/OS import
Resolved in Pega Version 7.4
When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.
SR-D28342 · Issue 504972
ChatMashup loading issue with IDP resolved
Resolved in Pega Version 8.4
When using a harness containing chat scripts via Mashup that called an activity to set parameters, attempting to launch the Mashup from an external application failed on the first attempt: an incorrect URL was generated and the activity was not triggered, resulting in an empty harness. The second attempt to launch the Mashup worked as expected. This was seen when using an IDP initiated Login with query string - pyActivity= classname.ActivityName, and there was a workaround to use SP initiated login or to use the activity URL directly on the IDP portal. Investigation showed that the resourcePath was coming as http in SSL enabled system, but the reqURI was still https. To correct this, the system has been updated so that if the reqContextURI starts with https and the requestURL starts with http, then the requestURL will be converted to https.
INC-222107 · Issue 732995
Trim added to refresh token request to handle extra spaces
Resolved in Pega Version 8.8
The request was failing when attempting to obtain an access token using refresh token when the previous access token was expired. This issue was due to an extra space in the scope in AuthenticationServiceOIDCSource.java, which has been corrected with an update which will trim the scope.