App actions, such as entering a Page Series
for the first time, clicking on a button on a Page, selecting a piece of data, navigating to another part of the App, entering data, etc can all have Evoke click actions
associated with them.
Evoke Click Actions are part of Evoke's internal Component Library and are powerful functional commands that can be processed during the normal running of your App. You can use a single Click Action or process multiple Click Actions based on a single event or click. Click Actions can also be accessed/run from Header actions, Navigation Click Actions, Page level Actions and other places through Evoke Apps
There are many different uses for Click Actions, you can review a full list of current click actions
Just some of the many functions of Click Actions are:
Populating Data Sources with information/data from the database, Saving data back to the backend database.
Assigning, adding, manipulating data/creating new records in the database
Processing Adaptations, showing hidden Segments, etc
Navigation; navigate down to Child Pages, sideways to Siblings, up to parents/grandparents; All navigation
Retrieving related data associated with selected data
Validation, UI enable/disable, forcing events such as Save/cancel, opening external browsers sessions (to display a web page etc)
Plus multiple other actions
Using Click Actions
Wherever Click Actions can be used, you have the option of setting a Caption
, Action Type
(please see Navigation/Grid actions example opposite). The exceptions to this are actions on page load and actions on button click/selection that do not have a separate caption.
When the menu (identified by the caption) is clicked by the user then all of the Click Actions
with the associated ActionID
will be actioned.
Access to the click action setup screen (shown above) is either via the ellipsis menu option, the "actions on row click/tap" button in the general settings of a Template
, or simply by right clicking a template segment while in WYSIWYG mode.
Here you set the following options:
In addition to any of the additional actions definitions and details e.g. datasource, segmentid, etc. as identified in the Click Actions List