Hey UiPath team,
My dev team and I would love to see a feature in Studio that gives a single place to view all the external connections and dependencies used in a project, and some adjustments to how connections are set, which would allow for integration service based custom activities.
We’d also like the ability to give a description for each connection used. There seems to be a description field in the project deployment tool, but there is no real way to update it.
Right now, in larger automations, connections are scattered everywhere, and it becomes really hard to quickly understand how many different connections you have for each connection type. This leads to unknown connection mappings when setting the connection value in orchestrator.
This gets especially painful when moving a project from Dev to Prod using project deployment. You often have to manually cross-reference what each connection actually is in Dev just to make sure you’re mapping everything correctly in Prod. It’s easy to lose track of what a connection was originally intended for. A feature where you can update the connection description on the project level would solve for all the above.
What I’m suggesting for ‘Connections’ panel improvements:
- Global view for all connections used
- Description field support (eg. Connection used for sending run report emails to Accounting)
- A 3 dot button for each connection that pops up the locations of all activities used with that connection, allowing you to click and jump to that workflow
- Ability to change the connection on a project level across all activities
- Flag unused or orphaned connections
- BIG LIFT - set connection objects in the connection panel so you can set the connection dynamically for all integration service activities, allowing you to build custom activities with integration service
My point on the BIG LIFT would be especially helpful, since it is currently not possible to build library activities with integration service, since you would have to use the same connection every time if you did.
Basically, just a clean “what systems does this automation actually connect to, and what is each one for?” view.
This would solve all the bigger shortfalls of integration service. I know this might be a bigger lift, but we believe this would send the benefits of integration service over the top.
Thanks for your consideration!