Welcome to the Windows-based UiPath Activities for PAD flow Export and Import repository! This collection of UiPath activities is designed to make backups of Flows in Power AutomateDesktop.
-
Export flows from My Flows section of Power Automate Desktop, looping through each Subflow and storing contents in WinAutomation syntax-based .subflow files in Subflow folder.
-
Export each flow Arguments (Input/Output variable panel contents), including all variable propety data, and store in Arguments folder of exported flow as an .arg file.
-
Import flows into My Flows section of Power Automate Desktop, looping through each Subflow and pasting it's contents from previously saved .subflow file from a specified Backup folder.
-
Import specific or all flow Arguments (Input/Output variable panel contents) including all variable propety data from the Arguments folder for each flow.
-
Export and import flows work with the following folder structure:
Root folder (define this in Import to import all flows)
——exported_FlowName (define this in Import to import just this particular flow)
——-Subflows
————Main.subflow
————SubflowName.subflow
——-Arguments
————Input
—————InputArgument.arg
————Output
—————OutputArgument.arg
- Export Test flow:
pad_exportflows_3.4.1080p.mp4
- Import Test flow:
pad_importflows_3.4.1080p.mp4
This attended automation allows to export arguments and all subflows of a Flow in PAD.
It is designed for RPA developers or RPA users that have the need to export flows from Power Automate Desktop My Flows section, including flow arguments and subflows.
This ready-to-go automation is fully compatible with PAD_ImportFlows, which allows to import flows from the PAD_ExportFlows created folders/files.
This ready-to-go automation has been tested and confirmed working with:
- Minimum display resolution 1024x768
- UiPath Assistant 24.10
- Power Automate Desktop 2.46 and 2.47, both Store and Standalone installer type
- Windows 11 22H2
- Windows 10 21H2
To install this ready-to-go automation, simply download it from UiPath Assistant 24.10 Marketplace.
This ready-to-go automation requires little configuration.
-
Prior to launching the automation, please launch and sign in to Power Automate Desktop. If you fail to do so, you will be prompted during automation.
-
The automation offers to choose and existing or create a new folder for exports at runtime.
- Run the automation
- Select or create new folder that will store exported flow/flows from PAD My Flows section
- Define which flows to export from the list of My Flows by entering flow names separated with ;, or type All into prompt to export all flows from My Flows
-
Extract one, several, or all PAD flows from "My flows" page
-
Create backups of each subflow in a flow-named folder structure, complete with each Argument (Input/Output variable)
-
Export files as .arg for arguments and .subflow for subflows for easy viewing in Notepad
-
Examine contents of PAD flow files with WinAutomation syntax
Neat export folder structure:
Export Folder defined in Browse For Folder prompt
——exported_FlowName
——-Subflows
————Main.subflow
————SubflowName.subflow
——-Arguments
————Input
—————InputArgument.arg
————Output
—————OutputArgument.arg
Most common error is due to UiPath Browse For Folder activity that presents folder selection dialog underneath active windows.
- If after the initial message box to select a folder for export, a Browse For Folder does not appear, please check manually if it is hidden underneath any active windows
Second most common error is due to longer time of opening of the Flow Designer panel.
- If the automation fails at Getting ready screen when opening a specific flow for the first time, please stop the automation, open the flow manually once, and re-run the automation
Third most common error is due to flows appearing in My Flows section of PAD, but they have been deleted in another instance of PAD.
- When automation opens user-specified flow from My Flows, if it has been deleted inside another instance of PAD for the same user, the deletion have not been yet synced to PAD instance that is being automated. This will result in an error popup in PAD.
PAD_ExportFlows does not have the capability to extract UI Elements and Images associated with the Flow.
PAD_ExportFlows does not yet have the capability to configure Flow run delays.
This attended automation allows to import arguments and all subflows of a Flow into PAD.
It is designed to supplement PAD_ExportFlows ready-to-go automation and import flows into Power Automate Desktop My Flows section, including flow arguments and subflows.
This ready-to-go automation is fully compatible with PAD_ExportFlows, which allows to export flows from the PAD_ExportFlows created folders/files.
This ready-to-go automation has been tested and confirmed working with:
- Minimum display resolution 1024x768
- UiPath Assistant 24.10
- Power Automate Desktop 2.46 and 2.47, both Store and Standalone installer type
- Windows 11 22H2
- Windows 10 21H2
To install this ready-to-go automation, simply download it from UiPath Assistant 24.10 Marketplace.
This ready-to-go automation requires little configuration.
-
Prior to launching the automation, please launch and sign in to Power Automate Desktop. If you fail to do so, you will be prompted during automation.
-
The automation prmompts the user to define a folder with previous export of PAD_ExportFlows.
- Run the automation
- Select a folder that contains either all previous "exported_FlowName" exports, or select a "exported_FlowName" folder to import only one flow
-
Import one or all PAD flows into "My flows" page
-
Leverage PAD_ExportFlows .arg and .subflow files to import nearly all Subflow data, complete with each Argument (Input/Output variable)
-
Use .arg for arguments and .subflow for subflows files in Notepad
-
Examine contents of PAD flow files with WinAutomation syntax
Neat export folder structure:
Improt Folder as defined in Browse For Folder prompt
——exported_FlowName
——-Subflows
————Main.subflow
————SubflowName.subflow
——-Arguments
————Input
—————InputArgument.arg
————Output
—————OutputArgument.arg
Most common error is due to longer time of opening of the Flow Designer panel.
- If the automation fails at Getting ready screen when opening a specific flow for the first time, please stop the automation, open the flow manually once, and re-run the automation
PAD_ImportFlows does not have the capability to import UI Elements and Images associated with the Flow.
PAD_ImportFlows does not yet have the capability to configure Flow run delays.
Sergejs Babikovs aka pizzadesk - https://github.com/pizzadesk/
https://github.com/pizzadesk/ https://www.linkedin.com/in/sergejsb/ https://www.linkedin.com/in/sergejsb/