|
|
System Jobs can run only active Data Scanners for the specified object.
|
|
Field
|
Value
|
|---|---|
|
Name
|
Enter a name that describes the purpose of the System Job.
|
|
Cron Expression
|
Define a cron expression to specify the time interval at which you want this System Job to run.
|
|
Operation
|
Click Data Scan System Job.
|
|
User
|
Click System Administrator.
|
|
Field
|
Value
|
|---|---|
|
Name
|
Enter a name that describes the purpose of the parameter.
|
|
Identifier
|
To run full scans with all Data Scanners for an object, enter object. To run full scans with a specific Data Scanner, enter an identifier.
|
|
Related System Job
|
This field is auto-populated with the name of the related System Job.
|
|
Parameter Datatype
|
Click Relationship,
|
|
Reference Field
|
• To run full scans with all Data Scanners of an object, click Object.
• To run full scans with a specific Data Scanner, click Data Scanner.
|
|
Parameter Value
|
Click the Data Scanner record you want to run, or select an object to run all its related Data Scanners.
|
|
|
• Multiple Data Scanners for a single object cannot run concurrently. When a Data Scanner configured for a specific object is running, and another Data Scanner configured for the same object is triggered, the newly triggered Data Scanner is placed in a queue and is triggered after the current execution is complete. This limitation applies to Data Scanners that are triggered manually or automatically by System Jobs, but does not impact automatic scans triggered by record updates.
• The number of Data Scanners for multiple objects that can run concurrently is configured in the Maximum Concurrently Processing Data Scanners field in the active System Setting record. When the number of currently running Data Scanners reaches this limit, newly triggered Data Scanners are placed in a queue and triggered after the number of current executions falls below the configured maximum. This limitation applies to Data Scanners that are triggered manually or automatically by System Jobs, but does not impact automatic scans triggered by record updates.
|