Actions
NIM Apps � Actions
Define what happens after a user interaction, from a guided navigation step to a controlled NIM operation.
An App action defines the outcome of a trigger. Attach actions to form buttons or grid controls, including buttons within a grid row, to navigate users, update App values, refresh data, or run a NIM operation.
Add an actionDirect link to Add an action
- Select the Button or Grid column that will trigger the action.
- Open Actions and select + Add.
- Choose an Action type, configure it, and save.
- Repeat for each action in the required sequence.
When more than one action is attached to an event, NIM runs them in descending order. Configure the sequence deliberately: validate or set values first, run the system operation next, then refresh or navigate.
Enable Wait for service actions to complete before continuing when a later action depends on the result of a service operation, such as collecting a system before refreshing a grid. Without waiting, the next action can begin before the service operation finishes.
Action referenceDirect link to Action reference
Idle
Use Idle as a placeholder when an event needs an action entry but should not perform an operation.
Restart App
Restarts the App and returns the user to its main page. Values entered during the current session are cleared.
Start App
Opens another App. The signed-in user must have access to the target App, and variable state does not transfer from the current App.
Form Initialize
Resets form variables and selected values to their initial state. For example, dropdown and checkbox selections are cleared along with any variables assigned to them.
Navigate to Form
Moves the user between forms in the current App while retaining variable state.
- Previous moves to the preceding form when one exists.
- Next moves to the next form when one exists.
- Form opens a specified form.
- Child opens a specified child form.
Target System Function Execution
Runs a selected function on a target system, such as creating an account, updating an attribute, or inserting a database record. Choose the target system and function, then provide the inputs required by that function.
Use Description to record a meaningful action description. Enter static text or use Append to add an App variable.
For each input attribute, choose a Value source:
| Value source | Result |
|---|---|
| None | Ignores the attribute. |
| Constant | Sends fixed text entered in the value column. |
| Variable | Sends the selected App variable value. |
| Clear | Clears the current target attribute value. |
| JSON | Sends a structured JSON value. See Action Sub-Mappings. |
All required mapping keys are required here as well. For example, an Active Directory user-create function requires the minimum attributes defined by its mapping.
Script Function Execution
Runs a script function configured outside the App. Select the required script function and confirm that it accepts the values the App supplies.
Service Resource Command
Runs a NIM resource command. Use it when the App needs to invoke a service operation rather than a target-system function.
Collect System Data
Collects fresh data from a selected target system. Enable waiting when a following action or grid refresh requires the newly collected data.
Run Scheduled Task
Starts an available Scheduler task.
Run Job
Runs an individual NIM job.
Grid Drag-and-Drop Reset
Resets the variables assigned to a drag-and-drop grid.
Grid Drag-and-Drop Update
Moves selected rows from one drag-and-drop grid to another. Configure at least two drag-and-drop grids with IDs that point to each other. The grids can allow single or multiple selection.
Navigate to URL
Opens a specified NIM or external URL.
Reset Variable
Resets the value stored in a selected App variable.
Set Grid View
Switches a grid to a configured view. Use this action with grid view navigation when another event should pivot the grid.
Generate Password
Runs the App's configured password generator and stores the generated value for later use in the App.
Validate the sequenceDirect link to Validate the sequence
Run the App and verify each action in the same order that users trigger it. Confirm that variables update before dependent actions run, target-system functions receive the expected values, and refreshes or navigation occur only after the required result is available.