SR-130695 · Issue 200024
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-130695 · Issue 200339
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-131723 · Issue 199975
Resolved RD header alignment
Resolved in Pega Version 7.1.8
When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.
SR-131723 · Issue 200028
Resolved RD header alignment
Resolved in Pega Version 7.1.8
When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.
SR-128213 · Issue 196729
Summary View handling added for property name missing dot
Resolved in Pega Version 7.1.8
In Summary View, it was not possible to add an embedded property for the drill down if the property name was missing a leading dot. A null check has been added to eliminate the NPE and handle this issue.
SR-128213 · Issue 195827
Summary View handling added for property name missing dot
Resolved in Pega Version 7.1.8
In Summary View, it was not possible to add an embedded property for the drill down if the property name was missing a leading dot. A null check has been added to eliminate the NPE and handle this issue.
SR-128423 · Issue 193544
RD filter caption localized
Resolved in Pega Version 7.1.8
In report definition, expanding the filter link showed the caption of the filter icon was not localized. This has been corrected by creating a new control and applying it to pyFilterLabel in pzEditSingleFilter.
SR-128423 · Issue 194206
RD filter caption localized
Resolved in Pega Version 7.1.8
In report definition, expanding the filter link showed the caption of the filter icon was not localized. This has been corrected by creating a new control and applying it to pyFilterLabel in pzEditSingleFilter.
SR-129062 · Issue 194086
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.
SR-129062 · Issue 195029
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.