It has always been easy to create, authenticate and manage connections in Integration Service.
Now it’s just as easy to share and govern your Integration Service connections across individual users and groups within your organization. Connection Sharing allows customers to quickly deploy and govern the API-based processes their automations require.
The new Connection Sharing feature allows customers to:
Create, manage, and govern system connections in specific, sharable folders
Share connections with individual, groups, attended, or unattended executions and robots
Manage connections through UiPath Assistant, Apps, Studio, and Studio Web by reusing Orchestrator’s folder structure and permission management
Granularly maintain connection authorization control across users, folders, and folder connection contents
We recommend attending the upcoming live Community webinars for "Power and govern API-based connection sharing across UiPath Business Automation Platform”.
This is a great update! The UiPath Integration Service was really lacking in this regard, but now it is a whole lot easier to use more integrations with numerous robots / users / etc. Great work, guys and gals!
@Charlie_Greenberg, this update has an issue. I published a package to Orchestrator via Studio, and that worked fine. But when I go to create a process in a folder, I get an error “An error occurred.” and I am not able to create a new process.
I found the solution was to click the “Configurable by users” in the “2. Package Requirements” page of creating the process for each of the Connections, and then I was able to create the process as required.
But there appears to be an issue if you just leave it as one of the “Shared” or “Personal Workspace Connections”.
Anyway, this feature is a great improvement but it still has some bugs in Orchestrator…
@Senne_Symons, yep, I am able to use Integration Service connections with my unattended robots!
HOW TO FIX:
You need to choose the “Configurable by users” in order to get Connections working properly. Otherwise you can’t create a new process.
Hi, Can you please confirm what connections you used at the time of the package build in the studio? Did you use connections from your personal workspace (Mu Workspace) or Shared workspace?
And when you said 'Create a process in a folder - can you please guide me on which page you are on to create a process?
I submitted a ticket to UiPath about this but haven’t heard back yet. I have UiPath Studio Enterprise (am a paying customer) and Studio Enterprise.
Sure, I used a shared connection (at least I think it is shared) and not a personal one. The connection is not one in my own personal workspace, it is in a folder within Integration Service.
To create the connection, I went into the Integration Service portal, navigated to the folder in question (not my workspace), and created two new connections for Microsoft Office 365. I authenticated and everything worked fine to add the two connections.
Everything works fine in Studio, it was just when I went to create a process in Orchestrator that the issue came up and would prevent me from creating the process.
To create the process in a folder, I opened Orchestrator and went to the folder in question (which is the same folder as the one in Integration Service). I clicked the “Automations” tab, and arrived in the “Processes” sub-tab. Then I clicked “Add process” and chose the Studio project I built. I didn’t change anything in the Package Requirements tab, nor in the additional settings tab.
And following those steps, I would always encounter the error: “An error has occurred” popup. And the process would not be created.
But if I changed the connection settings in the package requirements page of the “Add process” action to “Configurable by user” I was able to add the process and it worked just fine in Orchestrator with the correct connection.
Hopefully that helps, if you need more detail just let me know.
Hello, I tried to repro this, and I am unable to hit the error.
one more question - When you are on the ‘package requirement’ tab, what do you see in the dropdown for the connections? and what connectors did you use for your package?
I noticed that the integration service connection from the Google Workspace package 2.x don’t show in the Package Requirements tab package version 1.16 does show the connections. This results in not being able to use the integration service for Google activities like Use Google Drive and Use Google Spreadsheet. In addition, in studio only the connections from “my workspace” are visible and not from other folders. This needs a fix.
I found this studio issue true for Studio Enterprise version 2022.10.4 - tried with Activities package 2.1.2 and the connections from shared folder are not visible (the one’s from “my workspace” works well)
What’s interesting I also tried this on Community Studio (version 2023.4.0) with the same activity package version and here it seems to be working for both “my workspace” and shared folders. Strange it works for community and doesn’t work for Enterprise.
Did you find any info on how to tackle this issue?
I think the issue is in the UiPath.Platform[23.4.0] dependency version. Your Studio/Robot is in Platform 2022.10.x, but the activity is for Studio 2023.4.x.
You will need to try version Google Workspace[1.16.2] which is suited for UiPath.Platform 2022.4.0 and up.
Thanks!
Looks like you might be right.
I just used the classic activities with Service Account JSON authorization (instead of Service Integration) with package 2.2.0 - for my purposes it worked just fine.
It would be great thought if the newer version of google workspace would also be compatible with studio 2022.10.x - do you know if somebody is working on it?
I was testing this today and it is indeed a great improvement over some of the ‘classic’ activities however there is still a critical issue for unattended automations.
We have a setup where we have 3 tenants. Development, Acceptance and Production.
In this setup we are unable to use the integration service because, if we make the activity in Development, the connection it uses is then not available to run the robot in Acceptance or Production.
I believe this can easily be fixed.
I propose you allow us to choose the design time connection ID via the current dropdown and the runtime connection ID can be set via a variable, if runtime is left blank the design time connection is used. With this option I can then dynamically choose a connection ID, perhaps based on an asset, so if I run on other tenants the code still works as desired.
This functionality appears to have been broken in 2023.4.2 release that I was forced to install today. While I can see the folders in my notification/status bar (lower right in the blue bar in Studio), the available connections in any shared folder no longer appear when I try to select them from the drop down from a related activity.
@steve.meadows , @marian.platonov
I can concurr, I just had 2023.4.2 installed yesterday, and today none of my shared connections, that I have had no problem with in the past, are not showing up in Studio.
I have been working with the gSuite (Google Workspace) version 2.1.2 without any issue, until Studio 2023.4.2 was auto installed yesterday, and now the shared connections do not populate to let you configure the connection in the activity cards. This is a big blocker for our development. Are we not able to back to the previous 2023.4.0 version for some reason?
There appears to be an issue with the Google Workspace activities with the UiPath Platform 23.4.2 now. I just had this version auto installed yesterday, and now with the Google Workspace 2.1.2 version, my connections from the shared folder are not visible in Studio. Will already published automations be effected by this? As in if I published a bot on Monday before this update, and the gSuite connections were working fine, will the published bot run into this issue at run time because my UiPath platform upgraded to 23.4.2 yesterday?
I have a ticket open with UiPath support since June 9th but I have not yet received any solution or even a suggested solution. @mitchell.anderson , have you found anything further? I am only attempting to use Microsoft (“OneDrive / SharePoint” and “Outlook 365” connections). The connections that I can no longer see in Studio still work with unattended automations I created (and published) prior to upgrading to Studio 2023.4.2 so the connections themselves and the folder permissions appear to be valid but I cannot see them in Studio. @marian.platonov , I am using the same version of the Microsoft Office 365 package (by UiPath) that I was using when I was successfully using Studio 2023.4.1 (which is v2.1.1).
Hey @steve.meadows, unfortunately no, I haven’t gotten any closer to resolving this issue.
I am experiencing all the same problems as you, except with my shared connections for the Google Workspace (GSuite) activities, version 2.1.2, which is also the same version that was working properly (in Studio) before the auto update to Studio 2023.4.2.
Over this weekend I was able to confirm that my unattended automation that I published before the Studio update is able to use the shared Google Workspace connection properly, and it ran without issues. So at least already published automations are not effected, but we probably won’t be able to edit and publish a newer version of a previously published bot while the shared connections still aren’t showing up in Studio.
I am planning to release another unattended automation this week, but it also uses the Google Workspace package. So this problem may block me from releasing my automation. I am relatively new to developing with unattended bots, but I’m wondering if a possible temporary workaround would be to have my unattended bot use a personal workspace connection, because those are still showing up for me in Studio.
I have not tested that out yet, but probably will later today. I will comment back with any additional findings/info.
lrtetala
Anil_G
ashokkarale
SorenB
jast1631
kian.ng
mateuszmacheta
adext
Pierre_MOLs
alex87