SR-116950 · Issue 167458
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.
SR-116950 · Issue 168328
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.
SR-117164 · Issue 169821
Tightened vertical privileges
Resolved in Pega Version 7.1.7
If a User with lower rights accessed the cookie of a Manager, it was possible to update the Operator Details. A privilege check has been added when saving the operator record to resolve this issue.
SR-117265 · Issue 169903
Clarified "time" display for Calendar
Resolved in Pega Version 7.1.7
While using "pxCalendar" section to display task time, '?' was displayed near the current time in Daily and Weekly view. To avoid confusion, the '?' symbol has been replaced with the text 'Time' in a field value, which can be overridden accordingly.
SR-117265 · Issue 170246
Clarified "time" display for Calendar
Resolved in Pega Version 7.1.7
While using "pxCalendar" section to display task time, '?' was displayed near the current time in Daily and Weekly view. To avoid confusion, the '?' symbol has been replaced with the text 'Time' in a field value, which can be overridden accordingly.
SR-117513 · Issue 169033
History Audit information corrected for validation failures
Resolved in Pega Version 7.1.7
Following a validation failure in a flow action where validation is done in the post-processing activity, one line of history was being written for each validation failure in addition to one for the successful Submit. This was caused by the activity writing the history for a local flow action prior to calling the RunFlowActionActivity in which the validation occurs. This has been corrected to avoid history entry for error cases.
SR-117583 · Issue 170260
Draft Mode now includes referenced rules for shape sub-processes
Resolved in Pega Version 7.1.7
If a a flow was created in Draft Mode and shapes were added, adding subprocess shapes and implementing one of the subprocesses created a list of Referenced Rules that did not include the sub-flow rules. This was caused by dangling connectors, and has been corrected by a call that will generate the Java for the flow even when this condition is present.
SR-117591 · Issue 171917
Improved Bulk Action checkbox handling
Resolved in Pega Version 7.1.7
In Case Manager Portal, when multiple work items (>3) were selected and transferred with Bulk Action, some were deselected and are not processed. This was traced to the select of checkbox calling an activity, followed by parent section refresh with refreshed all checkboxes. If checkboxes were selected while the refresh was in progress, the value for the next selection was not posted even though it appeared to be checked. This has been corrected to ensure all selected checkboxes are posted properly.
SR-117606 · Issue 173816
Fixed portals enhanced for IE10 and IE11
Resolved in Pega Version 7.1.7
An enhancement has been added to the system to ensure portals will render accurately in IE10 and IE11.
SR-117674 · Issue 170571
Smart Shapes use properly limited to work class
Resolved in Pega Version 7.1.7
An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.