Buttons are used inside Smart Forms to execute certain actions. App Designer supports 3 Types of Button Configuration inside your smart form - Entity Button, Module Button and Process button.


  1. Entity Button: Entity buttons facilitates actions for the entire entity e.g. submitting the form, database calls such as Save/Cancel/Back/Approve or Reject actions on your smart form. Entity buttons can be dragged and dropped between Main Tab and Main module of your Entity. The Entity Button configuration provide a list of property settings with 2 icons as shown below:


  •   -   This Icon is used to open Button Configuration popup. Entity Button configuration popup provides a list of settings which can help configure your entity effectively. Entity Button Configuration settings along with their usage are listed in table below:


Button Item

Default value

Mandatory

Description

Button ID

System generated

Y

Button ID is unique and it is generated by system.

Entity_ID

System generated

Y

System auto-displays the Entity ID associated with resp. Button.

buttonName

Default system generated no.

Y

User can edit default value to any value as per business needs.

Sequence

0

Y

Sequence is used to sequence the buttons while displaying on facade screen. Button with sequence '0' would show before button with       sequence '1' and so on.

Button Type

button

Y

Button Type

Page Action

N/A

Y

Page Action has 3 types - ENTITY_SEARCH, ENTITY_INSERT & ENTITY_UPDATE


  • ENTITY_SEARCH is the page action used to display buttons on search screen/Search entity mode.
  • ENTITY_INSERT is the page action used to display buttons on insert screen/Insert entity mode.
  • ENTITY_UPDATE is the page action used to display buttons on update screen/Update entity mode.

(Note: For more information on Entity Modes, Check Entity Modes)

Button Action

N/A

Y

There are 7 inbuilt Button actions provided by ONEWEB - searchResult(), resetSearchCriteria(), addEntity(), cancelEntity(), deleteEntity(), viewHistory() & saveEntity(). The use of each of the inbuilt button functions are listed below:


  • searchResult() is used to search for existing records from database based on search criteria.
  • resetSearchCriteria() is used to reset the search criteria .
  • addEntity() is used to open an entity screen to enter data.
  • cancelEntity() is used to close the entity edit screen.
  • deleteEntity() is used to delete record from database.
  • viewHistory() is used to show the history of the respective screen.
  • saveEntity() is used to save the data in the entity to the corresponding database tables.


Note: User can use any customize functions here instead of inbuilt functions, to perform a customized button action.

Authentication

No

Enable to call authorization Engine ( IAM- Identity access Management)

Action

N/A

-

styleClass

button_style

Y

Custom Style Of CSS

sourceTag

N/A

Used to define button styles using HTML commands.

imgFlag

N/A

To show the button as image


  •   - This Icon is used to delete a Button from your Smart Form Layout.


  1. Module Button: Facilitates user actions for 1-Many module in an entity. The scope of module buttons is limited to module levels and would not impact an entire Entity. It can be used to add, delete or update records of the module. The Module Button contains the same configuration settings as an Entity button as shown above , except different options available for Button Actions specific to modules. The Button action configuration options specific to module configuration are shown below :


Button Item

Default value

Mandatory

Description

Button Action

N/A

Y

ONEWEB smart form provides 7 inbuilt Button actions w.r. Module Button Configuration:


  • [MODULE_ID]Delete() -  This action is used to delete Module Record.
  • actionFormSubmitOnTable( 'insertMany','Y')
  • [MODULE_ID]Copy() - This button is used for Copy Record.
  • actionFormSubmit( 'insertMany','Y')  - This button is used for Pop-up logging into the Many module (Hashmap)
  • [MODULE_ID]ImportExcel() - This button is used for Import Excel to the Module Many table.
  • [MODULE_ID]ExportExcel() - This button is used for Export Table to Excel.
  • $( '#many_[MODULE_ID]_dialog('close'); This button is used to close the Module popup.
  • popupList('[POPUP_ENTITY_ID]','[CURRENT_MODULE_ID]') - This button is used to open the Neighbor Tab or to open the Popup Entity.
  • popupActionFlow('[MODULE_ID]') - This button is used to open popup.


Note : User can use any customize functions here instead of inbuilt functions, to perform a customized button action.


  1. Process Button: Facilitates smart forms to connect with internal business processes & micro flows. Process buttons can be easily dragged and dropped beside entity button inside your entity. The Process Button configuration provide a list of property settings with following 4 tabs as shown below : -


  • Pre Action: Describes any actions that user wanted to perform on an Entity before performing Process button action. It provides user 3 inbuilt options - cancelEntity() ,deleteEntity() and savaEntity(). (Note : User can use any customize functions here instead of inbuilt functions, to perform a customized pre action)



  • Process: Process tab provides list of configuration settings.

 


Process Tab Item

Description

Process Server Status

Shows Green Light for active connection.

Process Type

User could choose from Process or Micro flow.

Project

User must select their project in Process Designer from drop down list

Process

User must select their Process in Process Designer

Process Action

Action to choose for respective process -


  • Post Action: Describes any actions that user wanted to perform on an Entity after executing Process button action. It provides user 3 inbuilt options - cancelEntity() ,deleteEntity() and savaEntity(). (Note : User can use any customize functions here instead of inbuilt functions, to perform a customized post action)



  • Other Settings are similar as other module buttons settings.



Process Button Item

Default value

Mandatory

Description

Button ID

System generated

Y

Button ID is unique and it's generated by system.

Entity_ID

System generated

Y

System auto-displays an Entity ID associated with resp. Button.

buttonName

Default system generated no.

Y

Appropriate name for button as per business needs.

Sequence

0


Sequence is used to display buttons in sequence on facade screen. Button with sequence '0' would show before button with sequence '1' and so on..

Button Type

button


Page Action

N/A

Y

Page Action has 3 types - ENTITY_SEARCH, ENTITY_INSERT & ENTITY_UPDATE


  1. ENTITY_SEARCH is used to display buttons on search screen/Search entity mode.
  2. ENTITY_INSERT is used to display buttons on insert screen/Insert entity mode.
  3. ENTITY_UPDATE is used to display buttons on update screen/Update entity mode.

(Note : For more information on Entity Modes, check Entity Modes)

Authentication

No

Enable to call authorization Engine ( IAM- Identity access Management)

Action

N/A

-

styleClass

button_style

Custom Style Of CSS

sourceTag

N/A

Used to define button styles using HTML commands.

imgFlag

N/A

To show the button as image.