Targeting custom tables

You can target custom tables in ServiceNow with a configuration file written in KVGroup format as illustrated below:

# KVGROUP-V2.0
   #
   # Sample configuration file for agtsvcnow.
   #
   "agtsvcnow" "node" = {
        "user" "u_bravura_user_profiles" = {
            "user_name" = "u_profile_id";
            "first_name" = "u_first_name";
            "last_name" = "u_last_name";
            };
        "group" "u_bravura_grp" = {
            "name" = "u_groupid";
            "description" = "u_groupname";
            };
        "grpmbr" "u_bravura_grpmbr" = {
            "group" = "u_groupid";
            "user" = "u_userid";
            };
        "asset" "u_bravura_compsvr" = {
            "ID" = "asset_tag";
            "name" = "display_name";
            "status" = "install_status";
            "disabled" = "1";
            "deleted" = "0";
            "getall" = "true";
            "sysparm_query"="asset_tagISNOTEMPTY";
            };
   };

The configuration file describes the mapping between the custom table and the built-in sys_user table from which the connector pulls users’ information with default behaviour.

The file maps the default user_name, first_name, last_name columns from sys_user to columns in a custom table. The "group" KVGroup should contain "name", "description" mapping. The "grpmbr" KVGroup should contain "group", "user" mapping if any of them are to be listed from a custom table. If empty, the information will be pulled from the system built-in tables. In addition, the "asset" KVGroup can be used to list any available computer server objects from a custom table.

By default, groupid is mapped to sys_id in the built-in table, which may result in empty group members. If you encounter this, add the following line to "grpmbr" to list all custom group members:

"group_is_sysid"="false";

The configuration file can be placed anywhere. The default path is the <Program Files path>\Bravura Security\Bravura Security Fabric\<instance>\ script\ directory.