Reusable Items
NIM Apps · Form items
Create a reusable, preconfigured group of form items when the same experience belongs in more than one App or form.
When to compose an itemDirect link to When to compose an item
Compose Items turns one or more configured form items into a reusable library item. Good candidates include a standard header, a consent notice, a consistent contact-information section, or a fixed status panel.
After you create a composed item, its item properties cannot be changed where it is reused—including size, spacing, alignment, text, and Grid targets such as filters or audit-query results. Design it to be broadly reusable before saving it.
| Use a composed item when | Do not compose it when |
|---|---|
| The controls should look and behave identically everywhere. | Each App needs a different label, text, filter, layout, or action. |
| A shared experience reduces repeated design work. | The content is still changing frequently. |
| The item group has no App-specific dependencies. | It relies on variables, Grid data, or actions unique to one App. |
Create a reusable itemDirect link to Create a reusable item
-
Start with a blank form and enable Compose Item Mode in the lower-left corner.
-
Build and configure the form items that should be reused.
-
Hold Ctrl and select every item in the group. Selected items show a light red background.
-
In the Items tab, select Create Item.
-
Choose an existing library or create a new one, then give the item a clear, reusable name and save it.
Reuse the itemDirect link to Reuse the item
The new item appears in its library in the lower-left area of the Form Builder. Drag it onto a form just as you would a built-in item.
Maintain a useful libraryDirect link to Maintain a useful library
- Name libraries by purpose, such as Branding, Shared notices, or Self-service fields.
- Name items by the user-facing outcome, such as Standard request header.
- Keep composed groups focused; a small reusable section is easier to place than a full form layout.
- Test the item in more than one form before standardizing on it.
- If a reuse case needs different properties, create a separate variant rather than forcing an unsuitable shared item.