Actions

Refer to the actions topic to understand concepts such as local and global actions, types of actions, as well as, how and where to configure actions in jigs, and data. The topics in this section provide code examples for each action.

Adding an icon property in an action only applies to swipeable, secondary, and header actions. Primary actions do not support icon setups.

Here is a list of all actions and the category type the action forms part of.

Type	Description	Action
Execution	Actions used to interact with data.	execute-entity
		execute-entities
		execute-sql
		submit-form
		find-replace
		sync-entities
		print
		generate-pdf
		generate-file
		share
		update-profile
Navigation	Actions used to navigate to another jig or Home Hub	go-to
		go-back
		set-active-tab
Opening	Actions used to open certain Components.	open-map
		open-media-picker
		open-scanner
		open-url
Evaluation	Evaluation state - actions to determine a specific status or value of a solution, property, or component.	set-state
		reset-state
Grouping	Multiple actions can be grouped to run with a single user interaction. The actions can be run sequentially or executed in bulk.	action-list
Display	Action used to display a modal or popup containing a message.	confirm info-modal
Events	Actions that execute after a user or device performs a trigger.	onRefresh onFocus onPress onLoad (only on index.jigx) onChange onDelete onButtonPress (only on calendar jigs) onTableChange (only on index.jigx)
Reuse (global-actions)	Using the execute-action action provides greater control and enables reuse when the same logic needs to be performed in multiple places. For example, action.sync-entities might be called during app initialization, again when data changes, or when only a specific subset of data needs to be synced. By using execute-action, you can easily reuse the granular actions that handle the actual work, reducing duplication and improving maintainability.	execute-actions