INC-153423 · Issue 615666
Timing update for Signature Capture Control
Resolved in Pega Version 8.4.4
A signature could be lost when using the signature capture control if a signature was drawn then the Accept and Submit links were clicked in quick succession. The problem occurred more frequently (although was not limited to) when there were multiple signature capture controls on the screen. This issue was due to transaction mismatch error for few pzAttachSignatureWrapper requests (signature post requests) caused by triggering the next accept request before completing the previous accept request. To resolve this, an update has been made to display busy indicator immediately when the first accept button is clicked.
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-151401 · Issue 615716
Context set for progressive scroll load of dynamic layout
Resolved in Pega Version 8.4.4
When setting pagination as 'Progressively load on scroll' for a repeating dynamic layout in a section with pagelist as the source, scrolling resulted in a null pointer exception and no further scrolling was possible. The issue was not seen when 'Progressively scroll on user action' was used. Investigation showed the activity Reload Section was failing because of the failure in the pre-processing activity, and this has been resolved by setting the correct context before making the pagination call.
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.
SR-A100503 · Issue 268474
Harness name field in flow accepts expression
Resolved in Pega Version 7.2.2
After upgrade, a harness issue was encountered where the generated flow was treating the pxFormName as String literal instead of Expression. This caused an error when trying to save a flow. To correct this, FlowFUA PopulateFlowActions function code used for Expression parsing in the harness has been updated.