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-122820 · Issue 177433
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
SR-122820 · Issue 182133
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
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-123023 · Issue 185999
Fixed emailing error for Report Browser subscriptions
Resolved in Pega Version 7.1.8
Once someone is subscribed to a scheduled report created in Report Browser, an email should be sent based on task scheduling. This was not happening as expected, though the status in the scheduled tasks was showing as sucessful. This was caused by an error in the ActionSendMailReporting activity which set the FromUserName to EmailAccount.pyEmailAddress instead of EmailAccount.pySMTPUserName, and has been corrected.
SR-123095 · Issue 184829
Removed redundant save prompt for changed logging levels
Resolved in Pega Version 7.1.8
When a logging level in Designer Studio was changed, a prompt appeared to save the rules upon exiting the System operations page. This was redundant - the log level is saved immediately when it is changed in the modal dialogue "Logging Level Settings", and the extra prompt has been removed.
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.