How to manage dependency files

Hi,

I made some searches on this topic, but couldn’t find anything. Sorry if this has already been discussed.

I am curious how you guys manage files that a given workflow is depending on. Files that must exist on the local robot to be able to execute a workflow.

The obvious (and bad practice) would be to just make sure the files exist on the robot by manually copying them there. I am sure there are clever ways to have such files bundled or associated with a given workflow. I am still new to this, so I wonder if the answer is in nupkg somehow?
I was thinking about a workflow template that downloads files from a central FTP site which looks up the files by workflow name and version. Maybe I am overthinking this and not seeing the obvious (easy) way to manage this challenge.
So, back to my question: How do you deal with this?

Thank you in advance.

br
Jesper

Hi
welcome to uipath community
thats a good question indeed
Fine

usually when a project is developed and published, its dependent workflow files or even other files like config, json or an excel file, all are kept in the same project folder and then only published so that we make sure that the dependency files are missed out any where, as they are being published with the mail.xaml file of our project
then

Exactly its all about .nupkg file that gets created when a project is published…so while publishing itself keep all the dependent workflows for that project in the same project folder and make sure that you have used those workflows inside your main xaml by using INVOKE WORKFLOW FILE ACTIVITY

Well FTP can be used to share the workflow between our local and to the remote servers and i hope it wont play a major role here when maintaining the dependent workflows

hope this would help you
Cheers @jesperrula

Thanks. So if I add a file to the project folder and use the INVOKE WORKFLOW FILE ACTIVITY, Orchestrator will know that the file is required and bundle it with the workflow when publishing? I have a feeling that I’m still missing a part of the puzzle.

Fine
publishing a process doesnt depend on orchestrator and even without orchestrator a process can be published
and coming to the point INVOKE WORKFLOW FILE activity is generally used when many workflows are used to gether in a single main xaml process and to use the functionality of each and every workflow along the current process
so to use that we need to have all those workflow xaml file in the project folder so that can be called with this activity
–and while publishing a package with all these workflows been called, if any validation error or syntax error occurs with any one workflow it wont allow us to publish. So only after rectifying them we would be able to publish a project as a package
–for example even if the file is called in a invoke workflow and if the file is not there in the project folder we wont be able to publish that project

hope this would help you
Cheers @jesperrula