Data Courier Configuration in Servicenow for Epic?

[Scott Jordheim]

Hello, was wondering if anybody else is tracking Epic Data Courier work in ServiceNow. If you are, would you mind sharing how you are doing it? Right now, we are tracking this via catalog item / workflows, but are looking to improve upon the existing process if we can.

There are situations where we may need to start a data courier request from an incident in addition to a normal request process.

[Jonah Piascik]

@Brian Nuernberg - I'm also very interesting in learning more about the details of this integration.  Do you think would be something your group would be willing to share on the community for other organizations to be able to look at and possible leverage?  Perhaps in the form of a GitHub repo or Developer Share Project on deveoper.servicenow.com?

[Bill40]

Could you share the link or the presentation itself with me?  the other link didn't work.

This is something we'd love to have!

[BrianNuernberg]

Sorry for the delay in replying all, I've attached the presentation from K21. 

[anthonybrown]

@BrianNuernberg  I am not sure how much you know about the presentation details, but after reviewing it, do you know if the time saved is attributed to analysts no longer needing to create both an Epic Content Management ticket and Charge record in ServiceNow? Are the ServiceNow records getting created automatically using the APIs and scripting?

[BrianNuernberg]

We were already suing both content management and requiring analysts to create change records before the integration.  The integration saved time documenting the changes being made to records in the change.  All they had to do was link the CM ticket to the change, and the integration pulled in the details. It also allowed us to qucikly search change records for INI's and records to see who and when changes were made to those records.