Question
NAB
AU
Last activity: 12 Jan 2023 13:09 EST
Declare Expression not getting fired from Grid Layout
Is there a change in the way declare expressions get triggered from Pega 8.4.2 to Pega 8.7.2?
We have this scenario: Configured a declare expression: FullName = FirstName + LastName in context of Work- class.
Displaying work/case details in grid: Grid -> Data Page -> Report Definition.
In report definition FirstName and LastName columns are mentioned and not the FullName.
In grid layout in section, configured FullName as one of the columns.
In Pega 8.4.2, FullName is getting displayed. When I trace, I see that FullName declare expression is being triggered as part of report definition execution.
Where as in Pega 8.7.2, FullName is not getting displayed and I do not see declare expression getting triggered.
Previous post Declarative Expressions | Support Center (pega.com) refers to SR-D44692. Not sure if this SR is about the same issue. Please help.
Regards
Murali
Accepted Solution
Updated: 12 Jan 2023 13:09 EST
Pegasystems Inc.
GB
@Murali Kakarla the support ticket you quote was logged 3 years ago and was for product version 8.1.4. The issue there was simply incorrect use of the Declare Expression for that scenario.
User had a declarative expression on a property and another declarative expression on another property that is dependent upon the first one. They were both set to whenever inputs change regardless of the page.
User called a report definition to populate a list. The first expression fired and set its properly to a value but the second expression did not fire.
Issue-1 : Declare Expression-1 not triggered with "Whenever Input changes"
Explanation: The reported behavior is working as expected as per the Product design. You are just fetching the value from the Report Definition to display in the Table/Grid. However, the value of the corresponding property is not changed in the provided use case.
Solution: Suggested to use Declare Expression with “whenever used”. This resolves the issue-1.
Issue-2 : Declare Expression-2 not triggered with Hover Action.
Explanation: On hover-over action, declare expression is not getting fired. Moreover, on adding the same property seperately in a section that is used in the hover action, the Declare Expression is getting fired. It is excepted that on hover action declare expression will not be triggered.
@Murali Kakarla the support ticket you quote was logged 3 years ago and was for product version 8.1.4. The issue there was simply incorrect use of the Declare Expression for that scenario.
User had a declarative expression on a property and another declarative expression on another property that is dependent upon the first one. They were both set to whenever inputs change regardless of the page.
User called a report definition to populate a list. The first expression fired and set its properly to a value but the second expression did not fire.
Issue-1 : Declare Expression-1 not triggered with "Whenever Input changes"
Explanation: The reported behavior is working as expected as per the Product design. You are just fetching the value from the Report Definition to display in the Table/Grid. However, the value of the corresponding property is not changed in the provided use case.
Solution: Suggested to use Declare Expression with “whenever used”. This resolves the issue-1.
Issue-2 : Declare Expression-2 not triggered with Hover Action.
Explanation: On hover-over action, declare expression is not getting fired. Moreover, on adding the same property seperately in a section that is used in the hover action, the Declare Expression is getting fired. It is excepted that on hover action declare expression will not be triggered.
Solution: The probable workaround that we can propose is that add a hidden content for the text property that you wish to display in the hover action of the property.
If you believe that the same configuration works differently between 8.4.2 and 8.7.2 then could I suggest that you log a new support incident? Please provide the ticket reference here.
Updated: 30 Sep 2022 7:37 EDT
TSPI
US
Try the Concatenate Function in Report definition. Explained the approach in Attached Document.
Thanks,
NAB
AU
@RohiniKumarU Thank you for responding.
If I include FullName column or include concatenation as suggested by you it works. Or when I private edit FullName declare expression and update the change tracking to 'Whenever Used', it works without having to include FullName column in report definition.
This was working fine in Pega 8.4.2 without any changes but after upgrading to Pega 8.7.2, it stopped working. Any change in behaviour of Declare Expressions (when referenced in RDs/Data Pages) from Pega 8.7?
Regards
Murali
NAB
AU
@PoojaGadige Could you please help with checking SR-D44692, if this SR is related to this and any solution provided? Thank you.
Accepted Solution
Updated: 12 Jan 2023 13:09 EST
Pegasystems Inc.
GB
@Murali Kakarla the support ticket you quote was logged 3 years ago and was for product version 8.1.4. The issue there was simply incorrect use of the Declare Expression for that scenario.
User had a declarative expression on a property and another declarative expression on another property that is dependent upon the first one. They were both set to whenever inputs change regardless of the page.
User called a report definition to populate a list. The first expression fired and set its properly to a value but the second expression did not fire.
Issue-1 : Declare Expression-1 not triggered with "Whenever Input changes"
Explanation: The reported behavior is working as expected as per the Product design. You are just fetching the value from the Report Definition to display in the Table/Grid. However, the value of the corresponding property is not changed in the provided use case.
Solution: Suggested to use Declare Expression with “whenever used”. This resolves the issue-1.
Issue-2 : Declare Expression-2 not triggered with Hover Action.
Explanation: On hover-over action, declare expression is not getting fired. Moreover, on adding the same property seperately in a section that is used in the hover action, the Declare Expression is getting fired. It is excepted that on hover action declare expression will not be triggered.
@Murali Kakarla the support ticket you quote was logged 3 years ago and was for product version 8.1.4. The issue there was simply incorrect use of the Declare Expression for that scenario.
User had a declarative expression on a property and another declarative expression on another property that is dependent upon the first one. They were both set to whenever inputs change regardless of the page.
User called a report definition to populate a list. The first expression fired and set its properly to a value but the second expression did not fire.
Issue-1 : Declare Expression-1 not triggered with "Whenever Input changes"
Explanation: The reported behavior is working as expected as per the Product design. You are just fetching the value from the Report Definition to display in the Table/Grid. However, the value of the corresponding property is not changed in the provided use case.
Solution: Suggested to use Declare Expression with “whenever used”. This resolves the issue-1.
Issue-2 : Declare Expression-2 not triggered with Hover Action.
Explanation: On hover-over action, declare expression is not getting fired. Moreover, on adding the same property seperately in a section that is used in the hover action, the Declare Expression is getting fired. It is excepted that on hover action declare expression will not be triggered.
Solution: The probable workaround that we can propose is that add a hidden content for the text property that you wish to display in the hover action of the property.
If you believe that the same configuration works differently between 8.4.2 and 8.7.2 then could I suggest that you log a new support incident? Please provide the ticket reference here.