> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/concepts/actions/actions-management-and-shortcuts.md). # Actions management & shortcuts ## Scope UI Bakery actions can be **page-specific** or **global**: * *Page-specific* actions are executed only on a certain page. You can easily convert a page-specific action into a global one or the other way around, just by dragging the action to the corresponding folder. You can also assign a page-specific action to another page, by simply moving it to the global state first and then transferring it to the necessary page. {% @arcade/embed flowId="KZbKlRSAvqjFjV02W53t" url="" %} * *Global* actions are available across the whole app. When using a global action, the **value it holds will be retained across page navigations** by default. This means that if you load some configuration settings using a global action, the settings will be accessible on all pages of the app using `{{actions.actionName.data}}`. ## Folders Folders offer a handy way of structuring your actions and are especially useful when you have a lot of actions in your application. You can drag actions to different folders as well as remove them. You can also add folders inside other folders - make a nested structure. {% @arcade/embed flowId="oMN3rX5oX4n9NFJRt7A4" url="" %} ## Usages From the *Actions* panel, under the **Usages** tab on the right side, you can check where each action is used. Here, you can see whether an action is used in any components, other actions, or references. If you click on a specific component or action, you will be taken to its settings, and you'll be able to make any adjustments if needed.
## Hotkeys During development, all actions can be run using the `Ctrl + Enter/Cmd + Enter` hotkey. :heavy\_check\_mark:You can quickly navigate to a certain action using `Cmd/Ctrl + click`. Simply point to the action name and use the hotkey - it will take you to the selected action. In the same way, you can navigate to components. :heavy\_check\_mark:For action steps that have a code editor, such as **JavaScript Code** and **SQL Query**, the following hotkeys are supported: * `Ctrl + F/Cmd + F` - find in code; * `Ctrl + G/Cmd + G` - next find result; * `Shift + Ctrl + F/Cmd + Option + F` - find and replace; * `Ctrl + L/Cmd + L` - jump to a line; * `Ctrl + Alt + L/Cmd + Option + L` - format code. ## Code analysis limits To keep the editor responsive when working with large values, UI Bakery automatically disables some code analysis features. For multiline code: * linting is disabled when the value is longer than 50,000 characters; * syntax highlighting is disabled when the value is longer than 100,000 characters. For code written on a single line: * linting is disabled when the value is longer than 5,000 characters; * syntax highlighting is disabled when the value is longer than 10,000 characters. When a limit is reached, open the expanded editor and click the code analysis button in the toolbar to temporarily enable linting or both linting and syntax highlighting. Click it again to restore the automatic limits. These limits affect editor assistance only. UI Bakery does not truncate or modify the code, and the limits do not affect its execution. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.uibakery.io/concepts/actions/actions-management-and-shortcuts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.