SR-121758 · Issue 178990
Logic added to resolve conflicting Currency display values
Resolved in Pega Version 7.1.8
The read-only display format of the out-of-the-box Control 'Currency' was not working as expected due to a precedence conflict between the 'Property Qualifier' configured at the property level and the out-of-the-box 'Currency' control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-121758 · Issue 178251
Logic added to resolve conflicting Currency display values
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.8
The read-only display format of the Out-of-the-Box Control "Currency" was not working as expected due to a precedence conflict between the "Property Qualifier" configured at the property level and the Out-of-the-Box "Currency" control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-122292 · Issue 182878
Operators and Access Groups are now automatically force re-indexed during import
Resolved in Pega Version 7.1.8
If a number of new OperatorIDs were created and added to two workgroups and then the changes were exported, the new OperatorIDs were present when the file was imported to other environments but a query run against the table PR_INDEX_OPERATOR_WORKGROUP did not incorporate the new IDs. While there was a workaround of manually forcing a re-index during import to fully incorporate the new IDs, the Operators and Access Groups are now automatically force re-indexed during import to ensure data is up to date.
SR-124198 · Issue 184897
Clarified messages for attachment deletion failure
Resolved in Pega Version 7.1.8
When trying to delete an attachment on the work item without proper authorization, the tracer shows a message being added on TempAttachmentPage in Work- DeleteAttachment activity reading "You are not authorized to delete instance DATA-WORKATTACH-FILE ATPEGA-TASK ". However, this message was not being propagated to the screen and the screen was refreshing as if it worked despite the failure. To clarify the actual results, the DeleteAttachment Activity has been modified to present any messages and to avoid page removal of the TempAttachmentPage and TempLinkPage if there is a message.
SR-132265 · Issue 200632
Improved hotfix detection
Resolved in Pega Version 7.1.8
Migrating from ML6 to ML7 was failing with an error reporting the system contained hotfixes that were generated after the release of ML7. This was due to the ML Readiness step incorrectly identifying pre-7.1 rules as having been updated after the upgrade to 7.1.6. This happened when the revalidate and save was run after the release of ML7, which updated the pxUpdateDateTime for the rules in question and led to them being caught by the validation. This was meant to catch hotfixes, and the handling has been improved to avoid this error.
INC-126662 · Issue 561315
Thread context updated to supply steppage
Resolved in Pega Version 8.4.2
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
SR-D94258 · Issue 560796
Thread context updated to supply steppage
Resolved in Pega Version 8.4.2
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
SR-119899 · Issue 177532
Breadcrumb functionality disabled for Process Modeler pending further development
Resolved in Pega Version 7.1.8
Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.
SR-119899 · Issue 182818
Breadcrumb functionality disabled for Process Modeler pending further development
Resolved in Pega Version 7.1.8
Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.
SR-123809 · Issue 185686
Report schedule icon display fixed for SQL
Resolved in Pega Version 7.1.8
When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.