> ## Documentation Index > Fetch the complete documentation index at: https://docs.powerux.app/llms.txt > Use this file to discover all available pages before exploring further. # Action Steps > This page contains the list of action steps that can be used to when creating custom client-side business logic in UX Flows ## Basic Action Steps Hides the selected controls from the form Displays the selected controls from the form Locks the selected controls on the form Locks the selected section related controls on the form Locks the selected tab related controls on the form Unlocks the selected controls on the form Unlocks the selected section related controls on the form Unlocks the selected tab related controls on the form Marks the selected columns as required on the form by displaying a red asterisk (\*) next to the column’s title. Marks the selected columns as recommended on the form by displaying a blue plus sign (⁺) next to the column’s title. Marks the selected columns as optional on the form Sets focus on the selected tab by navigating to the tab on the form. Clears the value of the selected columns Displays a loading spinner, which is a visual indicator used to show that a process is in progress and that the user should wait for it to complete. The spinner will be displayed on the user interface until you use the **Hide Loading Spinner** step. Removes the loading spinner from the user interface once the process is complete. This step is necessary to ensure that the spinner is not displayed indefinitely. Once the Hide Loading Spinner action step is selected, the spinner will be hidden from the user interface. Updates the form data in the background, without reloading the page. This ensures that any changes made to the form will be immediately reflected. Saves the record asynchronously, which means that the saving process will occur in the background. This allows you to continue with other tasks without waiting for the save to complete. Stops any default behavior that is expected to happen, for example, you can stop navigating to the next step in the Business Process Flow if the record doesn't qualify to pass to the next step. Another example, is to not open the lookup field when the user clicks on the lookup record tag. This allows you to extend and change the behavior and apply a custom one in a supported way. Displays an error message on a specific control. **Attention**: When setting an error on a new control, remember that the Unique Id you choose must be different for each error notification. If you use an already existing Id, you won’t be able to create your notification. **Tip**: Use a short Unique Id for easier identification. Removes an error message that has already been set. Filters the contents of a lookup table based on specific criteria. By using this action step, you can create a subset of the original table that only includes rows that meet certain conditions. This can be useful for a variety of purposes, such as identifying specific records within a larger dataset or simplifying the data that is displayed to the user. Separate tables by using a comma "," Use the logical name of tables, for example: `"contact,account,new_x"` ## Advanced Action Steps