ConfigBot for ServiceNow - Tables Management

The ConfigBot for ServiceNow Table Management Module enables users to efficiently create and modify fields within any ServiceNow tables. This module allows users to add new or pre-existing fields directly within the Form Layout using the view and section hierarchy, eliminating the need to navigate between multiple screens and enabling faster actions.


Additionally, the module provides a seamless way to compare differences between instances without manual effort. Users can also add fields to the List Layout and easily identify any discrepancies across multiple instances. 


Designed for scalability and control, Table Management helps administrators maintain consistent table structures, form and list configurations, field behavior, and workspace experiences while reducing manual configuration effort and improving configuration accuracy.


The following article explains how to use the Table Management module in ConfigBot to perform different operations.


Step 1: Log in to ConfigBot


Enter your username and password, then click Submit to access the portal.



Step 2: Access the Table Management Module 


From the Home Screen, navigate to Platform and click on the Table Management module tile.



Step 3: Create a New Iteration 


Click the Add New Iteration button.




  • Enter the Iteration Number.
  • Select the Workspace or Add New Workspace.
  • Enter the Host Address.
  • Choose the Instance Type.
  • Enter your Company ID and Username.
  • Add a short Description.



After filling in all required details, click Submit to create your iteration.


Reverse (Fetch Configuration from ServiceNow)


Step 1: Set the Filter Configuration 


Once the iteration is created, open the workbook.



Select the Required Filter Configuration.


Navigate to the Config Sheet, and configure filter criteria to backfill the records.


When Dependent is Set to = No, other columns will be auto populated on the basis of selected module in column E.



Note: All columns will auto populated with selected module table , except the Column J "View Name" & Column N "Agent Workspace List Name", You have to define these columns manually.


Here you can see, as i selected the CSM Module in column E.



These columns are auto populated with the respective module tables along with Fetch Only filter criteria.



However, you have to manually select the filter type for Views and Workspaces screen, as I select fetch all for these columns.



These Config filter criteria retrieves all applicable records from the ServiceNow instance.


You can also select other filter types based on your specific need:

  • Fetch All: Fetches all records from the ServiceNow instance.
  • Fetch All, except these: Fetches all records except those specified in the next column.
  • Fetch Only: Fetches only the records specified in the next column.
  • Fetch Active Only: Fetches only active records.
  • Fetch In Active Only: Fetches only inactive records.
  • Fetch By Query: Fetches only records that match the configured query.


You can also use the Dependent functionality by selecting “Yes” in Column B, “Dependent.”

  • Module: Select the required module from Column E. The bot will use the selected module table as the basis for fetching the associated records.
  • Application Scope: Define the required Application Scope to narrow down the data retrieval. The bot will first identify the tables available within the specified application scope and then fetch the records associated with those tables.




Dependency Relationships


The Table Management module supports dependent configuration relationships to ensure that related records are fetched according to their parent configurations.


  • Views → Records are fetched based on the selected module and application scope.
  • List Layout Records are fetched based on the selected module and application scope.
  • List Element Records are fetched based on the related List Layout records.
  • Form Section Records are fetched based on the selected module and application scope.
  • Form Element Records are fetched based on the related Form Section records.
  • Field Management Records are fetched based on the selected module and application scope.
  • Dictionary Override Records are fetched based on the selected module and application scope.
  • Agent Workspace Records are fetched based on the selected module and application scope.


The exact dependency behavior depends on the configuration selected in the Config Sheet.


Step 2: Generate Workbook 


Once the iteration is created and the filter configuration is completed, Go back to your workspace and click on the Hamburger Menu and select Generate Workbook.



In the pop-up window:

  • Enter your ServiceNow password.
  • Add any Execution Notes.
  • Under Advanced Options, select the required checkboxes to generate the desired sheets.
  • Click Confirm and Start to process the execution.



This step prepares the workbook with the configured Table Management sheets and backfills the configuration data from the ServiceNow instance.


Step 3: Review Results 


Once the execution status changes to Complete, open the generated workbook.



The workbook will be populated with the configuration data retrieved from the ServiceNow instance across the supported sheets:



You can review the backfilled configuration data and use it as the baseline for further validation, automation, or comparison activities.


Automation (Configure Records using ConfigBot)


Step 1: Open Generated Workbook


  • Click on sheet icon to open generated workbook 
  • Navigate to the desired Sheet (Views, List Layout, List Element, Form Section, Form Element, Field Management, Dictionary Override, and Agent Workspace): 
  • Create and update the records. 


To Start Configuration for Automation:


You can modify existing records or add new configuration records directly within the workbook.


Step 1: For list configurations, configure the required Views, List Layout, and List Element records.


Create View. Fill in the required fields such as Title, Name, and other mandatory details to create a valid View record.



Create List Layout. Fill in the required fields such as Table, List View, and other mandatory details to create a valid List Layout record.


