Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Buttons are important helpers in forms, because in most cases the user decides at the push of a button how the process will continue. Without a button, the user can only close the form window, data is not saved and the next process steps cannot be triggered. As a rule, a form therefore always contains at least one button.

Modelers can use the standard buttons, or create and configure own buttons.

The Standard Buttons

Since buttons are an important part of every form, a new Responsive Form EPC as well as a new Responsive Form (subform) already contains three default buttons:

  • Next 
  • Save
  • Go to Overview

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNamedefault_buttons_config
DisableCachingtrue
PageWithExcerptINTERNAL:_BPaaS_excerpts

Configuring Your Own Buttons

If the standard buttons are not sufficient for your application scenario, you can create your own buttons and configure them according to your requirements.

Drag a new button from the Sidebar New Elements to the work area.

The element Button can be found in the category General Forms.

Use the settings in the Edit Sidebar to rename the button and provide it with the required properties.

Frequently Used Buttons

The following table offers an overview of frequently used buttons:

ButtonButton PropertiesDescription

Cancel

The necessary setting for a Cancel button is:

  • Stop Execution

If this button is clicked, the process stops at this point. Entries made in the current form are discarded.

If the current entries are to be saved before the abort, also activate the option:

  • Save Instance

If you are using regular expressions to validate entries in form elements, activate also:

  • Validate Fields


Send Email

You have several options for sending an email at the push of a button. The simplest option is to model an EPC, the only process step of which is to send the desired mail.

You can then refer to this model in the field Run Model After Click.



Save & Close

If you want form entries to be saved and to close the form afterwards, create a Save & Close button. Activate the following settings for this button:

  • Stop Execution
  • Save Instance

If this button is clicked, the process stops at this point and the form is closed. However, the form entries are saved before closing the form.

If you have used validation expressions for input fields that are to be checked, also activate the option:

  • Validate Fields

Back

The following setting must be selected for a Back button:

  • Go to Previous Step

If this button is clicked, the user switches back to the previous process step. Entries made in the current form are discarded.

If the current entries are to be saved before the abort, also activate the option:

  • Save Instance

If you have used validation expressions for input fields that are to be checked, also activate the option:

  • Validate Fields



Panel
titleOn this Page:
Table of Contents


Panel
titleRelated Pages:

Otp
Floatingfalse
maxHLevel2

rprde


Panel
titleRelated Documentation: