When to use Data Source / Transforms instead of Flow Designer/Integration Hub

[marclindsay]

With integrations we have in place we have been using Data Source and Transformations for importing data from an external database.  We are now purchasing Integration Hub. 

Trying to figure out, When is it better to use Flow Designer with Integration Hub versus just using a Data Source and Transformation (import set) ? I have been looking for some Best practice to help define when each method would be better to use. 

Any information on the difference here would be appreciated. 

Thanks Marc..... 

[Sukraj Raikhraj]

Depends on the requirements, Integration hub helps with integration and web service or  with third parties.   software .  Depending with the subscription level, there are many OOB functionalities that comes with IntegrationHub that could easily be added to FLOW.  Most likely importset and data transformation is here to stay .

[surajp]

Hi Marc,

You can use Rest(integrationhub) type data source action - https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/import-sets/task/create-rest-type-data-source.html This way you would use integratedhub action to call third party api.

If you are planning to upgrade to Rome, you could use Integratedhub imports which is modern interface to configure data source & import set. https://docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/integrationhub/concept/integrationhub-imports.html

If you still not planned for Rome, if you still want to use flow designer and integration hub to import data. you could get the store app developed by Servicenow called Enterprise Service Management Integration framework which has several best practices for importing data into any SN table, which only requires to setup services with details like staging table, service flow that calls the action to fetch data and create records in staging table. The framework handles the task of creating import set, transform import sets and closing import set etc. Has the capabilities to configure full load, delta load, page count and track the jobs etc This is very well though framework to importing data into SN where you could configure all your integrations in one place. Also supports making outbound calls. https://store.servicenow.com/sn_appstore_store.do#!/store/application/08ca765153ed5010a86dddeeff7b1277/3.3.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3DEnterprise&sl=sh

Regards,

Suraj

[marclindsay]

Thank you for this additional information. But that doesn't quite answer my question. 

Right now I could use Flow Designer & IntegrationHub to do what you are describing above. Though an alternative would be to just create a Data Source, Transform, and Scheduled Job. 

My question is more centered around scenarios or best practice as to when to use the Flow Designer & IntegrationHub solution versus just using a Data Source/Transform/Scheduled Job solution.  Trying to determine when best to use these two different solutions ?

For instance (one example) should Data Source/Transformer/Scheduled Job only be used for easy or one-time imports. Whereas the Flow Designer / IntegrationHub solution should be used for repeatable, complex transformations.  Just looking if anyone knows of any best practice around when to use these two different import/integration options ? 

Thanks

Marc......

[surajp · Accepted solution]

Hi Marc,

I understand there are many options available at the moment to load data. Data source, transform map and scheduled job is still the preferred way to import data and this is not going away soon. SN still supports this methodology as we see new feature called integrationhub imports in rome. But integrationhub/flow designer is the future to build integrations as we see many Store apps integrations are built on flows/action instead of data source. If you want to take advantage of all the new features coming in future releases for flow/integrationhub and make your integrations maintainable by non developers then low code no code is the best way.

Regards,

Suraj