SR-B2863 · Issue 275455
Improved offline decision shape handling for GoToPreviousTask
Resolved in Pega Version 7.3
The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.
SR-B34274 · Issue 291209
Improved offline decision shape handling for GoToPreviousTask
Resolved in Pega Version 7.3
The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.
SR-B5982 · Issue 279431
Tabbed form submission errors read by JAWS
Resolved in Pega Version 7.3
JAWS was not reading the error messages on the screen if the form submission was in a tabbed layout. To correct this, a setTimeout has been added to the reloadAcessibility function to call displayErrorTable.
SR-C88882 · Issue 431067
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.3
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.
SR-D22319 · Issue 493660
Corrected Flex UI Alignment issues in Microsoft Internet Explorer 11
Resolved in Pega Version 8.4
In Microsoft Internet Explorer 11, a UI rendering issue was observed when Report Definition uses many columns. This was traced to Flex not being fully supported in Microsoft Internet Explorer 11, causing the flexResize function inside pzpega_ui_doc_lifecycle to not perform well when calculating harness width based on content. While there was a workaround of using the flag "pega.u.d.DISABLE_FLEX_RESIZE" to indicate the system should not execute that function, the issue has been resolved by setting table layout to auto.
SR-C88882 · Issue 431069
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.1.4
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.
SR-C88882 · Issue 431068
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.2.2
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.
SR-D88490 · Issue 548185
SQL query performance improvement
Resolved in Pega Version 8.3.3
An SQL query was running sequential table scans with UPPER keyword while also doing an index scan without UPPER, causing performance issues. The query was used when there was a conflict of a Page property pointing to different Page in the hierarchy of class while creating a dedicated Index, and used the Upper function for a filter condition on pyClassName and pyPropertyMode. In the Database the value will be in MixedCase and the code will pass it as mixed case, so the Upper function has been removed from the query to utilize the index scan for filter condition and improve the query performance.
INC-188127 · Issue 678351
Updated cache key generation for ROPC
Resolved in Pega Version 8.6.3
After configuring outbound email functionality using MSGraph with OAuth 2.0, sending the emails failed consistently following passivation. Running "Test connectivity" in the Email Account data instance then seemed to restart the functionality and the automation "Create And Send Email" subsequently worked. This was traced to a missing username in the cache key generation for the Resource Owner Password Credentials (ROPC), which caused the same token to be fetched when attempting to dynamically generate different usernames, and has been resolved.
INC-188127 · Issue 678350
Updated cache key generation for ROPC
Resolved in Pega Version 8.8
After configuring outbound email functionality using MSGraph with OAuth 2.0, sending the emails failed consistently following passivation. Running "Test connectivity" in the Email Account data instance then seemed to restart the functionality and the automation "Create And Send Email" subsequently worked. This was traced to a missing username in the cache key generation for the Resource Owner Password Credentials (ROPC), which caused the same token to be fetched when attempting to dynamically generate different usernames, and has been resolved.