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.
SR-122917 · Issue 182299
Resolved error in security change tracking
Resolved in Pega Version 7.1.8
If security change tracking was enabled using a declare trigger with a TrackSecurityChanges activity on the Operator class, adding a Data Transform ChangeTrackModel to track a number of properties on the operator record would create a PropertyIndex property and no further changes could be saved. This occurred in environments using the dynamic system setting "validateonsave" (set to true) which validates the property existence in the class hierarchy, but a validation error occurred on save because "pyPropertyIndex" is in the Embed-ModalParams class which was not accessible to Data-Admin-Operator-ID. To resolve this, the "pyPropertyIndex" has been moved to baseclass.
SR-123235 · Issue 183263
Additional localization for attachments functions
Resolved in Pega Version 7.1.8
Localization has been added in the attachments section for the "Attachment" link, "Attach URL", 'Add new party" in the work parties modal, and the "Save Draft" button.
SR-123242 · Issue 183215
Stage names now incuded in localization wizard
Resolved in Pega Version 7.1.8
Previously, Stage names were not picked up by the localization wizard unless each Case Type was saved in the application. An enhancement has been added to allow them to be localized more efficiently.
SR-123245 · Issue 185467
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.