You can create a new or edit and old context config in this user interface. To load an existing config file click on the `| Load Context Config |` button. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely. All jobs must fill out the local dependency fields at the top of the block.
@@ -102,7 +102,7 @@ Now when running a job you can simply load this file and it will populate the re
There needs to be a unique batch config file created for each script in the pipeline. Batch config files are not dependant on the project or the user.
:so: Only create one local and one remote file for each script. To get started go to:
You can create a new or edit and old batch config in this user interface. To load existing batch files click on the `| Get Batch Config File Names |` button. This interface allows you to look at, and edit, multiple config files at once. This helps you visualise the pipeline order, and ensure that every script you are using has a designated configuration file for it. If you are loading you can adjust the order of the files by changing the names of them in the the load window. If you do not change anything they will be loaded alphabetically. You will need to fill out a number of fields depending on whether you will be running the job locally or remotely.