Requested enhancement

pbrad

Hi,
I'm currently working on a large turnkey insurance company application and am making extensive use of wizard based navigation on forms worked on by clients.

I am wanting to use conditional visibility of form sections using the new separator row conditional visibility functionality based on the choices made on the form. In order for the separator row visibility to trigger based on a form selection I need to save the form when the relevant form selection is made.

The problem I am having though is that whenever the record is saved the form reverts to the first section of the form and the user has to click the next button a bunch of times to get back to where they were.

Is there any way that the form can remember the section that it is on when the record is saved automatically and remain on that section?

cheers,
Pete

aware_support

Aware IM should stay on the same section when the form is saved. Have you tried this in the latest build?

pbrad

Hi,
Thanks for the quick response as always. I was actually a couple of versions behind so I have tested it in the latest build but unfortunately with the same results.

I will email you a test bsv to demonstrate the issue.

Thanks,
Pete

nlarson

I don't use hided separators, but I have noticed this too. The form stays on the same tab, but the separator sections all revert to their default behavior

pbrad

Actually the problem is bigger than that. If you use auto save function on change of attribute on a wizard type form. When you change the attribute, you are automatically returned to the first section of the form. It doesn't have anything to do with whether you use separator rows or not.

Pete

nlarson

Ah, much worse! I don't use auto-save so did not realize.

tford

If you use auto save function on change of attribute on a wizard type form. When you change the attribute, you are automatically returned to the first section of the form. It doesn't have anything to do with whether you use separator rows or not.

Just building an online questionnaire and came across the same issue.

aware_support

Setting the flag to save the form on attribute change is not a proper solution to get the separator re-displayed. The proper solution would be for Aware IM to recalculate the condition dynamically and then redisplay the separator if anything changed (just like it is done now with rules executed dynamically on the client).

Not to mention that saving the form will CREATE an object if it's a new one. Dynamic recalculation won't.

So, we'll see if we can get Aware IM to be more intelligent here. In the meantime see if you can get around the problem by adding some dummy dynamic rule executed on the client and removing 'save on change' flag

pbrad

Hi,
Thanks for the response and the entirely usable workaround. Unfortunately though, the workaround doesn't seem to work.

The Separator Row visibility condition seems to be based on the database value of the controlling attribute, not the form value and it doesn't pick up the change unless the form is changed, thus taking you back to the first form section.

I will email you a simple bsv that demonstrates this.
Thanks,
Pete

pbrad

Any news on this yet?
Cheers,
Pete