Form Layout

Prev Next

Overview

Once you configure the L1-L3 UDM levels, you can configure the L4 level, which is primarily the Category Forms. You can think of Categories as a container, which can be used to add your assets. In ITAM, Category can be defined as a high-level classification or container that groups similar assets together based on their type, purpose, or characteristics. A category acts as the parent grouping under which individual asset records are created and managed.

The L3 levels are pre-defined and out-of-the-box factory default available. L3 assets such as Fixed, Accessories, Consumables, Facilities, etc.. are alreay available. However, to better group assets under Fixed, Accessories, etc.. based on their usage, purpose, you need to create categories such as Desktop, Laptop, Mouse, etc..

These categories are also used, when you are adding an asset as shown in the following figure.

Figure: Add Asset.

Category Examples:

Category

Example Assets

Desktop

Dell OptiPlex, HP ProDesk

Laptop

Lenovo ThinkPad, Dell Latitude

Keyboard

Logitech Keyboard, Dell Keyboard

Mouse

HP Wireless Mouse, Logitech Mouse

Monitor

Dell 24" Monitor, Samsung Monitor

Printer

HP LaserJet, Canon Printer

Mobile Phone

iPhone, Samsung Galaxy

Server

Dell PowerEdge, HPE ProLiant

Network Device

Router, Switch, Firewall

Chair

Ergonomic Chair, Visitor Chair

Fan

Ceiling Fan, Pedestal Fan

Table

Office Desk, Conference Table

Use case and benefit

Example: Review an existing Toner or Keyboard form before adding a similar category. This helps identify reusable fields and avoids creating another field for information already represented in the model.

Recommended check: After a change, reopen the same category under the same department and confirm that the intended layout and fields remain present.

Configuring Categories

Prerequisites

• Use an account with access to Asset model studio and the configuration pages.

• Identify the department, classification, and asset type under which you intend to add or change a category.

• Prepare field labels, input rules, allowed values, dependencies and role access requirements.

• For a shared-field change, identify the categories that inherit that definition.

To add a category form, perform the following steps:

  1. Log in as an Administrator.

  2. Click Workspace > Admin > Infrastructure > Platform > Form Designer.

  3. Click Form Layout tab and select the Department under which you want to add the Category.

  4. In addition, you can select the Classification as well such as IT or Non-IT under which you

    Figure: Form layout

  5. Click Add Form.

  6. The New form wizard contains Basic, Category, and Asset code stages.

  7. On Basic, enter a unique Category name and Short code. Add a Description when needed.

  8. Resolve any inline errors, then click Next.

    Figure: Basic details for New Form

    Field Name

    Description

    Category Name

    Required category name used to identify the form in the library. Example: Laptop, Desktop, Mouse, Keyboard, Chair, etc..Use values appropriate to your asset taxonomy.

    Short Code

    Required short identifier; it can be included in the asset-code format.

    Description

    Additional information about the category and its purpose.

    Table: Basic Form Details

  9. In the second step, select the category as IT/Non-IT and select the Asset Type (such as Fixed, Accessories, Consumables, etc..) under which you want to add the category and click Next.

    Figure: Select the Asset Type

  10. You can configure and select the Asset Code and review the Asset Code format.

  11. Select the required attribute components and separator. The displayed choices include Category short code, Manufacturer, Model, Location Short Code, and Asset ID; separators shown include a hyphen and slash.

  12. Use View all attributes if you need to inspect further available components. Remove an unwanted component using its x control.

  13. Check Preview to confirm the intended format.

    Note

    Example

    Category short code + hyphen + Asset ID produces the demonstrated preview MAC-001. The preview illustrates the format; verify the actual generated code when testing asset creation in your environment.

    Recommended practice: use a consistent code structure across related categories. Avoid including information that changes frequently unless your asset-code policy requires it.


    Figure: Asset Code

  14. Click Open form builder.
    In the form builder, remain on Define attribute. Review the category label at L4 and the inherited L3, L2, and L1 groups.

  15. Use Add section to create a category-specific section.

  16. Use + Add next to the L4 category to create a new attribute. Complete its field settings and click Create.

  17. Add available category attributes to the category section. Review the chips in the section and any Required markers.

  18. Arrange sections within their level. For an inherited structural change, return to the owning model level.

  19. Click Next when the attributes and sections are ready.

    Figure: Add Attributes to Category (L4 level)


    Example Use Case

    A Keyboards form can capture Switch Type and Connection Type alongside inherited IT device information and Universal identity fields. Add fields needed only by this category at L4, then test required-field behavior before releasing the form to users.

    The screenshot shows the existing Keyboards example.

  20. On Select layout, choose 2-column or 3-column.

  21. Use the Base form dropdown to preview a specific view where available. The screen states that the selected layout type applies to all views.

  22. Scroll through every section and check field labels, grouping, order, and available space.

  23. Click Save.

    Figure: Select layout

  24. Return to Form layout, find the category, and review its rendered form. Reopen it with Edit to confirm the configuration persisted.

The category is available in the form library and the preview displays the saved sections and fields. Use two columns when longer labels or wider inputs need more space; use three columns only when the resulting form remains easy to read.

Troubleshoot displayed validation messages

The following messages and restrictions are visible in the KT. Use the corresponding action to correct the configuration context or input.

Figure: Duplicate category name and short code

Message or restriction

Action

Category name already exists

Enter another category name. If you intend to change an existing category, cancel creation and select that category in Form layout, then click Edit.

