1.3.5.2. File Repository

The Configuration Items → File Repository page can be reached by clicking the   menu item.
On this page can be defined a multitude of scripts and their versions that can be assigned to workflow timestamps and included in the execution of the workflow using PSscript or RunBashScript activities.

A version will be available for assigning to a workflow timestamp only after selecting it and making it active (by clicking the Make Active button). The scripts are kept under folders and/or subfolders. The scripts versions are kept under the scripts. Each script will have at least one version, which is actually the one that contains the script code.
A folder can be defined by clicking the Add Folder button from the Folder Actions drop-down list.

 
The Add new folder window will open:

• insert a name for the new folder
• insert a description for the new folder (optional)
• click Save changes in order to finish creating the new folder

When you click on a folder name, the Details for scripts folder section will be displayed:

• edit the name for the folder
• edit the description for the folder (optional)
• click Edit Folder Rights, if you want to give certain administrator rights for the version. Administrators can only see and work with the folders to which they have rights, but SuperAdmins can access all folders.  When you give certain administrator rights on a folder, the same rights will be automatically propagated to all the scripts under that folder.
• click Yes/No on the Confirmation window, depending on your choice
• click Save Changes in order to save the changes

A subfolder can be defined by right-clicking on a folder and selecting the Add Folder option. 

• insert a name for the new sub-folder
• insert a description for the new sub-folder (optional)
• click Save changes in order to finish creating the new sub-folder

A script can be defined after selecting a folder, by clicking the Add Script option from the Folder Actions drop-down list or by selecting the Add Script option after right click over the folder. The Add Script window will open:

• insert a name for the script
• insert a description for the script(optional)
• click Save changes in order to finish adding the new script

When you click on a script name, the Details for script section will be displayed:

• edit the name for the folder
• edit the description for the folder (optional)
• the Path is prefilled automatically - this path can be used in Designer as input  for GetFileRepositoryContent activity
• click Save Changes in order to save the changes

A script version can be defined after selecting a script, by clicking the Add version option from the Version Actions drop-down list or by selecting the Add Version option after right click over the script. The Add new version window will open:

• insert a name for the version
• select the script's version type: Powershell, SSH, Python, Yaml, Json, Xml and Perl
• insert a description for the script version (optional)
• insert a value for the script version
• click Save changes in order to finish adding the new script version

When the new version is created, a corresponding timestamp is automatically added to it.

There are three options that can be set by right-clicking on version: Clone version to other script, Remove and Export.

Clone version to other script

• click on Clone version to other script
• select the Target Folder
• insert a New script name
• insert a New script description
• insert a New version name
• insert a New version description
• click OK in order to save the settings

Remove

• click on Remove
• click Yes in order to delete the version

Export

• click on Export
• the version is downloaded

When you click on a version name under a script, the Details for version section will be displayed:

• edit the name for the version
• edit the description for the version (optional)
• click Edit rights, if you want to give certain administrator rights for the version. Administrators can only see and work with the scripts to which they have rights, but SuperAdmins can access all scripts. This will also affect which script versions are sent to the Designer when an administrator checks-out a workflow
• edit the script content for that version or browse after an already existing script

• click on Is Active, if you want to activate the version. Making it active, it will mark it also as active in the Scripts tab in Workflow Details panel
• edit the Version Type: Powershell, SSH, Python, Yaml, Json, Xml and Perl
• click Test Script in order to test the script.

NOTE: the errors returned by the script execution are now visible in the Test Script area, unlike previous versions of Flowster Studio, when a generic error was thrown and an execution test was required in Powershell/SSH applications

• click Save Changes in order to save the changes. You can overwrite existing version or save as a new version