Troubleshooting Scenario Questions

The condition 'current.state == 1' is incorrect syntax.

Why wrong: The syntax is valid for a before query business rule.

Another business rule with higher order is preventing execution.

Why wrong: Order only affects sequence, not whether a rule runs.

The business rule is scoped and cannot access the table.

Why wrong: Scoped business rules can access tables within the same scope.

The scheduled import job was interrupted by another job

Why wrong: Job interruption would cause failure, not partial load.

The transform map has a filter that excludes certain records

Why wrong: Filters on the transform map affect which records are processed, but the question states partial data, not missing specific types.

The field mapping is incorrect and some fields are not being populated

Why wrong: Incorrect field mapping would result in empty fields, not fewer rows.

Add client-side caching using $scope

Why wrong: Caching reduces repeat requests but doesn't speed up the initial query.

Load the widget using ng-if instead of ng-show

Why wrong: ng-if removes DOM elements but doesn't affect server query performance.

Create a custom table with only required fields

Why wrong: Custom table helps but doesn't address the missing filter; still needs filter.

Wrap the script in a try-catch block and log the error then return

Why wrong: This would hide the error and the workflow would still not start.

Change GlideRecord('task') to GlideRecord('change_request')

Why wrong: This would work but is unnecessarily complex; current already holds the record.

Add a check if (task.isValidRecord()) before accessing cmdb_ci

Why wrong: This would prevent the error but would not fix the logic; the CI would not be found.

The assignment group field is read-only on the form but can be set via business rule

Why wrong: Business rules can set read-only fields.

The business rule is set to run only in the global scope

Why wrong: Scope does not affect execution; the rule runs if conditions are met.

OAuth token for LDAP is expired

Why wrong: LDAP does not use OAuth; it uses bind credentials.

LDAP attribute mapping does not match target fields

Why wrong: Attribute mapping issues cause field errors, not import failure.

LDAP server is unreachable

Why wrong: Connectivity is a basic check, but it is not specific to LDAP import configuration.

The 'change_request' table is locked for data imports.

Why wrong: Table locking is not a common reason; it's more likely a validation issue.

The user's role is not recognized when using SOAP web services.

Why wrong: The user's role is recognized; ACLs are evaluated correctly.

The SOAP message uses a different namespace.

Why wrong: A namespace mismatch would cause a parsing error, not a failure to insert.

The client script is set to run on the 'Load' event instead of 'Change'.

Why wrong: Could be, but hide field typically works on load if condition is evaluated; not most likely.

The script is using a deprecated API.

Why wrong: Deprecation likely not the issue.

The script is not running due to a missing 'Run As' role.

Why wrong: Client scripts don't have Run As.

The field is not part of the application scope.

Why wrong: Fields can be referenced across scopes.

Review the syslog for error messages.

Why wrong: While helpful, this is not the most efficient first step; Studio's debugger is more direct.

Check the ACLs on the table.

Why wrong: ACLs do not affect client script execution.

Add a gs.log() statement to the server-side code.

Why wrong: Client scripts run client-side; server-side logging won't help.

Check the business rule order.

Why wrong: Order is relevant for conflicting rules but not a primary diagnosis step.

Run the business rule from the context menu.

Why wrong: Business rules cannot be executed manually.

Check if the table is locked.

Why wrong: Table locks affect records, not business rule execution.

Use a parent widget that calls three child widgets

Why wrong: Incorrect: Parent-child setup can still lead to cascading failures if parent fails.

Use a widget that loads data in parallel with error handling

Why wrong: Incorrect: Despite parallel loading, if the single widget has a critical error, all data may be lost.

Use a single widget that fetches all data sequentially

Why wrong: Incorrect: Sequential fetching means one failure stops all data loading.

Check the client script that may be hiding the field.

Why wrong: Client scripts could hide it, but the first step is to verify the field exists on the form.

Check the ACLs for the 'Cost Center' field.

Why wrong: ACLs control data access, not visibility.

Check the role requirements for the field.

Why wrong: Roles affect access, but if the field is not on the form, it won't show.

Check the browser's HTML source for the macro's placeholder.

Why wrong: This can help but is not the most direct initial step.

Ensure the UI Macro is in the global scope.

Why wrong: Scope issues are possible but syntax errors are more common.

Verify that all referenced UI Scripts are loaded.

Why wrong: UI Scripts are not typically used in UI Macros; macros use Jelly.

Verify that a script include used in the condition is accessible

Why wrong: UI Policy conditions are typically simple conditions, not script includes.

Ensure the field has a 'Mandatory' attribute on the dictionary

Why wrong: UI Policy overrides dictionary settings; the field does not need to be mandatory by default.

Check if the 'Mandatory' ACL on the field prevents modification

Why wrong: ACLs control read/write access, not mandatory behavior.

The script is trying to set a field that is read-only before insert.

Why wrong: Category is writable before insert.

The sys_choice table does not contain the choices for the incident category field.

Why wrong: It does, choices are stored there.

The GlideRecord query is incorrectly using 'name' instead of 'table'.

Why wrong: 'name' is the correct field for table name in sys_choice.