Dynamic form field population via REST API fails for conditional logic

BPM ServiceNow
, , , , , , , ,
1

I’m working on a custom form in ServiceNow where fields need to populate dynamically based on user selections. The REST API call works fine for simple field population, but when conditional logic is involved, the form submission gets blocked.

The scenario: User selects a category from dropdown, which should trigger an API call to populate related fields based on field dependency mapping. The API payload structure seems correct, but the conditional logic triggers aren’t firing properly.

Here’s the API call I’m using:

var request = new sn_ws.RESTMessageV2();
request.setEndpoint('https://instance.service-now.com/api/now/table/form_fields');
request.setRequestBody(JSON.stringify({category: selectedValue}));

The fields remain empty even though the API returns valid data. Has anyone dealt with conditional field population via REST API in forms management? The form just sits there waiting, and eventually times out without populating the dependent fields.

2

Thanks for the responses. I do have a callback function, but maybe I’m not triggering the conditional logic correctly. The API returns data successfully - I can see it in the browser console. But the form fields don’t update. Should I be using a specific event to trigger the field dependency mapping after the API response?

3

Let me give you a working solution that addresses all three focus areas properly.

Field Dependency Mapping: First, ensure your field dependencies are registered in the system. Go to System UI > UI Policies and verify that your dependent fields have the correct conditions set up.

Conditional Logic Triggers: The core issue is that REST API responses don’t automatically trigger form events. You need to explicitly fire them. Here’s the corrected approach:

var request = new sn_ws.RESTMessageV2();
request.setEndpoint('https://instance.service-now.com/api/now/table/form_fields');
request.setHttpMethod('POST');
request.setRequestBody(JSON.stringify({category: g_form.getValue('category')}));
var response = request.execute();
var responseBody = JSON.parse(response.getBody());

responseBody.fields.forEach(function(field) {
    g_form.setValue(field.name, field.value);
    g_form.fireEvent(field.name, 'change');
});

API Payload Structure: Your original payload was too simple. Include metadata about which fields need updating and their dependency chain. The response should contain not just values but also field names and any validation rules.

Additional critical points:

  1. Use g_form.fireEvent(fieldName, ‘change’) after EACH setValue call
  2. Implement proper error handling with try-catch blocks
  3. Add a loading indicator so users know the form is processing
  4. Consider using onSubmit client scripts to validate all conditional fields are properly populated before allowing form submission
  5. Test with both onLoad and onChange scenarios

The fireEvent call is what triggers the conditional logic re-evaluation. Without it, ServiceNow’s form engine doesn’t know the field has changed programmatically. This should resolve your form submission blocking issue completely.

4

The problem is that ServiceNow’s built-in conditional logic doesn’t automatically re-evaluate when you programmatically set field values via API responses. You need to manually trigger the field change event. After setting the values in your callback, use g_form.fireEvent() to notify the form that the field has changed. This will cause the conditional logic to re-evaluate and process your field dependencies properly.

5

I had the exact same issue last month. Here’s what worked for me: instead of just setting values, I wrapped everything in a GlideAjax call with proper sequencing. The key is ensuring your conditional logic triggers fire AFTER all dependent fields are populated. Also double-check that your UI policies aren’t conflicting with the programmatic updates.

6

I’ve seen this before. The issue is usually timing - the conditional logic evaluates before your API response comes back. You need to ensure the field dependency mapping is configured to wait for the async response. Check your client script execution order.

7

Adding to what api_ninja_dev said - your API payload structure might be correct, but are you handling the response properly? The conditional logic triggers need to be explicitly fired after you receive the data. You should be using g_form.setValue() or g_form.setReadOnly() in the callback function to update the dependent fields. Also, make sure your REST message has proper error handling. Without seeing your callback code, it’s hard to pinpoint the exact issue, but the async nature of REST calls is almost always the culprit in these scenarios.