> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/examples/readme/actions/state-actions.md). # State actions Jigx provides three levels of *state management* that allow you to store, update, and share data dynamically within your app.\ Each state type serves a different purpose, from app-wide variables to screen(jig)-specific and component-level data, enabling flexible logic and responsive UI behavior. ## **Types of State**

State Type	Scope	Defined In	Accessed Using	Typical Use Case
Solution State	Global (shared across all jigs)	`index.jigx`	`@ctx.solution.state`	Store user roles, preferences, or data shared across multiple screens.
Jig State	Screen-specific	Inside a jig file (e.g., `jig-a.jigx`)	`@ctx.jig-state`	Manage temporary or screen-level logic, such as workflow steps or filters.
State (Component State)	Component-specific	Within a component or control	`@ctx.component.state` `@ctx.current.state`	Track component interactions, such as toggles, field input, or selected list items.

## **Best Practices** * Use **Solution State** for global variables shared across multiple screens. * Use **Jig State** for logic or UI control within a single screen. * Use **Component State** for localized interactions within a specific component. * Always reset state where appropriate (e.g., on logout, refresh, or workflow completion) to ensure consistent behavior. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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/state-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.