- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Do you maintain ETL jobs just to show external data in a catalog form?
This demo shows another way, using the Workflow Data Fabric Zero Copy Connector.
I connect a Microsoft SQL Server table (hosted on Azure) to ServiceNow as a Data Fabric table. A Sales request catalog item in Employee Center then reads it live. Nothing is copied into ServiceNow, so the list is always current.
In this video:
The use case: why ETL imports for catalog forms get expensive and go stale
Live SQL queries from the form, watched on the SQL Server as they happen
Showing extra fields on selection with a client script and a GlideAjax script include
The risk: the source row can change or disappear after the request is submitted
The fix: a snapshot of the key fields stored on the request item at submit, using a business rule
Setting up the connection, the Data Fabric table and the catalog item Data Fabric tables are read-only, and each lookup is a SQL query pushed down to the source, so expect a little latency.
The snapshot is one design option, not the only one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.