AX1386
The following diagram illustrates the full update process for Axiom forms. This is provided to help form designers understand the timing of various events, so that they can set up formulas and interrelationships between components and Axiom features set up in the file.
Users trigger this update process by doing one of the following:
- Clicking a Button component in the form.
- Changing any interactive component that is configured to Auto Submit.
- Performing other actions that trigger the form update, such as clicking the save icon in the Task BarThe gray bar that displays across the top of browser-based Axiom files, as well as various feature pages of the Web Client. The Task Bar provides access to various tasks that are specific to the current area, page, or document..
The Command Processing Steps only apply when the update is triggered by a component that has one or more defined commands, such as a Button component or a KPI Panel component. The processing steps indicate when the command will be executed during the process. When using an Axiom form as a dialog in the Excel Client or the Windows Client, you can also indicate where the command will be executed (the processing context)—either on the form itself, or on the active client spreadsheet.
NOTE: Refresh variables do not trigger a full form update as described in this topic. For more information on what actions occur when refresh variables are applied to a form, see Defining refresh variables for Axiom forms.
NOTES:
-
The After Save Data processing step is only evaluated if a save is performed during the update. If you have a command that is configured to run After Save Data, but no save-to-database is performed, then the command will not be run.
-
Data lookups will be run as normal (unnamed are run as part of every data refresh, named are run after specific Axiom queries if configured to do so).
-
When using embedded forms, special behavior applies to the form update cycle, as both the parent and child forms may be updated. For more information, see Form session and update behavior for embedded forms.
-
Data Grid and Fixed Report components are not refreshed by default during the form update cycle. Instead, the Component Dependencies property is used to create an association between the Data Grid / Fixed Report component and one or more other components. If one of the other components submits a changed value, the grid or report is refreshed.
Keep in mind that refreshing the Axiom form using web browser functionality does not trigger this update process. Refreshing the browser page reloads the form as if it were initially opened. For more information on how an Axiom form determines its initial state when it is opened, see Update and save behavior for Axiom forms.
