SR-122440 · Issue 183753
Corrected text wrap for cases
Resolved in Pega Version 7.1.8
Text wrapping was not happening automatically in long history descriptions in a case. This was due to a missing function and has been corrected.
SR-122493 · Issue 190767
Support added for conditional page list properties
Resolved in Pega Version 7.1.8
After upgrading, validate rules on aggregate properties had unexpected behaviors. This rule formation was inadvertently allowed in some earlier versions despite guardrails, so support for these conditional page list properties has been added in order to enhance backwards compatibility.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.
SR-122559 · Issue 181629
Removed pagination from GetBinaryFiles RD to ensure all records are reported
Resolved in Pega Version 7.1.8
When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.
SR-122559 · Issue 179977
Removed pagination from GetBinaryFiles RD to ensure all records are reported
Resolved in Pega Version 7.1.8
When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.
SR-122637 · Issue 183016
MaxFileLength property added to avoid truncating attachment names
Resolved in Pega Version 7.1.8
While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.
SR-122757 · Issue 185151
Chinese filename issue with Microsoft Internet Explorer resolved
Resolved in Pega Version 7.1.8
When using the Chinese version of the Microsoft Internet Explorer browser and the out-of-the-box attachment gadget to attach files, dragging and dropping a file with Chinese characters in the file name caused the name to become corrupted. This issue was due to the encoding method, and has been resolved by removed the encoding for the filename.
SR-122761 · Issue 188488
Tuned logic for propagating shape flow actions
Resolved in Pega Version 7.1.8
When a work flow has moved from an assignment shape to an assignment service shape, the other actions menu was showing the flow action from the previous assignment. Work-.Connect activity invoked populateFlowActions function to populate the assignment local action. By the time this was invoked, the pxFlow() was not updated with the correct assignment details and the old assignments actions were being populated. This has been fixed by tuning the logic of invoking populateFlowActions.
SR-122809 · Issue 182677
Application Wizard updated to use long-form function name
Resolved in Pega Version 7.1.8
When using the Application Wizard in some environments, clicking 'Preview' or 'Create' on the Data Objects screen caused a refresh and no summary of the created rules was generated. This issue was traced to an error in the library/function rule resolution where the short-form reference to a function was finding more than one suitable rule resolution candidate if there was more than one version of a ruleset function with the same formal parameters and the function was called using the short form of the function name. In this particular scenario the PageListContains function was causing a problem as this function exists in both the PegaSurvey framework and the Pega-AppDefinition ruleset. There was a workaround of doing a private checkout of the CopyFrameworkClassGroup activity and changing the short function rule reference to the long function rule reference (specifying ruleset and library, but the Wizard has been updated to use long-form function name to prevent this issue.
SR-122839 · Issue 185954
Audit entries properly suppressed
Resolved in Pega Version 7.1.8
Audit entries were being added to the history even after suppressing the same in the DT "FilterHistory" of the respective interaction class. When the "RemoveAssignmentByTicket" function called the activity "AddWorkHistory", the parameter workPage was not being sent. Because the system skipped the call to the decision tree, it was returned as 'true' each time. To resolve this, the system now passes "WorkObjectPageName" to ensure proper evaluation.