SR-D71475 · Issue 538720
Check added to apply values of newAssignPage.pxFormName
Resolved in Pega Version 8.3.2
After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.
SR-D72672 · Issue 536386
Security updated for CreateOperator
Resolved in Pega Version 8.3.2
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D75469 · Issue 538119
Resolved null-pointer exception in Expression Builder launch from activity rule
Resolved in Pega Version 8.3.2
A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.
SR-D75835 · Issue 539301
Added handling for Google Chrome drag and drop of Outlook email
Resolved in Pega Version 8.3.2
Attempting to drag and drop an email from Outlook to a case opened in Google Chrome resulted in the email being moved to the Outlook deleted folder. This was traced to Google Chrome defaulting to defining the "dropEffect" attribute as "none" when the expectation is it should be "copy". To resolve this, the recommended handling from Microsoft has been added as an event to make a copy (and not a move) an email from Outlook when dragged and dropped with Google Chrome.
INC-200802 · Issue 699967
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.6.4
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.
INC-177312 · Issue 692111
Added handling for FieldValue issue during Excel export
Resolved in Pega Version 8.6.4
After upgrade from Pega 7 to Pega 8, the export to Excel function for business-rules kept and maintained via Decision-Tables created a file that Excel could not open. This was traced to a function call in the Results tab and the Return Actions in the decision table which caused an issue with the generated Excel to be used for editing. To resolve this, any allowed values will have quotation marks removed before the vales are passed to the export.
INC-194330 · Issue 708710
Added special character handling for DecisionTable column-label
Resolved in Pega Version 8.6.4
The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.
INC-195790 · Issue 687810
Updated recording test scenario for attachments
Resolved in Pega Version 8.6.4
Recording scenario tests for a case type was not working as expected when attaching a document to a case as part of case flow. This has been resolved as part of the updates made for Pega Test Automation Kit (PTAK) v1.6.
INC-195793 · Issue 697921
Enhanced ruleset validation for portal creation
Resolved in Pega Version 8.6.4
Attempting to create a new portal (web channel) from the app studio using the Creation Wizard with "Branch development preferences" enabled resulted in the error message "No valid rulesets in application preferences". Investigation showed this occurred due to CPM-Portal being specified in the application as the UI class: when attempting to create the portal, the system was evaluating the class against ruleset candidates. The class was not visible to the rulesets in the stack and thus the portal could not be created. This has been resolved by adding validation on UI pages, Int and Data classes in the application to ensure that they exist in user rulesets, and by adding an allowance for classes to exist only in branched rulesets and not the base ruleset during check if the ruleset is present in application stack.
INC-200416 · Issue 699863
Updated AttachmentPreview control for Account Manager Access Group
Resolved in Pega Version 8.6.4
When using the Account Manager Access group as the default and only access group on a profile, attempting to render a PDF on the click of a link did not work as expected. The render-on-click worked as expected when logged in as the Author and the application was switched to Account Manager. This has been resolved by registering the activity pzAppStorageOkToAttachFile in the pzAttachmentPreview control.