Question
Rabobank
NL
Last activity: 30 Jan 2024 12:47 EST
In a questionnaire, in Constellation, going back a page might end up on the same page
I have a questionnaire setup where a page's visibility is dependent on a previous answer. If that page is not shown due to this condition, we'll end up on the next page, which is correct. That next page has a Previous button (navigateToStep previous). Hitting that, most probably navigates back to the 'invisible' page, the condition is evaluated again, and we end up on the same page with that Previous button. We see this in 'Pega native' as well as in our integration with ConstellationJs.
***Edited by Moderator Marije to add Support Case Details; ***
Accepted Solution
Updated: 30 Jan 2024 12:47 EST
Pegasystems Inc.
GB
Hoi @BartRoozendaal. I see that INC-B2756 was closed with your agreement as you are no longer using the visibility of pages anymore for your flow - without the provision of reproduction steps our support team are not able to work on this issue.
I understand that you explained that the basic idea (initially) was to use a the visibility of a page dependent on a field from the previous screen. You didn’t use the Branch in the questionnaire at that time, but only used the visibility of a page to show/hide a page in the questionnaire.
Your solution was to change the design of the Questionnaire in order to use the Branching in questionnaire which made the UI work correctly.
As the Branching in Questionnaires seems to solve your needs you agreed to close the ticket.
If you do find a way to put together the reproducible step, feel free to log a ticket with the GCS team at that point so that our SME's can look at it when it can be replicated.
Pegasystems Inc.
GB
Hoi @BartRoozendaal. I'm not sure what your expectation is with this post - are you requesting a product enhancement?
If you want to report this as a product defect could I ask that you raise this via our MSP as a support incident and let us know the INC id here?
Rabobank
NL
@MarijeSchillern First of all I would like to understand if this is expected behavior of the product ;-) It seems odd and confusing to me
Updated: 12 Jan 2024 4:42 EST
Pegasystems Inc.
GB
@BartRoozendaal It does indeed sound inconsistent. @Sam Alexander do you have any input here?
I think it might be an idea for you to log a support incident so that our support team can see the exact configuration you are using, log file entries etc, and they will be able to provide you with the information based on that.
Please let us know the INC here so that I can help track it.
Updated: 22 Jan 2024 9:12 EST
Pegasystems Inc.
US
Rabobank
NL
@Sam Alexander This is the INC: INC-B2756
Accepted Solution
Updated: 30 Jan 2024 12:47 EST
Pegasystems Inc.
GB
Hoi @BartRoozendaal. I see that INC-B2756 was closed with your agreement as you are no longer using the visibility of pages anymore for your flow - without the provision of reproduction steps our support team are not able to work on this issue.
I understand that you explained that the basic idea (initially) was to use a the visibility of a page dependent on a field from the previous screen. You didn’t use the Branch in the questionnaire at that time, but only used the visibility of a page to show/hide a page in the questionnaire.
Your solution was to change the design of the Questionnaire in order to use the Branching in questionnaire which made the UI work correctly.
As the Branching in Questionnaires seems to solve your needs you agreed to close the ticket.
If you do find a way to put together the reproducible step, feel free to log a ticket with the GCS team at that point so that our SME's can look at it when it can be replicated.