Rule Synopsis
These are the rule/s that control whether CI Sync updates the first_discovered attributes on each record during CI Insert and CI Update Operations, or only on CI Insert Operations.
Rule Details and Default
-
By default, CI Sync does update the first_discovered attribute on both CI Insert and CI Update Operations.
Override Options
Context
Customers may consider overriding the default rule to have CI Sync only update the first_discovered attribute on CI Insert operations.
Override
-
The rule can be amended so that CI Sync only updates the first_discovered attribute on CI Insert operations.
Overriding via Connection Settings
Also, customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:
-
For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.
-
For the specific CI Sync Connection Setting/s related to the rule described on this page please read Update First Seen (Discovered) on Update of CIs in ServiceNow.
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
The first_discovered field is only applicable/mapped for the following source systems:
-
Microsoft Defender for Endpoint
-
InTune
-
JAMF
-
Lansweeper On-Prem
-
Lansweeper Cloud
-
Omnissa Workspace ONE
Related Rules
N/A
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: Yes (via self-service in the CI Sync UI)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Bronze Plan, Silver Plan or Gold Plan (for customers wanting Syncfish assistance to perform overrides of this rule)