Specifications
• The appropriate PowerSwitch/ FullSwitch connection has been established; see connecting to
Switch.
• The server information has been recently updated; see updating server information.
• The messages issued by all enabled connections are merged in a single list.
Note:
SwitchClient can no longer show log messages that have been deleted by PowerSwitch/ FullSwitch,
so showing logs is also limited by the "cleanup" Application Data preferences in PowerSwitch/
FullSwitch.
Filtering and sorting messages
Type search strings in the filter fields at the top of the message pane to select the subset of
messages to be displayed. To sort the table rows on the values in a particular column, click on
that column's header. To rearrange the table columns, drag the column headers around.
For more information see Viewing log messages in PowerSwitch/ FullSwitch.
Working with jobs
Job folders
In Switch a job can be an individual file or a job folder.
An individual file is treated as expected.
A job folder represents a set of files that moves along the flow as a single entity. For example,
a page layout with its accompanying images and fonts or the individual pages in a book. A job
folder may contain nested subfolders (which can contain other files and folders, recursively).
To submit a job folder to a flow, simply click the Submit Folder button - which is similar to
clicking the Submit File with a regular file. The job folder is submitted to and moved along the
flow as a single entity.
PowerSwitch/ FullSwitch can disassemble jobs into separate files if required, but not every flow
uses this capability. Thus it is important to know, for each Submit point, whether its flow supports
job folders or not.
See also Working with folders.
Relationship between jobs
Sometimes a particular job spawns another related job. For example, a preflight application
might generate a preflight report about the job. This report is a separate job (most likely a single
file) since the original file is still there as well. Most often the report is named for the original
job (with a different suffix), but in the current version of Switch there is no other way to show
the relationship between the two jobs.
165
Enfocus Switch 10