SR-A325 · Issue 203740
Added Params to activity display before check-in
Resolved in Pega Version 7.1.9
When calling an activity from another activity, parameters were not being properly retrieved in the calling activity call step unless there was a check-in that called activity. This happened when a private ruleset was not in the user's context and therefore the checked out rule was not picked up. To correct this, the open activity method has been modified to use db.open() .
SR-A4712 · Issue 211249
Repaired column header labels in Decision Table
Resolved in Pega Version 7.1.9
Clicking on a column header and opening the property changer, then closing it using the X in the top-right corner of the popup caused the label to change to the label of the rightmost column. This was traced to incorrect behavior by the modal dialog where closing the window did not return the correct value from the previous launch. This has been corrected.
SR-A4712 · Issue 211249
Repaired column header labels in Decision Table
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.9
Clicking on a column header and opening the property changer, then closing it using the X in the top-right corner of the popup caused the label to change to the label of the rightmost column. This was traced to incorrect behavior by the modal dialog where closing the window did not return the correct value from the previous launch. This has been corrected.
SR-A3716 · Issue 209598
Added conditional check for bulk check-in memo
Resolved in Pega Version 7.1.9
When performing a bulk rule check-in, the comment was being prefixed with a ?:?. This caused issues when using pyMemo as part of a code review with a report looking at check-in comments for specific changes associated with a project. This name difference was due to the different activities being called and how the pyTaskID parameters were being attached. There was a workaround of saving the Rule-.PreCheckIn activity into the application ruleset, then removing the existing java step and adding a property set to for setting the Param.InMemo value, but this situation has been resolved by conditionally appending task id to history memo.
SR-A540 · Issue 205835
Guardrail justifications logging corrected
Resolved in Pega Version 7.1.9
The 'Reference properties' Guardrail warning for Rule-Obj-Property was not being saved in the pr_index_warnings table as expected. The issue was caused by the warning not being created while saving the rule, and has been resolved by adding a step to set reference warning in checkForWarnings activity.
SR-A1199 · Issue 206250
Updated Email Listener mProtocol
Resolved in Pega Version 7.1.9
It was noticed that testing mail connectivity was working, but the Email listener was failing to start. This was happened when the "getStore" function on a Mail Session in the connection test passed a protocol argument that included [pop3, pop3s, imap, imaps]. EmailListener did not update the "mProtocol" variable to have the "s" for SSL, so it was only ever one of [pop3, imap]. To resolve this, the protocol name in Email Listener has been abstracted so that the 's' appears when telling java mail the protocol name.
SR-A1482 · Issue 204980
Enhancement added to support custom headers through REST
Resolved in Pega Version 7.1.9
The getObject(?pxHTTPServletRequest?) function was returning null when the authentication activity was run through the REST service. The retrieval of custom headers in the custom authentication activity was not previously supported as the object which stores the request map was null, but an enhancement has been added to make the servlet object available to HTTP/REST Service in the custom auth activity.
SR-A1484 · Issue 205662
Enhancements added to assist in migrating truststore information to new clusters
Resolved in Pega Version 7.1.9
An installation working on development both in the system and with set of trust for Connectors defined inside Pega that were specific to the development server and SOAP endpoint desired to have all of the trust configurations migrated along with the code base when setting up additional environments. Problems occurred during certificate validation that prevented the desired use, but no useful error information was generated. In order to support this function, enhancements have been added to produce an informative exception error in the checkServerTrusted method of CompositeX509TrustManagerwhen a certificate is not trusted, and to ensure that the signer certificates and then each of its intermediate certificates in the certification path are imported to Pega?s IBM WebSphere JVM?s truststore and all WebSphere JVMs participating in SSL communication on the PRPC cluster.
SR-A1538 · Issue 207014
prvisiointerface.cab unblocked
Resolved in Pega Version 7.1.9
Effective with earlier ML versions of Pega7, several OCX functions were intentionally deprecated and replaced with Silverlight functions: Prbatchscanning prDeveloper prpackagecominterface prvisiointerface. However, it was found that there are two Word features around the embed merge function requiring prvisiointerface.cab that will produce some visual problems on the screen referring to the missing cab break if the files are ported from an earlier version of PRPC and prvisiointerface.cab is unavailable. Therefore, prvisiointerface.cab has been unblocked and restored for use.
SR-A1574 · Issue 205921
Reverted WSDL naming convention to previous style
Resolved in Pega Version 7.1.9
In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.