topic Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator in Workato Pros Discussion Board

Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

mroldanvega — Fri, 15 Oct 2021 18:57:07 GMT

Hi Workato Team,

2 suggestions for new features:

1. It would be very useful if we could export the dependency graph to excel or CSV. One use case is: I want a list of all the recipes that are connected to Salesforce. I can see them in the graph, but I cannot export them (to use them as a checklist or so).

2. Another feature that would be helpful: in the dependency graph, if you can show (maybe with an icon) the type of trigger the recipe has (callable, scheuler, teams, webhook) it would be easier to identify the if a recipe is relevant or not to the search you're performing.

Tridivesh Sarangi - maybe you ca forward this to the relevant folks. Thanks!

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

steven-marissen — Fri, 15 Oct 2021 19:17:13 GMT

Additional idea to point 2: I would be very handy to see in the dependency graph whether a callable recipe is synchronous or asynchr (+ that option to wait for asynch to finish).

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

tridivesh — Fri, 15 Oct 2021 21:28:27 GMT

Manuel Roldan-Vega - Thanks for sharing the use cases and suggestions. In the example you shared i.e. listing recipes connected to Salesforce, can you share how that list will be used? Is it for audit purposes, or for analyzing the impact in case changes to the Salesforce connection was made? I can see similar requirements for callable recipes/lookup tables or any resource that has multiple dependencies.

Also curious, what additional benefits do you see by creating an export of the dependency graph? We have heard some customers wanting to import this data into their existing data lineage repositories.

Nishtha Mehrotra - FYI

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

mroldanvega — Fri, 15 Oct 2021 21:44:00 GMT

Hi Tridi,

You're absolutely right. All of the above.

Impact analysis would be our primary use case. Not only for connections, but recipes, callables, lookup tables, and any other resource.

I can see how it could also be used for lineage too. For that use case i think we would need additional metadata at the recipe level, like objects (at least), otherwise i am not sure if it would be very helpful.

If you're going in this direction, please also keep in mind a Dependency API. That would be very useful to automate the w*rk out ot these two use cases. 😉

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

deven-maru — Fri, 15 Oct 2021 22:28:20 GMT

Thanks Manuel Roldan-Vega. We have several enhancements lined up for dependency graph. Like Tridi said, we have heard requests about exporting the dependency graph. It's in the backlog at this moment. We will explore what the best export format should be. But thanks for the details on the use cases. Maybe we can have a session on the enhancements to the dependency graph with you when we have it in preview.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

deven-maru — Fri, 15 Oct 2021 22:48:42 GMT

Steven Marissens that's a good suggestion. Let me see how we can add it to the UI.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

mroldanvega — Sat, 16 Oct 2021 00:02:25 GMT

Would love to. Keep me posted.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

bud — Sat, 16 Oct 2021 12:31:02 GMT

Both good suggestions. I agree.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

steven-marissen — Mon, 18 Oct 2021 15:00:30 GMT

Did some more thinking about this during the weekend, could be a nice usecase for using Neo4J. Could easily give insights to relationships / attributes, not to mention via a connector to keep everything updated.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

mroldanvega — Mon, 18 Oct 2021 17:05:06 GMT

Yes, precisely Steven Marissens . Up until today, we're using the APIs to extract and build these dependencies manually, but it would be so much better if we could export them from the dependency graph.

Curious - are you already using neo4j? Would love to hear more about it.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

steven-marissen — Mon, 18 Oct 2021 21:26:59 GMT

I have used Neo4J for customer relation analysis / tracking but not for Workato. It's doable but would require quite a lot of effort to keep it updated with no 'live' updates coming from Workato so far. You could use it as a separate version of the truth and add your own metadata but that also has its disadvantages.

Personally I think it would be superb if you could stream a live feed from Workato to Neo4J but then again adding your own custom metadata could be overwritten.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

deven-maru — Tue, 19 Oct 2021 02:13:08 GMT

Steven Marissens that's interesting. The idea to push changes to keep the graph updated may be a little tricky as there could be many interconnected dependencies.

Re: Enhancement: Export/Print Dependency Graph and Trigger Type Indicator

mroldanvega — Tue, 19 Oct 2021 02:21:52 GMT

This is part of the reason I mentioned an dependency graph API, Deven Maru. Then we can update it programmatically.