SR-126157 · Issue 193349
Email Listener message handling updated for DSN messages
Resolved in Pega Version 7.1.8
Signature protected emails were causing an error even when the 'include DSN messages' checkbox was active. According to the Oracle tech note at http://www.oracle.com/technetwork/java/javamail/faq/index.html#imapserverbug this can be worked around by creating a new copy of message for this call, and that code has been added to this function.
SR-131055 · Issue 201905
JNDIurl information picked up for Transport rule test scenarios
Resolved in Pega Version 7.1.9
JNDIurl information was not being picked up from the Transport rule during the testconection flow even though the implementation logic was present at runtime. The proper function has now been added to the test scenario. In addition, handling was added for the retrieval of the destination name from endpoint URL when the endpoint URL doesn't contain '?'.
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-A15491 · Issue 231066
Access control added for duplicate work baskets
Resolved in Pega Version 7.2.1
out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.
SR-A15491 · Issue 231387
Access control added for duplicate work baskets
Resolved in Pega Version 7.2.1
out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.
SR-A18722 · Issue 240874
Resolved alert for PYLOADMYCASESTREE
Resolved in Pega Version 7.2.1
While trying to invoke the out-of-the-box activity pyLoadMyCasesTree, a Pega0050 alert was triggered and logged. The function is failing to copy the items to Code-Pega-List from the pxResults due to the class of treePage which contains all the cases that needs to be displayed in the Gadgets. The tree page has been changed to @baseclass to resolve this issue.
SR-A22722 · Issue 246998
pxDereferenceEndpoint Activity can be overridden by the customer
Resolved in Pega Version 7.2.1
The generic pxDereferenceEndpoint Activity that applies to the Rule-Connect-REST class was not the functionality desired by the customer, so they wanted to be able to change it, but it was set to ?Final? and couldn?t be changed. The availability of the pxDereferenceEndpoint Activity has now been set to ?Available? so that customers may override it in any RuleSet. (No logic changes have been made to this activity.)
SR-A38578 · Issue 253239
Population handling added for null value flowType property
Resolved in Pega Version 7.2.2
While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.
SR-A90472 · Issue 258243
Population handling added for null value flowType property
Resolved in Pega Version 7.2.2
While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.
SR-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.