Author intends user to go down path 1, get documents, interact with the court, then reload saved answer file and reload interview and go down path 2 to get 2nd set of documents.
In old a2jviewer (pre Dec 2021), when a user reloaded saved answer file, they were taken to the 1st question of an interview. Author implemented before logic on that first page to test if user had completed path 1
(example BEFORE logic: IF [Step 1 complete TF] = true or [A2J incomplete TF] = false, GOTO "2nd path", END IF)
With new advanced nav viewer, reloading a saved answer file takes the user to the page in which they left off of the interview. In this scenario, that's the "Get Document" page from Path 1.
I tried adding before logic on the get document page to trigger a look at [Step 1 complete TF], but logic doesn't rerun again with a reloaded answer file (which is generally how it should work - logic doesn't re-evaluate on pages you've already visited).
Any thoughts on how we could accomplish the original goal of this interview with the new advanced nav feature?
Options: (please add to this list if anyone comes up with other options)
[ ] add a button on Get Document page that says "Move on to step 2" -- it'd be kind of confusing for 1st time through people and a bit ugly for everyone. Would also require author to explain when users should use this button. PROS - immediately implementable and free (no dev time for anyone but author)
[ ] implement a "turn off advanced nav" feature in about tab like "reduced interface" and "open advanced nav interface by default" so authors with these types of interviews and branching logic can force all users to reload at page 1. CONS- needs dev time to implement, benefits of advanced nav lost to these end users
Interview contains two forks - path 1 and path 2.
Author intends user to go down path 1, get documents, interact with the court, then reload saved answer file and reload interview and go down path 2 to get 2nd set of documents.
In old a2jviewer (pre Dec 2021), when a user reloaded saved answer file, they were taken to the 1st question of an interview. Author implemented before logic on that first page to test if user had completed path 1
(example BEFORE logic: IF [Step 1 complete TF] = true or [A2J incomplete TF] = false, GOTO "2nd path", END IF)
With new advanced nav viewer, reloading a saved answer file takes the user to the page in which they left off of the interview. In this scenario, that's the "Get Document" page from Path 1.
I tried adding before logic on the get document page to trigger a look at [Step 1 complete TF], but logic doesn't rerun again with a reloaded answer file (which is generally how it should work - logic doesn't re-evaluate on pages you've already visited).
Any thoughts on how we could accomplish the original goal of this interview with the new advanced nav feature?
Options: (please add to this list if anyone comes up with other options)
[ ] add a button on Get Document page that says "Move on to step 2" -- it'd be kind of confusing for 1st time through people and a bit ugly for everyone. Would also require author to explain when users should use this button. PROS - immediately implementable and free (no dev time for anyone but author)
[ ] implement a "turn off advanced nav" feature in about tab like "reduced interface" and "open advanced nav interface by default" so authors with these types of interviews and branching logic can force all users to reload at page 1. CONS- needs dev time to implement, benefits of advanced nav lost to these end users
GI at issue and answer file (zipped b/c Github doesn't allow .anx files): NYS Supreme Uncontested Divorce.zip answer - 2022-07-11T140705.676.zip