Connect File rules
|
Complete this tab to identify the file name, location, and other characteristics of the connector.
Field |
Description |
Destination Path |
Enter a full path to an existing output directory. For example, if the Process Commander server is hosted on Windows, you can enter C:/temp. If the server is hosted on UNIX-based operating system, you can enter /tmp. |
File Name |
Optional. Enter a file name and optionally a file type (extension) that is valid for the server platform. This field is required unless this Connect File rule is to download a work object file attachment. In that case, leave the File Name blank. The output file has the same name as the work object attachment. |
If File Already Exists |
Select to control runtime results when a file already exists:
|
Field |
Description |
Keep File Open |
Your application can create the contents of the output file with a single execution of the Connect-File method, or with multiple executions. See Connect-File method. Select this check box to allow the file to remain open for additional output. Include in the processing sequence a final use of the Connect-File method that closes the file. |
Field |
Description |
Status Value Property |
Identify a property to hold the outcome status rule. You can use a default property @baseclass.pyStatusValue or another |
Status Message Property |
Identify a property to hold an outcome status message. The default value @baseclass.pyStatusMessage. |
Test Connectivity | After you save the Connect File form, click to confirm that the server hosting Process Commander has write access to the directory. ( No files are written by this operation.). |