SR-120103 · Issue 177698
Headers auto-expanded when printing from portal
Resolved in Pega Version 7.1.8
When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.
SR-120195 · Issue 180041
Smoothed adding rows to a repeat grid after canceling previous action
Resolved in Pega Version 7.1.8
When adding an item to the Repeat Grid, a small modal is opened to allow value entry to associate with that row. However, canceling the modal and then clicking on the button to add a row failed to open the modal a second time and it was not possible to add another row to the Repeat Grid. This was caused by the previous canceled modal call remaining active resulting in the new event being skipped. To correct this, the modal dialog incall property will be reset so it may be properly opened as expected following a previous cancelation.
SR-120218 · Issue 180532
Corrected dismissal of discard/cancel modal popup
Resolved in Pega Version 7.1.8
The out-of-the-box discard and cancel modal pop up was not closing up on single click. This was caused by a redundant action from the pyNewCaseHeaderInner section that has now been removed.
SR-120224 · Issue 178688
Potential vulnerability closed in XML stream generation
Resolved in Pega Version 7.1.8
A potential security issue was found with the XML stream generation and runtime, and has been corrected.
SR-120276 · Issue 179709
Corrected handling for DecimalPrecision Property Qualifiers in Advanced tab
Resolved in Pega Version 7.1.8
When DecimalPrecision Property Qualifiers were added to Advanced tabs, the Min/Max character limitation was not working for numeric input (Decimal) in pxTextInput or pxNumber. This was caused by an error in the initialization, and has been corrected.
SR-120329 · Issue 178133
Assembler compatibility issue resolved
Resolved in Pega Version 7.1.8
After upgrade, web services that modify the Header were failing due to a compatibility issue with the default assembler. While there was a workaround of giving the value of 'true' to the dynamic system settings 'Owning ruleset: Pega-IntegrationEngine' and 'Setting purpose: switchtooldassembler', this has been resolved.
SR-120454 · Issue 188836
Fixed error handling for MDB listener
Resolved in Pega Version 7.1.8
JMS MDB listener was failing and throwing 'NoClassDefFound' errors in the PegaRULES log file. The issue was found to be the error reporting in one of the integration methods, and has been fixed by modifying the ServiceAPI.generateErrorMessage such that if LogHelper cannot be used, an error is reported in the system error file and the listener continues.
SR-120477 · Issue 180530
Smoothed navigation for multiple screen trees
Resolved in Pega Version 7.1.8
In a tree navigation screen flow with multiple screens, the screens have client side validations which were not working when navigating from the tree navigation control link but did work when the "Next" or "Back" buttons were clicked. This was found to be a problem in the work flow UI doc submit method where validation was skipped if the Activity was "GoToPreviousTask". To resolve this, a check was added (previousEntryPoint) if submit is called from back button of screen flow.
SR-120525 · Issue 186509
Added handling for special characters in PDF Eforms
Resolved in Pega Version 7.1.8
PRPC uses a third-party library 'iText' to read and write PDF 'Eform' documents. It was found in some cases that if the input document contains fields ("Acrofields") that contain special characters (in particular the '#' hash/pound symbol) and/or accented characters, then the iText library would throw an error. To eliminate this, a check of the Field Name has been added to ensure it has a value before doing anything with it. If it is empty, that will be logged. As a workaround, it was found that by editing the input PDF file (using an appropriate third-party editor/generator) and ensuring that no field names ("Acrofields") contained special characters or accented characters, the iText library (and then subsequently the PRPC activity "GenerateEform") was able to process the input file and correctly produce the 'filled-in' output PDF 'EForm'.
SR-120556 · Issue 180535
Dirty prompts functioning with JAWS
Resolved in Pega Version 7.1.8
When a dirty work object is closed, you are warned with a dirty prompt. When this dirty prompt is sourced via the modal/section pyDirtyCheckConfirm, JAWS did not gain focus to read this prompt and a manual click on this was required to read any elements. This was an issue where JAWS wasn't reading the dialog because there was no role attribute attached. This has been corrected.