Rule Synopsis
These are the rule/s that control whether a User Oriented Attribute (such as Last Logged On User or Most Frequent User) is read and processed by CI Sync to set the Assigned_To or Most_Frequent_User against each windows computer CI record in ServiceNow.
Rule Details and Default
-
By default, CI Synchronizer does not process any form of User Oriented attribute between Lansweeper and ServiceNow.
Override Options
Context
Customers may consider overriding this rule so that the destination windows computer CI record in ServiceNow stores Assigned_To or Most_Frequent_User.
Options
-
This Data Sync Rule can be overridden so that CI Sync does process one or more User Oriented values.
-
The scope of this rule is limited to Windows Computer Assets in Lansweeper (as these only these are the only asset types Lansweeper captures Last Logged on details).
-
The persisted value will be a sys_id reference between the CI record and the corresponding record in the ServiceNow sys_user table.
-
For customers wishing to override this rule, further dialogue is required to confirm the specific correlation (matching) details between the source and destination attributes (i.e. to determine the customer specific content of the Last Logged on User values and how these can be correlated/matched to a specific sys_user attribute (such as sys_user.user_id, or sys_user.email, or sys_user.upn and so on).
-
The most common attributes used for this purpose are described below.
-
|
Lansweeper Value |
ServiceNow CI Attribute |
Additional Notes |
|---|---|---|
|
Last Logged on User |
Assigned_To |
The following ServiceNow attributes are sometimes used by customers (subject to their specific ServiceNow requirements): Attested_by, Managed_by, Owned_by and Supported_by. |
|
Most Frequently Logged on User |
Most_Frequent_User |
Lansweeper does not provide a Most Frequently Logged on User. Instead, Lansweeper retains a small history of the logged on users. CI Sync queries the history of logons to determine the most frequently (recent) logged on user. |
Overriding via Connection Settings
N/A
Additional Information
-
Syncfish requires formal customer approval before introducing this rule. Approval is required because introducing this rule means the customer CI Sync SaaS instance is transiting and persisting at least one attribute that may constitute Personal Data (PD) or Personally Identifiable Information (PII). The inclusion of such data may then trigger additional governance, compliance and contract changes between Syncfish and the customer business.
-
As each business determines their own logon value (email address, firstname + lastname, first initial + lastname, etc), it is the customer’s responsibility to assess the values contained in any User Oriented attributed processed by this rule. It is the customer’s responsibility to determine whether the values constitute Personal Data (PD), Personally Identifiable Information (PII) or other similar definitions.
-
Please also refer to Lansweeper On-Prem Example A - Lansweeper On-Prem User Oriented Attribute Processing Examples for a diagrammatic representation of this topic using several examples.
Related Rules
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: No (a plan is needed - see below)
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