Romannyschuk a11y servicenow connector #480
Conversation
- Add how to verify that the discovery source of “Device42” was created. - Add how to create the relationship so that we can use IRE to create database CIs. This would only be needed if the app doesn’t automatically create the relationship. - Add that scheduled imports have a default schedule that the customer can modify to meet their needs. - ServiceNow only supports the three most recent releases. Remove sections for “Version 2.0.1 (or previous).” Consider adding a note that Servicenow only supports the three most recent releases to forestall questions to Support.
|  | ||
|
|
||
| 2. Add **Device42** to the data source choice list. Navigate to **System Definition > Scripts – Background** (search for it under **All**) and paste in the following script. Leave **in scope** as **global. | ||
| 2. Add **Device42** to the data source choice list. Navigate to **System Definition > Scripts – Background** (search for it under **All**) and paste in the following script. Leave **in scope** as **global**. |
There was a problem hiding this comment.
This should come after verifying the discovery source and only needs to be run if it does not exist.
There was a problem hiding this comment.
This paragraph replaced with 2.
| if (gr.hasNext()) { | ||
| gs.info('Device42 found'); | ||
| } else { | ||
| gs.info('Device42 did not find'); |
| :::caution | ||
| The following information is accurate for the Washington DC and Vancouver versions of ServiceNow and may not work completely as expected for Xanadu. The approach laid out below is still relevant, but some details may differ. | ||
| The following information is accurate for the recent versions of ServiceNow. The approach laid out below is still relevant, but some details may differ. |
There was a problem hiding this comment.
Remove The approach laid out below is still relevant, but some details may differ..
|  | ||
|
|
||
| These can be scheduled to run at certain times and should be run in the highlighted order: Devices, IPs, Services, Software Details (version 2.0.1), and Software Instances. You can click on an individual schedule to edit it or to **Execute Now**. | ||
| These can be scheduled to run at certain times and should be run in the highlighted order: Devices, IPs, Services, and Software Instances. You can click on an individual schedule to change running order , period and time. And then you can **Execute Now**. |
There was a problem hiding this comment.
Add the new items that we added.
There was a problem hiding this comment.
Affinity Group, Application Components, Business Applications, Database, Database to Instances, D42-Web-Sites, Web Site, Devices, IPs, Services, and Software Instances
| Please note that all records will appear to be ignored in versions 3+, because we use the Identification and Reconciliation Engine (IRE). | ||
| **Direct Connection (3.0.0+ Only)** | ||
| Direct Connection |
There was a problem hiding this comment.
There are other places that reference 3.0.0 that need to be removed.
There was a problem hiding this comment.
Removed all.
|
|
||
|  | ||
|
|
||
| ## Adding the Relationship |
There was a problem hiding this comment.
Check if the relationship exists and if it does not add it.
There was a problem hiding this comment.
I replaced sentence with one above
| if (gr.hasNext()) { | ||
| gs.info('Device42 found'); | ||
| } else { | ||
| gs.info('Device42 did not find'); |
There was a problem hiding this comment.
You will need to update the screenshot too.
There was a problem hiding this comment.
/assets/images/device42-servicenow-connector/the-script-find.png
| - Username: You may use any value here, but it is required. | ||
| - Password : `${x_192652_device42.instance_key}` | ||
| Please note that all records will appear to be ignored in versions 3+, because we use the Identification and Reconciliation Engine (IRE). |
There was a problem hiding this comment.
All removed.
- fix all task
| if (gr.hasNext()) { | ||
| gs.info('Device42 found'); | ||
| } else { | ||
| gs.info('Device42 not find'); |
There was a problem hiding this comment.
Change "find" to "found" and update the screenshot too.
| The scheduled imports first run the respective data source to collect and store data in the import set tables for a given data source. After this data has been imported into this table a transform script is run to map the data into ServiceNow's internal tables. Version 3.0.0+ of the ServiceNow integration plugin leverages ServiceNow's IRE module. For more information on this feature, please visit ServiceNow's documentation page: | ||
| The scheduled imports first run the respective data source to collect and store data in the import set tables for a given data source. After this data has been imported into this table a transform script is run to map the data into ServiceNow's internal tables. ServiceNow integration plugin leverages ServiceNow's IRE module. For more information on this feature, please visit ServiceNow's documentation page: | ||
|
|
||
| [https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/c_CMDBIdentifyandReconcile.html](https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/concept/c_CMDBIdentifyandReconcile.html) |
There was a problem hiding this comment.
|  | ||
|
|
||
| The scheduled imports first run the respective data source to collect and store data in the import set tables for a given data source. After this data has been imported into this table a transform script is run to map the data into ServiceNow's internal tables. Version 3.0.0+ of the ServiceNow integration plugin leverages ServiceNow's IRE module. For more information on this feature, please visit ServiceNow's documentation page: | ||
| The scheduled imports first run the respective data source to collect and store data in the import set tables for a given data source. After this data has been imported into this table a transform script is run to map the data into ServiceNow's internal tables. ServiceNow integration plugin leverages ServiceNow's IRE module. For more information on this feature, please visit ServiceNow's documentation page: |
There was a problem hiding this comment.
Add "The" before "ServiceNow integration plugin leverages...".
|  | ||
|
|
||
| These can be scheduled to run at certain times and should be run in the highlighted order: Devices, IPs, Services, Software Details (version 2.0.1), and Software Instances. You can click on an individual schedule to edit it or to **Execute Now**. | ||
| These can be scheduled to run at certain times and should be run in the highlighted order: Affinity Group, Application Components, Business Applications, Database, Database to Instances, D42-Web-Sites, Web Site, Devices, IPs, Services, and Software Instances. You can click on an individual schedule to change running order , period and time. And then you can **Execute Now**. |
There was a problem hiding this comment.
Replace this paragraph with:
The Device scheduled job is set to run at a default time which can be modified if needed. The Device scheduled job will automatically trigger the next scheduled job to run, which will then trigger the next scheduled job, and so on until all of the scheduled jobs are run. The order the scheduled jobs will run is: Device, IP, Software, Service, Affinity Group, Application Component, Business Application, Database, Database Instance, Database to Instance, Website. You can click on the Device scheduled job to change period and time. And then you can **Execute Now**.
|
Approved |
|
@Nadia-JSch Can you get this one through. Thanks. |
4 participants
Consider adding a note that Servicenow only supports the three most recent releases to forestall questions to Support.