Workflow Manager 2013 R2
In the course of completing workflow requests, your workflow consumers and administrators may want to upload or download files relevant to the tasks they are performing. Do the following to configure which directories on your Workflow Manager server uploaded files should be stored in:
To specify folders for uploads and downloads:
| 1. | Navigate to the following shared directory on your Workflow Manager server: \\<workflowManagerServer>\AESFileShare\_____AMS_System_Uses_This_Folder_Do_Not_Modify\ _____Sample_Folder_Structure, and open the DirectoryConfig.xml file in a text editor of your choice. |
| 2. | The file contains a list of tags, each representing a directory where your uploaded and downloadable files will be stored. Update each tag with the name of an appropriate subfolder of the _____Sample_Folder_Structure directory you just opened. The following tags are available for you to modify: |
|
Tag Name |
Purpose of Folder |
|
InstallationUploadDirectory |
This directory contains files uploaded during the completion of a workflow request, using a data element of type Application Upload. |
|
DocumentUploadDirectory |
This directory contains files uploaded during the completion of a workflow request, using a data element of type Document Upload. |
|
DependencyUploadDirectory |
This directory contains files uploaded during the completion of a workflow request, using a data element of type Dependency Upload. |
|
CustomerDownloadDirectory |
This directory contains files that can be downloaded from the Downloadable Files sub-tab of a workflow request’s Workflow Progress page. |
|
IssueFileUploadDirectory |
This directory contains files associated with an issue raised during the course of a workflow request. |
For example, the contents of DirectoryConfig.xml might look like this:
<DirectoryConfiguration>
<InstallationUploadDirectory>
6_Original_Install
</InstallationUploadDirectory>
<DocumentUploadDirectory>
7_Documentation_Misc
</DocumentUploadDirectory>
<DependencyUploadDirectory>
8_Dependencies
</DependencyUploadDirectory>
<CustomerDownloadDirectory>
1_MSI_Repackaged_Install
</CustomerDownloadDirectory>
<IssueFileUploadDirectory>
5_INC_Files
</IssueFileUploadDirectory>
</DirectoryConfiguration>
| 3. | If any of the folder names you specified in the previous step do not yet exist as subfolders of the _____Sample_Folder_Structure, ensure you create them before beginning to use Workflow Manager. |
Note: The first time a workflow consumer or administrator uploads a file during the course of completing a workflow request, Workflow Manager does the following:
| • | Creates a subfolder of the \\<workflowManagerServer>\AESFileShare directory using the name of the workflow administrator company associated with the request (unless such a folder already exists). |
| • | Creates a subfolder of the workflow administrator company folder using the name of the workflow consumer company associated with the request (unless the folder already exists). |
| • | Creates a subfolder of the workflow consumer company folder for the new workflow request, using a GUID appended to the workflow request name. |
| • | Copies all the files and folders in the _____Sample_Folder_Structure folder to the new workflow request directory. |
The file being uploaded is then placed into the appropriate subfolder (as defined in the DirectoryConfig.xml file), and the same happens to all subsequent uploaded files.
See Also
Performing Configuration Tasks
Workflow Manager 2013 R2 / AdminStudio Enterprise Server 2013 R2 SP1 Help LibraryFebruary 19, 2014 |
Copyright Information | Contact Us |