Short code already exists

Enter an unused short code and confirm the error clears before clicking Next.

View only - edit this attribute at L1 level

Close the dialog. Select Universal on Model and open Edit model there.

Cannot edit or delete sections at another level

Return to the entity level that owns the section, then make the structural change there.

Cross-level attribute placement is not supported

Place the attribute in a section at its own level. Add a separate category-specific field only if it represents a distinct requirement.

Configure checkbox and date inputs

Use Checkbox for a yes/no characteristic, Date for calendar information and Date and time for time-sensitive events. These input types help users enter consistent values.

1. Create or edit the attribute at its owning level. Enter a descriptive name and choose Checkbox, Date or Date and time.

2. Complete the common settings. For Date or Date and time, open Validation type on Basic and choose the rule required by the process.

3. Create or save the attribute, place it in the appropriate section and save the model.

4. Open the category form and verify the input control and date behavior.

Figure: Checkbox and Date/Time

Field Name

Description

Date

Validation Types:

Allow current date; Don't allow future date; Don't allow past date; Free date.

Date Time

Validation Types

Current time window; Don't allow future date and time; Don't allow past date and time; Custom date and time.

Configure Text Boxes and Text Area

Use Textbox for concise labels or identifiers and Textarea for longer descriptions. Length and duplicate controls help align the form with the data you need.

  1. Select Textbox or Textarea on Basic.

  2. Set Min length and Max length to the permitted input range. The Textbox demonstration uses 1 and 20; the Disk size example later uses 1 and 300.

  3. For Textbox, set Allow duplicate values as appropriate and complete Validation type when required.

  4. Set placeholder, help text, filter inclusion and Used in where needed.

  5. Create or save the attribute and save the containing model or category form.

    Figure: Text box and Text Area

    Field Name

    Description

    Text box

    Use Text Box if you want user to insert text which is very short and limited to specific max length, which is not too much. In addition, you can specify the Validation type for the type of text, which you want to only allow in the text box.

    Examples:

    Alphabets only - Allows only alphabetic characters. Valid - Dell. Invalid - Dell-01

    Alphanumeric - Allows letters and numbers.

    Decimal - Allows decimal numeric values.

    Email - Validates email address format.

    Free text - Allows users to enter any combination of characters without format restrictions.

    Number only - The Numbers Only validation type restricts the textbox to accept only numeric values (0-9). Users cannot enter alphabetic characters, special characters, or spaces.

    Text Area

    A Text Area is a multi-line input field that allows users to enter large amounts of text across multiple lines. It is typically used to capture descriptions, comments, notes, justifications, and other detailed information that cannot be accommodated in a single-line textbox.

Create a dropdown from a master source Use case and benefit

Use a Dropdown when users should select a controlled value, such as an asset condition or a reference from a master. This can reduce spelling variants and inconsistent classification.

  1. Create or edit the attribute and select Dropdown.

  2. Select Master source. Visible sources include Common master, Cost center, Department, Location and Project.

  3. If using Common master, choose Common master type.

  4. Complete any source-specific settings exposed by the dialog.

  5. Configure Dependency only when the field must be limited by another attribute.

  6. Create or save the field, place it in a section and save the model.

    Figure 6 Dropdown master source selection

Expected result

The category form presents a selectable list sourced from the configured master. Verify the list under the relevant department and user role.

Recommended check: Ensure the intended master contains usable values before investigating a blank dropdown as a form problem.

Configure dependent dropdown mappings

A dependency lets one field control the choices offered by another. For example, a selected Asset condition can limit the available values in a common-master dropdown.

  1. In the dropdown Basic settings, select its master source and common master type when applicable.

  2. Scroll to Dependency. Select the controlling field under Depends on. In this example, you have selected Asset condition.

  3. In the mapping grid, select a Parent value and the permitted Child value or values.

  4. 4. Click Add mapping to define the next parent-to-child relationship. Use the delete control to remove a mapping that is no longer needed.

  5. Create or save the attribute and save the enclosing model.

  6. Test every configured parent choice in a category form. Confirm the child list and behavior when the parent is changed.

Figure: Dependency configuration: Parent and child values mapping

The visible example maps parent Fair to child Active in AM Antivirusstatus; Active and Inactive are shown as selectable child choices. These values illustrate the controls and are not a prescribed business rule.

Recommended check: Check missing parent mappings, blank parent values and an existing child selection after the parent changes. Verify the actual reset behavior before relying on it in an operational process.

Configure Tree

You can also configure a Tree type custom attribute using the Tree. A Tree Control is a hierarchical selection control that allows users to select a parent value and view or select its associated child values based on the parent selection. It establishes a structured relationship between two or more levels of data, making it easier to manage and select related information.

To configure a Parent and child relationship, in Dependency select ‘Assigned Location’ and in the Parent value select the location or All location and corresponding cost centers you want to populate from the Child values.

In this example, Location acts as the Parent, and Cost Center acts as the Child. The Cost Center options dynamically change based on the Location selected by the user.

Figure: Configure Dependency | Parent and Child for a Tree Type

User Search type

User Search Control is a field type that allows users to search for and select usernames from a predefined user directory or user repository. As the user starts typing a name or username, the control automatically fetches and displays matching user records, enabling quick and accurate user selection without requiring users to manually enter complete usernames.

Example: Searching and Selecting a User

Consider an ITSM application where an administrator needs to assign an incident to a specific user.

Figure: User Type Field