New Flow Parameters Provide More Control Over Save and Exit

New flow parameters have been introduced to give better control over the buttons for saving an appointment during the flow and for continuing or exiting a screen flow. MSR-1104 | Feb 2025 (QU 28-02-2025)

Who is this feature for?
All users benefit from this improvement.

Key benefits:

  • Prevent emails in a flow screen from accidentally not being sent
  • More control over saving an appointment mid-flow

New parameters for Mail and Generic Mail flow components

The following two new flow parameters are relevant for use with the Mail and Generic Mail flow components:

Close screen on send
The default value is false, which maintains the current behavior. The email is sent using the send button, which then becomes grayed out or disabled. You then use the next or finish button in the footer to continue or exit the flow.

Setting the value to true changes the behavior. Once the email is sent, the flow automatically moves to the next step or closes. With this parameter, you can also hide the next and finish buttons in the footer.

Prevent finish without sending email
The default value is false, which maintains the current behavior. The flow can be continued or closed without sending the email.

Setting the value to true changes the behavior. If the email has not been sent, a warning message appears when attempting to continue or close the flow.

New parameter for Appointment flow component
A new flow parameter has been added to the Appointment flow component. This parameter is only relevant if the existing parameter "Display save button on flow" is set to true; otherwise, it is ignored.

Don't close screen on save
The default value is false, which maintains the current behavior. After saving the appointment, the flow automatically moves to the next screen or ends if it contains only one screen.

Setting the value to true changes the behavior. After saving the appointment, the flow screen does not automatically close. With this setting, the next and finish buttons in the footer must be used to control further navigation.

Feature implementation time (FIT)

  • Very simple implementation: < 15 minutes