Server-side events are used to integrate workflows and add custom Xbasic to do additional processing on the server for the UX component.
Fires after the Ajax callback is made
Fires after the UX Component is successfully validated. Does not fire if the dialogValidate event returns an error.
This event fires before any attempt is made to authenticate the user. A possible use for this event is to log out any user who might be logged in (use the A5WS_LogoutUser() function).
Fires before every Ajax callback made to the server.
Validates data in the UX Component that was submitted.
Fires every time the UX Component is run. This includes the first time it is run and whenever an Ajax callback is made.
Fires the first time the UX Component is run.
Fires after the user has been authenticated.
Fires when the user tries to logout.
Fires when the UX component is being synchronized. Fires after the client-side 'onSynchronizeDialog' event has fired.
- Server Side Event Handlers - Data Submitted - JSON
When the UX makes any type of Ajax callback, the data that are submitted (including data in Repeating Sections) are now available in a convenient new property called
- Server-side Action Scripting
Server-side action scripting makes it easy to add functionality to server-side events. For example, these actions can save data that was submitted from the client to the server, or populate client-side controls with data from a server, whenever the specified server-side event fires.