ServerAdmin - Configure - Files tab

The File tab allows you to identify and configure output folders and file names. You can access it by following these steps:

1. In the Settings tab, click on the ServerAdmin icon:
   
   
   
2. When the Server Administration opens, select your printer and click on Configure. 
   
   
3. Go to the Files tab.

Base Directory

• Root: Defines the folder in which the files generated by the printer will be saved.
  Click on the ellipsis button [ ] to select a new folder. For example, you can use a shared folder from the Pinter Controller. It does not include options (media name, etc.) and job name.
• Optional: If you wish to add job-dependent strings to the folder’s name (media name, resolution, etc.), click on the ellipsis button [ ] of this field. A new window will appear, where you can select the strings to insert:

• Available: Column where you can find all the options available for selection.
• Selected: Column that shows the selected option.
• Add all: Add all the options to the selected one.
• Add: Add just one option to the selected ones.
• Pos.: Use the Position field or + and - to move ahead or move down an option.
• Delete: Delete only a selected item from the selected options.
• Clear: Delete all the selected options.
• Current list: Summary according to the sequence of the selected options.
• Example of optional strings, resolution (%r) and quality (%Q), added to a base directory:
  /opt/caldera/var/public/CalderaJet/100x100/1 pass
  

    Info

  In computer programming, a string is traditionally a sequence of characters, either as a literal constant or as some kind of variable.

Create one folder per job

• Create one folder per job: Check this box if you want to save all the generated files in a folder specific to the job.
• Name: Allows you to define how these folders are to be named. By default, the name is <%n> (which corresponds to the job’s name), but you can edit it directly in the field.

File names

• Data: This is the name of the output data file(s). It must contain the string <%n> (corresponding to the job’s name) unless each job is saved in its own folder. If not, all jobs might be overwritten by the next one.
  If the printer generates one data field per ink channel, you also have to add the <v%> string (ink identifier).
• Process ink IDs: You can edit the list of identifiers for process inks by clicking on the ellipsis button [ ] to edit.

    Warning

  Please note that changing the default values may cause trouble with the printer controller.

• Ticket: This is the ticket’s name. If each job is saved in its folder, it also has to contain the <%n> string.
  If this field is left blank, no ticket is generated.
  The ticket is either in the format specified by the printer controller or in the standard Caldera format (simple text file).

Options

• When job already exists…: This option defines what the printer driver has to do when you RIP the same file twice (or when two different files have the same name). Options are:
  • Increment the job’s index.
  • Write over the previous existing job (Erase files).
• Indexation scheme: This option defines how the jobs’ names will be incremented. Three ways are available:
  • Without any separator.
  • With dot separation.
  • With underscore separation.
• Confirmation before printing: Set this option accordingly if you wish a confirmation dialog window to pop up when you click the Print button, in the main interface:
  
  
  This dialog box shows where the file is to be generated, and also allows you to change the job’s name and folder. You can choose to display it:
  • Always.
  • Never.
  • Or using the keyboard shortcut Shift+Click.

Edit forbidden Characters

Clicking this button opens an editor where you can define which characters cannot be used in the file names:

• Spaces.
• Non-ASCII characters.
• Quotes and double quotes.
• Other characters (defined by you in the space for it).

You can set a replacement character in the With field.

• Example: In the following image, we defined that spaces should be replaced with an underscore. The second image shows you how the file is now named: