Skip to main content

ServiceNow - "Service Graph Data Visualizer" and "IntegrationHub ETL"

 as part of the Service Graph 

references:

https://store.servicenow.com/sn_appstore_store.do#!/store/application/d43fe173dba23300c121f3c61d961958/2.2.1

https://store.servicenow.com/sn_appstore_store.do#!/store/application/1e6f4587c73600109cea1197fdc26062/1.1.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate&q%3Ddata%2520visualizer&sl=sh 

 

IntegrationHub ETL

Summary

ServiceNow CMDB is a single system of record which can maintain all configuration data related to a given infrastructure. An accurate and reliable CMDB is required for every successful ServiceNow implementation whether it be IT Service Management, IT Operations Management, IT Business Management, or Security Operations.

IntegrationHub ETL (IH-ETL) is a UI based tool that offers an easy to use interface to Extract, Transform and Load data from third-party data sources into the CMDB. 

IH-ETL uses Concurrent Import Sets, Robust Transform Engine (RTE), and Identification and Reconciliation Engine (IRE) to ensure:

  • Efficient import of data
  • Mapping of complex, hierarchical data sets to appropriate CI classes
  • Data stored in CMDB is aligned with the appropriate data model, and appropriate relationships between data entities are automatically created 
Key Features

IntegrationHub ETL (IH-ETL) is intended to be used by developers who are creating new integrations, as well as by CMDB Administrators who manage and fine-tune existing integrations. Some operation types supported in the UI require more advanced users (for example, creating a Script operation).

Feature highlights:

IH-ETL provides a wizard-style user experience that allows users to do the following:

  • Import source data.
  • Preview third-party source data and prepare it for mapping to CMDB classes and attributes.
  • Choose target classes in the CMDB to which to map source data, and add relationships among these classes.
  • Preview sample integration results and schedule imports.
  • Perform rollback if the results of the preview are not satisfactory.
  • Ability to Activate/Deactivate mappings to prevent a class from being populated during the integration run, while preserving all of its mapping configuration.

 

Service Graph Data Visualizer
Visualize data transformation and mapping in Service Graph Connectors
ServiceNow
Compatibility: San Diego, Rome, Quebec | Other App Versions
Automatically entitled on all ServiceNow instances and all ServiceNow developer portal instances

 

Summary

The Service Graph Data Visualizer is a tool that can be used to get a visual representation of the data transformations and mappings that are configured in a Service Graph connector. It enables you to see how the input fields from source data are processed and mapped to the target entities in the CMDB

Key Features

Getting multiple views of the data mapping and transformation including:

  • See how any output field is mapped
  • See how input fields are used
  • See all the mapping and transformation associated with a target entity
  • Specify values for input fields and preview the results of the transformation on that data.

In addition, you have the ability to create either an SVG or a PNG of the resulting visualization.

 

Comments

Popular posts from this blog

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){