Process Automation Library

i_planned
orchestrator
studio
r_18_3

#1

UiPath Edit

Why

  • need the ability to invoke and deploy common pieces of automation (eg: SAP Login / Workflows from a master/common project); as of now the shared folder approach is available

How it works

  • set one or multiple common projects/processes in Orchestrator Ui
  • these will become visible in UIPath Studio interface
  • drag & drop will generate an Invoke Workflow Activity
  • this common projects/folders will be deployed/versioned on all robots via the orchestrator

I’ve been having fun recently getting to know UiPath and even after a small amount of training I find we get along very well :wink:. As I work in healthcare and am surrounded by dozens of applications, I could see myself quickly building a collection of small application-specific workflows to use in multiple automation projects. These don’t really fit into UiPath’s project template, having no entry point or logical flow of steps, nor into the Library category, because they have to be invoked as workflows rather than pasted as a snippet of code.

Of course, invoking such workflows from a network storage location as you recommend is sensible and works, but I feel this category could do with some more love. I would love to have a pane I can point to a folder, similar to the Library pane, and drag from to create an “Invoke Workflow” activity in my current workflow, similar to the Project pane. What do you think?


How to establish communication between two packages?
#2

Such a feature is in the works, hang tight.


#3

Till then the workaround is to use a shared network folder to invoke the reusable components.


#4

Awesome, thanks for the quick reply guys!


#5

I was just wondering if the feature is in place now? We are in the same situation and would like to have a place that we can have them in a multi developers can utilize the library.


#6

It’s planned for 2018_2 release, so… in 6-9 months, more or less.


#7

I figured out another way but will wait to see what the release has.

Thanks!


#8

Can you or someone expand in greater detail whether it’s currently possible to have one or more common/shared workflows that robots A, B, and C all use… and then be able to modify the common workflow and have robots A, B, and C all instantly benefit from that change without having to re-publish them all?