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.

[Inactive_Us1180]

Hey Scott, we dont have a direct integration with DC in Epic, but all data Courier packages require a service now change ticket number on the Epic side. 

That way we can track where the original request and reason for the change. We fill out a change request from incidents, requests and even projects. 

Are you looking for a way for your analyst to submit work to a specific data courier person? 

[Scott Jordheim]

Thanks! Yea, in this case, we are trying to figure out what the best way to track work for each project. In our case, data courier moves are handled as requests, rather than large / small projects.

We use change requests in some cases as well, for instance if it is large enough to need approval. Otherwise, for most situations, it is the mover or requestor putting in a service request and letting the workflow drive most everything from there, and then a task going back to the reuqestor to verify move completion.

With the movers wanting to be able to do this from other tasks as well, this wouldn't really work well in its current form. We can have a UI action to automatically launch a request, but I'm not sure that is the way we want to go.

[Brian Nuernberg]

We track all data courier moves through change requests, no exceptions.  This become much simpler if you are using content management. We've automated task creation on change requests to streamline our overall epic release process. 

[ralphd]

Are you able to then validate that all Data Courier migrations were accompanied by a ServiceNow ticket?  We're looking for ways to confirm that is no undocumented build moving to PRD.