A Library is a collection of reusable components. A reusable component is a workflow invoked as an activity in multiple processes. It’s powerful because it decreases the development time, saves time from debugging because ones it’s done you just use it in the projects that you need and your team doesn’t need to invest again the time for solving a specific problem.
When we think of reusable components - we need to think how we can create them as functionalities. When creating a library we don’t want that library to be for a specific bot or group of bots. We want to create it in a way that the developer can use it in every project that he needs.
I believe that a good practice for creating libraries is to split them based on application/system.
ex: WordActivitiesLibrary or MailActivitiesLibrary.
This way the developers will know what to expect when they install your library.
The second important thing we can do is to create the specific reusable component dynamically as possible!
How we do that?
- by making a .xaml file for only one action. ex: ExcelWrapText ex: ExcelChangeFont ex:ReadWindowsInputLanguage
- by creating good logic with proper error handling that will give us error stored in output argument if there’s one.
If you want to learn more about libraries and how we can make the most of them check out my tutorial:
