Exporting Libraries as Reusable Flows
Many of the source RPA tools support the concept of a library. "Libraries" in UiPath, or VBOs in Blue Prism are examples, where the code can be reused in multiple automations. After importing these to Blueprint their contents become individual Blueprint processes. When exporting to PAD if you'd like these to again become reusable across multiple automations (flows) then you would use the "Export as Library" or "Export as VBO" feature. This feature:
- Exports each process or action as a separate PAD Flow that can be referenced by any other Flow
- Tags each exported Flow with the name of the library for easy filtering and organization in PAD
- Creates Reuse Rules for each exported Flow so future migrations automatically reference them
- Converts calls between exported Flows into Run Flow calls
β This feature is only available when Enable Rules is on in Settings. See Exporting RPA from Blueprintο»Ώ.
Blue Prism β Export as VBO
Preserves the VBO concept after migration to PAD. Each action within the VBO is exported as an individual PAD Flow, tagged with the VBO name so all actions remain grouped and discoverable in PAD's filter view.
- In the Project Explorer, select and activate the root process of the VBO β this is the process that shares the VBO name and is the parent of all VBO actions
- Choose Export -> Export as VBO
- Click Continue in the confirmation modal and select any additional export options when prompted
Blueprint creates an export job that generates a tagged PAD Flow for each VBO action and the associated Reuse Rules.
UiPath & A360 β Export as Library
Any folder or process can be exported as a library. Each Blueprint process within the selected folder or process is exported as a separate PAD Flow and tagged for grouping.
- In the Project Explorer, select the desired UiPath or A360 folder or process
- Choose Export -> Export as Library
- Click Continue in the confirmation modal and select any additional export options when prompted
Blueprint creates an export job that generates a tagged PAD Flow for each process and the associated Reuse Rules.
Tag values by platform:
- UiPath β the namespace value is used as the tag
- A360 β the folder name is used as the tag
ο»Ώ
This video gives an example of the feature being used: