Control Screen Behavior Using Buttons
How a screen behaves in an interview depends on the type of button defined for the screen. When defining a screen you have four options for buttons:
Specify the button type on a screen
To specify the button type on a screen:
- In the screen list, select the screen.
- In the screen layout view, select the button.
- On the command bar, select the current button type.
- In the drop-down window, select the new button type.
The screen in the screen layout view is updated to show the new button.
Tip: You can change the text of the Next, Submit and Back buttons individually or globally. For more information, see Button text settings. You can also use HTML in button text. For more information, see Change the Appearance of Text Using HTML Tags. In addition to changing the button text, you can also change the styles used for these buttons, and the position of the buttons on the screen. For more information, see Configure the Back and Next Buttons.
Next button
The Next button submits the data into the session and then navigates to the next appropriate screen. The next appropriate screen will either be the next screen in the screen order if the data submitted successfully, or the same screen redisplayed with any errors or warnings that were raised when trying to submit the data.
Next buttons save checkpoints (where the checkpoint option is selected for that screen). If a checkpoint is created when the user clicks a Next button, the checkpoint will resume on the next screen.
The last screen in an interview cannot have a Next button. (The exception to this is a Next-type button on the last screen which acts as a redirect to another page. For more information, see Redirect the User to an External URL.)
Submit button
The Submit button does everything the Next button does, but, for interviews integrated with an external application, additionally calls out to the data adapter to submit the data into the application (assuming that the data was successfully submitted into the session). It is possible to have multiple Submit screens defined in an interview. For more information on this process, see Submit Data to a Connected Application.
Submit screens are shown with a save icon in the screens list.
Submit buttons delete checkpoints (where the delete after submit option is selected). If a checkpoint is created when the user clicks a Submit button, the checkpoint will resume on the next screen.
The last screen in an interview cannot have a Submit button.
The screen immediately after a screen with a Submit button does not have a Back button. This is to ensure the interview user does not perform multiple submits by attempting to revisit the Submit screen.
A Submit button can also be used to redirect the user to another page. For more information, see Redirect the User to an External URL.
You should not place a Submit button on an entity level screen.
The Submit button text can be changed. For more information, see Button text settings.
Back button
The Back button displays the previous screen shown in the interview.
The first screen in an interview cannot have a Back button.
You can specify that an interview should not include a Back button on any screen. For more information, see Add or remove the back button.
In August 2016 version interviews, a screen immediately after a screen with a Submit button cannot have a Back button.
In Latest Version Interviews, you can add or remove the Back button on a screen-by-screen basis.
No next button
Selecting No button in the button type drop-down means no Next button is shown on the screen.
Screens with a no next-type button are shown in the screens list with a red stop icon.
The last screen in an interview must have no button (unless it acts as a redirect to another page).
It is possible to have multiple ending screens defined in an interview, where which one is displayed depends on the path the user has taken through the interview or the result they have received (for example, eligible or not eligible).
Each of these ending screens should have no Next button.
