This is the first topic in the #BetaFollow-up series.
First, big thanks to @MirceaGrigore who has helped put this in place.
Today’s topic: Library (Reusable components).
What is it?
A Library is a collection of reusable components. A reusable component is a workflow that can be compiled and packaged as an activity and reused in multiple processes. So go ahead and define all that common code once and reuse it multiple times. You can now create these workflows and publish them as activities.
Why do you need this?
Reuse is a key enabler for improving business efficiency. As developers we can’t afford to do things differently in every process and for every automation, but at the same time to hope for flexibility and innovation. A known best practice in the development world is to divide a business process into smaller parts. Common parts become reusable so that you don’t reinvent the wheel every time.
Who needs this?
This feature mostly addresses to RPA Developers and will help you easily maintain the automation processes, align with internal best practices and reuse existing implementations. RPA developers and IT need it so that they do not do redundant work, so that they can easily maintain process automations, so that they align with internal best practices and reuse existing proven, reliable and robust implementations. Business need it because it is costly to have to implement the same thing every time.
So, how does it work?
The easiest way to explain our new Library feature is to showcase an example. For the purpose of this demo we will keep the example very simple.
Let’s assume we have an existing automation called “Expense Report in Concur” which we built using 18.2. Normally an automation like this would have multiple moving pieces but for the sake of simplicity let’s say this automation has 3 workflows:
Main which calls a Login subworkflow, then does some expense actions and last calls a Logout subworkflow (via Invoke Workflow)
Login to Concur
Logout from Concur
Instead of using 2 invoke workflows like “Login” and “Logout” which represent common logic for any Concur related process, we could build a Library with these 2 components.
Start building a Library of Concur reusables from scratch…
Import your Login and Logout workflows from the initial process (or really build from scratch if you feel like it)…
Publish your new Library project…
Publish screen will appear …
You can now use this Library in any process. Easy!
Let’s go ahead and modify our initial process.
Delete the Login and Logout workflows - you don’t need them anymore. Yes, click ok
Go to Manage Packages and add your local folder as a Feed…
Install the Concur Library …
This will add Login and Logout activities in the Activities Panel. Replace the Invoke Workflows to Login and Logout with the newly added activities.
Finally your new project using reusable components should look like this:
Let us know what you think!