SR-123292 · Issue 188135
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-123303 · Issue 185053
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123303 · Issue 176110
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123492 · Issue 184136
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.
SR-123492 · Issue 183606
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.
SR-123533 · Issue 187272
Corrected calculation of WO SLA Goal,Deadline based on calendar input
Resolved in Pega Version 7.1.8
The calculation of Goal,Deadline for WO SLA was not showing the expected results based on business days in the calendar. This was caused by not passing the appropriate parameter (CalendarName) to Work-.DefineSLATimesFromNewProperties so that BusinessCalendar.addTime function could evaluate the SLA based on the calendars, and has been fixed.
SR-123623 · Issue 178641
Added clipboard clearing for correspondence
Resolved in Pega Version 7.1.8
External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.
SR-123623 · Issue 184847
Added clipboard clearing for correspondence
Resolved in Pega Version 7.1.8
External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.
SR-123628 · Issue 184174
Control inserted for determining Elastic Search (ES) index building
Resolved in Pega Version 7.1.8
As Elastic Search (ES) indexing can take significant time and may cause a temporary performance problem, an enhancement has been added to control whether or not indexes are built during an upgrade. The option also exists to start the build at a later time if it is not performed during upgrade.
SR-123712 · Issue 184471
Resolved schema qualification for dedicated tables
Resolved in Pega Version 7.1.8
When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.