Join us on May 14-15, 2019 at Forrester Digital Transformation & Innovation 2019 in Chicago, USA.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In this article, we will discuss on how we can control form fields' values saving based on which button is clicked on form submission. Let's use this form as an example.

The business requirement is to not save the value for "Contact" when "Save As Draft" button is used to submit the form.

In order to address this requirement, the field "contact" needs to be in its own section. This is because form section offers permission control.

In the section where the subform is, set the permission of the section to Bean Shell Script.

We will then need to detect when the "Save As Draft" button is clicked or not to determine the next step forward.

The same script can also be placed in the subform's form section permission, or in the subform's form permission too.

With this, the value "c" will only gets replaced with user's input value when "Complete" button is hit, otherwise, it will stays as it is.

  • No labels