Buttons & Actions

Buttons App Designer supports 3 types of Button Configuration inside your smart form.

Entity Button: Entity buttons facilitate actions for the entire smart form e.g. database calls or Cancel /Reject actions on your smart form.

The figure shows an example of Entity Buttons:

Module Button: Facilitates user actions for the 1-Many module. It will not impact the entire entity and can be used to add, delete or update records of the module.

The figure shows an example of Module Buttons:

Process Button: Facilitates the smart forms to connect with internal business processes or microflows.

The figure shows an example of Process Button:

Note: To see all configuration property settings of Button's in detail, please refer Button section in Chapter 8 - App Designer Reference.

Actions Actions are hooks provided by App Designer to attach a custom JSP, JavaScript or a custom Java class to your entity. There are two types of Actions.

Entity Action: Entity Actions cover an entire entity. You can attach Java classes to Entity Action to override the function to save or update an entity. But you cannot attach a JSP file to an Entity Action.

The figure shows an example of Entity Action

Module Action: Module Action covers only the corresponding module. You can include a custom JSP into your module using a Module Action, you can also add Java class to override and then add, update, save functions on the module, or add JavaScript functions to customize the interaction on the modules.

The figure shows an example of Module Action:

Note: To see all configuration property settings of Button's in detail, please refer Action section in Chapter 8 - App Designer Reference.