Determining whether variable settings are incorrectly configured



If the Variable Editor or variables within the editor are not appearing as expected, the variables may have been set up in a number of places incorrectly:

A good place to start troubleshooting is to ensure that the variable itself is correctly configured. There are multiple configuration points for a variable and any one of these may contribute to unexpected behavior. 

To determine if variable settings are incorrectly configured:

  1. Navigate to Service Catalog > Maintain Items.
  2. Select the item that is causing issues.
  3. Open the Catalog Item form and navigate to the related lists at the bottom. The Variables related list holds the variables and their configurations.

  4. From the list, open the variable causing the issue.
  5. Try the following troubleshooting steps:
    1. Mandatory: mandatory behavior can be configured in many ways. For example, in the Mandatory field, in a client script, or in a UI policy. It is important that these different mechanisms do not clash with each other or you may see unexpected behavior.
    2. Read-Only: read-only behavior can be configured in many ways. Using multiple methods for the same variables can create unexpected behavior.
    3. Default value: default value / dynamic default value are powerful features because they allow scripting. They can also create confusing behavior for end-users on how certain fields are populated without them filling them out. Checking the settings/configurations here is a good place to start.
    4. Active: a false value here may cause problems.
    5. Read roles: if the variable is correctly configured for Mandatory, Read-Only, Default value, and Active, the variable still may not be visible if there are restricted Read roles. If there are no roles, then this variable appears to everyone, otherwise, it is removed from the form.