# Actions Refer to the [actions](https://docs.jigx.com/building-apps-with-jigx/ui/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.	evaluate
		execute-entity
		execute-entities
		execute-sql
		submit-form
		/pages/Hx0tDH2e1JhKRSFdPsAo
		sync-entities start-sync-scope delete-sync-scope delete-sync-status
		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
		set & reset component state
		set & reset jig state
		set & reset solution 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
	Notify users about important information or errors in the app.	show-alert
Events	Actions that execute after a user or device performs a trigger.	onBlur 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

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.jigx.com/examples/readme/actions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.