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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A3610 · Issue 217555

Corrected ParseXML clipboard mapping

Resolved in Pega Version 7.2

The ParseXML rule was not correctly mapping data to the clipboard after upgrade. This was a regression: the design limitations of the new parse rule caused an issue with calling child parse rules on the fly based on the context page, and has been fixed by parameterizing the override class of the new parse rule.

SR-A3992 · Issue 212220

Fixed appendment handling for ComplexType elements

Resolved in Pega Version 7.2

If an element was of ComplexType, the attributes were appended before the sequence of elements are appended; this has been corrected.

SR-A5222 · Issue 215076

Fixed Vcalendar meeting invites propagation

Resolved in Pega Version 7.2

Because the VCalendar file was considered a text file while sending calendar invite request, it was not being properly handled for meeting invites. Code has now been added to treat meeting requests as attachments

SR-A5659 · Issue 214180

HTTP Connector Simulation properly runs for both Global and User sessions

Resolved in Pega Version 7.2

When attempting to use a simulation activity for a HTTP Connector, it worked when set to Global Session but did not appear to run when set to User Session. At run time, the list of simulation activities was picked from the pyISSimulation clipboard page. Because that page was available in the "STANDARD" thread only, the code responsible for loading the simulation activities was not able to find the correct page. This has been fixed to allow the table to properly execute the Connector simulation for both Global and User Session.

SR-A5103 · Issue 214155

Improved Rule-Connect-SOAP connector performance

Resolved in Pega Version 7.2

Performance issues seen when running Connect-SOAP with NTLM authentication and tracing it using Performance Profiler have been resolved by modifying the parsing to improve use of the cached objects.

SR-A5050 · Issue 213004

Max characters limit removed for Custom properties on JNDI Server rule

Resolved in Pega Version 7.2

The 30-character limit on the JNDI Property Name and Value pairs on the Custom Properties tab of the JNDI Server rule has been removed to allow for site customization.

SR-A6108 · Issue 217715

Node validation check added to SOAP services

Resolved in Pega Version 7.2

Code has been added to SOAP Services to check whether the node is usable or not before processing the request.

SR-A5671 · Issue 215223

Node validation check added to SOAP services

Resolved in Pega Version 7.2

Code has been added to SOAP Services to check whether the node is usable or not before processing the request.

SR-A6364 · Issue 214336

Quotes stripped from Parse XML namespace to resolve compiler error

Resolved in Pega Version 7.2

When the node namespace value in a Parse XML rule was entered within quote marks, a compilation error occurred upon save. To resolve this, the system will strip any quotes from the namespace value.

SR-A6223 · Issue 214939

Resolved WSDL SOAP exception when using target namespace

Resolved in Pega Version 7.2

When adding a well-defined XML ParseRule as a Request Header, saving and checking in the rule caused the Deployment results link to generate the error "Caught exception while creating WSDL for service package: : com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException Header message is included with method namespace instead of targetnamespace" This was an error in the code handling a target namespace for Request Headers (configured on the Service Soap -> Requests tab), and has been fixed.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us