Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

SR-114819 · Issue 175544

Localization added for currency values using commas vs decimal points

Resolved in Pega Version 7.1.8

Excel within PRPC was not properly localizing for the use of decimal and comma as thousand and decimal separators for decimal/double currency property values, a use that is common in non-English installations. The records editor has been changed to support localization for properties of type double and decimal.

SR-115526 · Issue 178638

Epilog activity correctly executing for asynchronous queues

Resolved in Pega Version 7.1.8

When configuring a File Listener and Service-File for Asynchronous execution queue, the Epilog activity was not being executed. There was a workaround of switching to synchronous execution, but this issue was traced to a logic flaw that created a race condition between the processing of the file parsing (which occurs in one thread) and the row processing (which occurs in a separate thread) and has been resolved.

SR-118044 · Issue 178369

Corrections and enhancements made to Outlook meeting requests

Resolved in Pega Version 7.1.8

Using the function 'SendEmailMessage' to send an Outlook meeting request was only generating an email instead of the full meeting invitation. This was traced to unimplemented code and has been corrected. In addition, enhancements have been added to the FormatMeetingRequest RUD to set RSVP options for TO & CC recipients, and the PRODID flag value has been parameterized.

SR-118160 · Issue 175398

Email Listener performance improved

Resolved in Pega Version 7.1.8

A mismatch in time values was causing Email Listener to be extremely slow in some complex installations. This has been corrected to improve performance.

SR-118269 · Issue 174402

Eform wizard upload error resolved

Resolved in Pega Version 7.1.8

When attempting to upload a file using the EForm wizard, an error was generated stating "The Flow Action post-processing activity PopulateFileRule failed" and the file did not upload. The root cause of this ruleset problem was that the necessary class was not present in the JAR, and has been resolved.

SR-118486 · Issue 175139

XSS filtering improved for Host and Gateway

Resolved in Pega Version 7.1.8

For security, XSS filtering has been improved on hostconfig.jsp and .

SR-118615 · Issue 172704

Addressed XML handling for "Expand Java Pages"

Resolved in Pega Version 7.1.8

After upgrading, an IOException occurred while updating a work object if "Expand Java Pages" was unchecked in General options -> Tracer Settings. When the checkbox is enabled, the Javaobject wrapper uses its custom read/write methods to serialize the page. When unchecked, default serialization invoked the which contained some properties which are not Serializable. In order to ensure proper XML handling, changes were made to so the code flow is independent of the expand java pages option in tracer and always takes the custom serialization path.

SR-118735 · Issue 175180

Addressed ruleset integrations problems using Google Chrome

Resolved in Pega Version 7.1.8

When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.

SR-119103 · Issue 178373

Missing hyphen auto-added to base class by import wizard

Resolved in Pega Version 7.1.8

When running the Connector & Metadata wizard to import the XSD file, entering the base class name without a dash created classes and properties all concatenated with the class name. However entering a dash at the end of the base class name created properties separated with the dash from the class names. This was an error in the wizard - it is no longer mandatory to end the abstract class with a dash, and the code has been updated to correctly append the hyphen at the end of baseclass if one doesn't exist.

SR-119214 · Issue 175331

Stream XML generation and runtime handling enhanced for optional nodes in schema

Resolved in Pega Version 7.1.8

When a stream rule was executed using connect-SOAP and blank data was passed from the UI, a tag corresponding to the XML element marked as optional was being generated. This resulted in those optional properties being unexpectedly created in source systems. To change this, the generation of the Stream XML rule has been enhanced such that at runtime it ignores optional nodes/attributes mapped to properties which do not exist or which have an empty value. NOTE: this new behavior in Stream XML rule generation is effective only with the below DSS configuration (to avoid backward compatibility issues ): Owning Ruleset : Pega-IntegrationEngine Purpose : StreamXML/DetectEmptyProperties Value : true

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us