The first time an incremental load job runs to capture change data for a ServiceNow source, the job retrieves and loads only the change records that are created after the date and time specified in the associated ingestion task. You can specify the date and time when you configure the source in the

application ingestion and replication

task wizard. However, when you resume a stopped or aborted job, the job begins propagating change data from where it last left off.

The data stored in some ServiceNow objects can be retrieved only if the API client is configured with the maint and nobody roles.

Application Ingestion and Replication

does not retrieve data from such source objects that require the ServiceNow Mass Ingestion connection to be configured with the maint and nobody roles.

You must have Admin privileges to access table APIs or aggregate APIs.

Incremental load jobs configured for ServiceNow sources do not capture change data for the objects that do not contain the sys_updated_on field.

Incremental load jobs and combined initial and incremental load jobs configured for ServiceNow sources do not detect and replicate the renaming of source fields.

Application Ingestion and Replication

retains the masking configuration of source fields on the target. For example, if a masked field on the source contains the value 1234****, the corresponding field on the target also contains the value 1234****.

In the Secure Agent configuration properties, set the

metadata_manager.jvm.ai.servicenow.enable.cdc.using.inherited.columns

and

task_container.jvm.ai.servicenow.enable.cdc.using.inherited.columns

custom properties to

true

to include the child tables inheriting CDC columns from the parent table in the task.

Set the

ai.servicenow.enable.additional.datatypes

custom property to

true

, to enable the following ServiceNow data types:

Audio
Basic Image
Encrypted Text
FX Currency
Image
Journal List
List
Name-Value Pairs
Reference
Video
Wiki