Designer

NIM Apps · Designer

Build forms, connect App behavior, test the experience, and check access before users run it.

The Designer brings the App's forms, variables, generators, validation, and access settings into one workspace. Work through the stages below, then use the tab reference to find the setting you need.

From design to releaseDirect link to From design to release

Build

Arrange formsAdd screens, rows, and items Set item propertiesConfigure input and display

Connect

Define variablesShare values across the App

Add behaviorConfigure actions and generators

Check

Run the AppTest the user journey with safe data

Review validationResolve errors and inspect warnings

Release

Confirm accessVerify the intended users can run it

Repeat the checks after changing a form, variable, action, generator, or access setting.

Find the right areaDirect link to Find the right area

To do this	Open
Arrange screens and controls	Forms → Design and Construction
Configure a selected item	Props; some items also have Table or Actions
Share values between items and actions	Variables
Generate names or passwords	Name Generator or Password Generator
Preview the experience	Forms → Run
Check configuration problems	Validation and Variable Validation
Choose who can run the App	Access
Configure report categories or report tables	Report Categories or Report Tables
Manage resources used by the App	Resources

Build formsDirect link to Build forms

The Forms tab is the design surface for items. Forms use a 12-column Bootstrap grid. In Design mode, drag an item by its handle onto a highlighted drop zone to place it above, below, or beside another control.

Select an item to open its Props. Some items also expose Table and Actions tabs. Configure the item's properties before connecting behavior with actions.

Inspect the hierarchyDirect link to Inspect the hierarchy

Use Construction to view the form as grids, rows, and items. Drag controls to rearrange them, use the delete icon to remove an item, and use the arrow control to add rows.

Work with variablesDirect link to Work with variables

The Variables tab defines values shared throughout an App. Items and actions can read them, making variables useful for values calculated on one form and needed on another.

Variable type	Use it for
JavaScript	Calculations or derived values based on App data and other variables.
Timer	Incrementing or decrementing values that start with the App or a selected form.

Name variables for the value they contain, use predictable output types, and keep secrets out of variable values and logs. When an action reads a variable, check its value in Run mode before relying on it.

Validate JavaScript before saving

Check the syntax and expected return value of JavaScript used in variables or item properties before you save it. Invalid JavaScript can break the App and may prevent it from appearing in the Designer. After a change, open the App in Run mode and verify the affected forms and actions.

Add generatorsDirect link to Add generators

Use the Name Generator or Password Generator tabs when the App must generate account names or passwords.

Tab	Configure	Output
Name Generator	Generator, activation delay, input fields, and input source values	Map generated names to App variables.
Password Generator	Generator and its input fields	Map generated passwords to App variables.

Create the required name generator or password generator first. Map the generated output to the variable that the form or action will use.

Password generation

A password generator produces a value only when a Generate Password action runs.

Name GeneratorDirect link to Name Generator

Use the Name Generator tab to select the configured generator and store its result in the variable used by the App.

Password GeneratorDirect link to Password Generator

Configure report data & resourcesDirect link to Configure report data & resources

Some Apps use report categories, report tables, or resources. Open the matching Designer tab when the App requires one of these components.

Report CategoriesDirect link to Report Categories

Use Report Categories to configure the categories available to the App.

Report TablesDirect link to Report Tables

Use Report Tables to configure the tables available to the App.

ResourcesDirect link to Resources

Use Resources to configure resources available to the App.

Validate before publishingDirect link to Validate before publishing

Switch Forms to Run mode and follow the same route a user would take. Test navigation, actions, generated values, and both valid and invalid input with safe test data. Then review the validation tabs.

Include a keyboard-only pass through each form, check that controls have understandable labels, and make sure validation messages identify the input to correct. WCAG 2.2 provides the accessibility criteria to use when reviewing the App experience. Test the published App with the assistive technologies your users rely on; the Designer preview alone cannot establish conformance.

Variable ValidationDirect link to Variable Validation

NIM validates values tied to form items when an input loses focus and when a form is submitted. Use Variable Validation to exclude values that are expected to change between those moments, such as a generated JavaScript value or a calculated filter field.

Do not exclude ordinary user input from validation; fix the input rule or variable mapping instead.

Form ValidationDirect link to Form Validation

The Validation tab reports construction errors and warnings. Select a description to locate the affected form item. Errors prevent successful validation; warnings do not, but should be resolved whenever possible.

Configure accessDirect link to Configure access

The Access tab controls who can run the App using users and groups from NIM's Internal system. NIM creates an nga_-prefixed group for each App.

Preferred access method: Role Model

Select the App's nga_ group in Access and save to allow that group to run the App.
In a role model, base a role on a filter that selects the intended internal users and assign the App group to that role.
Process the active role model through a job to provision group membership. Verify access with a non-administrator test user.

See the App tutorial for a worked example.

Before users access the AppDirect link to Before users access the App

Test each form, action, and navigation route in Run mode, including empty, invalid, long, and unexpected input.
Check that generated names and passwords reach only the intended variables and actions.
Resolve validation errors and review warnings.
Confirm the intended user can open and complete the App.

For a complete build example, follow the App tutorial.