INC-192649 · Issue 706133
Basereference context available for attach content control
Resolved in Pega Version 8.7.2
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-195601 · Issue 685770
Basereference context available for attach content control
Resolved in Pega Version 8.7.2
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
SR-A92755 · Issue 261497
Fixed links display with privilege option in repeating grids
Resolved in Pega Version 7.2.2
When making use of the privilege option in the link control configuration as a condition to enable/disable the links in the repeat grid, the links were disabled/hidden even when the operator had the correct privilege. Analysis showed this happened in cases where the primary page was different from the page context on which the current part of the section was rendering (for example, when a grid or repeating dynamic layout is present), and it has been fixed by passing the current step page to the pega_rules_default.ValidatePrivileges function instead of passing the primary page.
SR-A91639 · Issue 260691
eForm PDF displays Japanese characters
Resolved in Pega Version 7.2.2
When trying to generate a PDF document using eForm PDF, Japanese characters were not displaying in the corresponding mapping field. This has been fixed by adding input parameters to get font details in the GenerateEForm activity and embed the font information in the PDF itself.
SR-A91639 · Issue 260831
eForm PDF displays Japanese characters
Resolved in Pega Version 7.2.2
When trying to generate a PDF document using eForm PDF, Japanese characters were not displaying in the corresponding mapping field. This has been fixed by adding input parameters to get font details in the GenerateEForm activity and embed the font information in the PDF itself.
SR-A22230 · Issue 245989
Focus corrected for auto-complete fields in Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using the Microsoft Internet Explorer 11 browser, selecting the value for an auto-complete field caused the cursor to move to the next field and then return to the first field. This was an issue with the focus and on-change refresh within the dynamic layout, and has been fixed.
SR-A22230 · Issue 244700
Focus corrected for auto-complete fields in Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using the Microsoft Internet Explorer 11 browser, selecting the value for an auto-complete field caused the cursor to move to the next field and then return to the first field. This was an issue with the focus and on-change refresh within the dynamic layout, and has been fixed.
INC-209071 · Issue 706039
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.7.2
When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.
INC-215877 · Issue 715233
Handling added for Oracle "NUMERIC" type
Resolved in Pega Version 8.7.2
When a product rule was created in an environment using Oracle, importing the product into the cloud environment with database table schema changes resulted in errors. This was traced to a change in Oracle's JDBC driver which was reporting Number as a JDBC "NUMERIC" type instead of the previous "DECIMAL". Pega uses the NUMBER data type and expected a type=DECIMAL for an Oracle number, causing the errors. This has been resolved by adding a check for flex numbers if column is NUMERIC.
SR-A102433 · Issue 271744
Optional warn forced for PersistSystemInfo
Resolved in Pega Version 7.2.2
When using com.pega.pegarules.monitor.internal.state.DatabaseInfoHandler.persistAllCurrentComponents(PRThread), errors are logged and the flow continues. As this may cause customer logs to fill up with errors, the function has been changed to warn forced and stacktrace will only be displayed if debug is enabled.