Need to renter a field that was skipped

What would you like to see in CSPro?
Post Reply
AriSilva
Posts: 615
Joined: July 22nd, 2016, 3:55 pm

Need to renter a field that was skipped

Post by AriSilva »

Hi folks,
I´m using a type of menu application where the fields do not have a specific order of answering.
Or the user decided to reenter a field that was already skipped.
For example, if some basic fields are not changed, we do not need to enter them.
But there times when the user, in one of the alternatives of the menu, he needs to change a field that it is located before the menu.
But the system does not allow to reenter a field that was already skipped.
In this type of environment, where the case it is not a real questionnaire, but a sort of control menu, how can we return, or go to, or change the flow of the data to “go back” to other fields and not to get an error message?
Or, as a new feature, a new command, like the reenter, but that would allow returning to “back” fields.
Best
Best
Ari
aaronw
Posts: 570
Joined: June 9th, 2016, 9:38 am
Location: Washington, DC

Re: Need to renter a field that was skipped

Post by aaronw »

The navigation that you are describing is not easy to do. We are aware and may consider this in a future release.

Here's one approach. Enforce the limitation that all fields will eventually be answered. Near the beginning of you application you'll have a field you never skip, so it can always be reentered. Let's call it NAV. You always reenter NAV before skipping to the section you're navigating to. During this you never allow the application to complete until a validation step is taken. Your case in maintained in a partial save state. The validation step will not succeed until all fields are complete. It will reenter NAV and then advance to end. At this point the application can complete and save normally.
AriSilva
Posts: 615
Joined: July 22nd, 2016, 3:55 pm

Re: Need to renter a field that was skipped

Post by AriSilva »

Great,
Thanks,
I´ll try that strategy.
Good thinking.
Best
Ari

By the way, all the applications we are designing now are based in that menu-questionnaire approach you´ve used in the synchronization in logic example, having two programs (or more), one for the managerial tasks and the other(s) for the real interview(s)
Best
Ari
Post Reply