Note: you can select you recent created view from the highlighted column dropdown.



Create List Element. Fill in the required fields such as Table, List View, and other mandatory details to create a valid List Element record.


Note: Column H "List ID" is mandatory, you have to fill it manually once the list layout created, copy the Processing ID of List Layout and paste in the Column H.



Step 2: For form configurations, configure the required Form Section and Form Element records.


Create Form Section. Fill in the required fields such as Table, View, and other mandatory details to create a valid Form Section record.



Create Form Element. Fill in the required fields such as Table, View, and Section, and other mandatory details to create a valid Form Element record.


Note: You can select you recent created Form Section from the highlighted column dropdown.



Step 3: For field-related configurations, configure the required Field Management and Dictionary Override records.


Create a Field. Fill in the required fields such as Table, Name, Value, and Field Type, and other mandatory details to create a valid Form Element record.



Create Dictionary Override. Fill in the required fields such as Table, Name, Value, and other mandatory details to create a valid Dictionary Override record.



Step 4: Configure the required Agent Workspace records where applicable.



Step 5: Finally, navigate to the Config sheet. Set Maintain Update Set to Yes and enter the desired Update Set Name to capture your configurations. 



Note: Make sure to set the Processing Status of each record to Pending before running automation.


Step 2: Start Configuration 


Once your configuration data is set:

  • Return to your Workspace.
  • Click the Hamburger Menu and select Request Reprocess.



  • Click the Hamburger Menu again and select Start Configuration.



In the pop-up window:

  • Enter your ServiceNow password.
  • Add any Execution Notes.
  • Select the Advanced Options corresponding to the sheets you configured.
  • Click Confirm and Start to execute the configuration.



Note: Select the checkboxes according to the Table Management configurations you want to automate.


Step 3: Result Overview


You can click the Information Logs (🛈) icon on your iteration to monitor the processing status and execution logs in real time.




Once List Layout is configured



Navigate to sheet and copy the Processed Record ID of List Layout.



Then navigate to List Element sheet and paste the id in the List ID column.



Once the execution is Complete, navigate to the workbook to review the results.



You will notice highlights across multiple tabs:

  • Green Highlights → Indicate matching configuration values between the sheet and the ServiceNow instance, confirming that no configuration differences have been identified.
  • Red Highlights → Indicate configuration differences between the values currently maintained in the sheet and those available in the ServiceNow instance. These highlights identify configurations where changes have been detected or where the sheet and instance are not aligned.


Validation (Validate Configuration Changes from the Sheet)


Step 1: Open Generated Workbook


Click on the Sheet Icon to open the generated workbook.



Step 2: Change the status to Pending 


Navigate to the desired Table Management sheet for which you want to validate the configuration.
Change the Processing Status to “Pending".



Step 3: Start Execution (Validation) 


Once the Processing Status is set to Pending, close the workbook and navigate back to the Workspace.
Click on the Hamburger Menu and select Request Reprocess.



Click on the Hamburger Menu one more time and select Start Validation.



In the pop-up window:

  • Enter your ServiceNow instance password.
  • Add any Execution Notes.
  • Select the checkbox for the desired Table Management sheet.
  • Click Confirm and Start to begin validation.



Step 4: Review Results 


Once the execution status changes to Complete.



Open the generated workbook, Review the validation results across the selected Table Management sheet.



You will notice highlights across multiple tabs:

  • Red Highlights → Indicate configuration differences between the values maintained in the workbook and those currently available in the ServiceNow instance.
  • Green Highlights → Indicate matching configuration values between the workbook and the ServiceNow instance.


These results allow you to quickly identify which table configurations remain aligned and which configurations require attention.


Compare (Compare Between Two Executions)


Step 1: Should have two Generated Workbooks 


Ensure that you have two generated workbooks/executions available for comparison.
The workbooks can represent configurations from different ServiceNow instances or different executions of the same instance.



Step 2: Start Execution (Compare): 


Click on the Hamburger Menu and select Request Reprocess.



Click on the Hamburger Menu one more time and select Compare Iteration.



In the pop-up window:

  • Select the iteration you want to compare against.
  • Click Confirm and Start to begin the comparison process.



Once the execution status shows Complete.



Open the workbook and navigate through the Table Management sheets to review the configuration differences.



You can notice highlights across multiple tabs:

  • Red Highlights → Indicate configuration differences between the two iterations.
  • Green Highlights → Indicate matching configuration values across both iterations.


These color-coded results allow you to quickly identify what has changed and what remains consistent between the two ServiceNow configurations.


You can also navigate to the Compare Summary sheet to review the identified differences.



The Compare Summary provides a consolidated view of the comparison results, allowing you to quickly identify configuration changes across the supported Table Management components without manually reviewing every record in each sheet.


This provides a quick and reliable way to verify configuration consistency between two executions and identify table-related configurations that may require synchronization or further review


Thank You.

Updated on: 09/12/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!