Component Events
Dashboard components may generate events when the user interacts with them. For example, a button has an action event which fires when the user clicks it.
An event may be specified as the binding activator for a binding. An "activator" causes the binding to do just that -- act, and thus write data from a dashboard to a context on the server, read data from a context and use it as a dashboard's content, or perform some other data processing.
Let's say we have a Name text field which is bound to a field in some server context's variable (i.e, the First Name of a user). Its binding also specifies an activator event -- the action event of the Save button, which is right next to it. When the user clicks this button, the following sequence of events occurs:
1) All bindings of the dashboard are scanned, looking for their specified Activator events.
2) The system sees that the binding for the Name text field has this action event defined as its "activator".
3) The binding is then executed, along with any other bindings which have this event as their activator (such as Last Name, if there is one). In simple words, the data in the text fields is now written into the database.
See dashboard data model for more information.
Was this page helpful?