Organizing Jobs into Workspaces

A workspace groups jobs that belong together, such as the jobs for one product or one release line. Each workspace has a jobs folder, a staging folder, and a set of destinations that every job in the workspace can deploy to by name. The ePublisher AutoMap Administrator shows one workspace at a time. When the computer has workspaces other than Default, its title bar names the workspace it shows.

The Default workspace is the job folder and staging folder set in the ePublisher AutoMap preferences. An interactive installation of ePublisher AutoMap also adds the Quantum Sync Trial evaluation workspace. For more information, see Trying ePublisher AutoMap with the Quantum Sync Trial.

The list of workspaces, and the workspace the Administrator shows, are stored with the ePublisher AutoMap preferences for the computer, so every user of the computer shares them.

Switching Workspaces

On the File menu, point to Workspace, and then click the workspace you want to see. The main window then lists the jobs in that workspace's jobs folder, and the Job folder and Staging folder fields in the preferences show that workspace's folders.

Switching changes only what the Administrator shows:

  • Scheduled tasks keep running, whichever workspace is shown, because each task names its own job file.

  • Each job stages into the staging folder of its own workspace. The job log names the folder and where it came from, for example Staging folder of the 'Release 2026.1' workspace: D:\Builds\2026.1\Staging.

  • A job run from the command line finds its workspace from the location of its job file.

Adding, Editing, and Removing Workspaces

To add a workspace

  1. On the File menu, point to Workspace, and then click Manage Workspaces.... The Workspaces window lists every workspace with its jobs folder, staging folder, and destinations.

  2. Click Add....

  3. In the Workspace window, type a Name, and choose the Jobs folder and Staging folder. You can click Browse... to choose a folder.

  4. Optionally, add Destinations for the jobs in this workspace. For more information, see Workspace Destinations.

  5. Click OK, and then click Close.

To change a workspace, select it in the Workspaces window and click Edit.... Editing the Default workspace changes the job folder and staging folder in the preferences.

Each workspace needs its own name and its own folders. ePublisher AutoMap checks a new or edited workspace and explains what to change:

  • A workspace named '…' already exists. Workspace names must be unique, and only the Default workspace can be named Default.

  • This jobs folder is the same as, inside, or around the jobs folder of the '…' workspace. Jobs folders cannot be the same, and cannot contain one another, because ePublisher AutoMap finds a job's workspace from the folder its job file is in.

  • The '…' workspace already uses this staging folder. Same-named jobs in different workspaces would overwrite each other's staged files.

To remove a workspace, select it and click Remove. Removing a workspace only takes it off the list: its folders and jobs are not deleted, and scheduled tasks for its jobs keep running. If you remove the workspace the Administrator shows, it shows the Default workspace.

Managing Workspaces from the Command Line

A script, an installer, or a build server can add, remove, and list workspaces with the ePublisher AutoMap command-line interface, so a computer can be set up without opening the Administrator. The command line applies the same checks as the Workspace window and reports the same messages. It needs permission to change the ePublisher AutoMap preferences for the computer, and nothing else.

The following example adds a workspace named Docs 2026.1:

WebWorks.Automap.exe --addworkspace="Docs 2026.1" --workspacejobs="D:\Docs\2026.1\Jobs" --workspacestaging="D:\Docs\2026.1\Staging"

ePublisher AutoMap creates the folders if they do not exist yet. Running the same command again changes nothing and succeeds, so a setup script can run more than once. If a workspace with that name already uses other folders, the command stops with an error and changes nothing; to give that workspace the new folders, run it again with --replaceworkspace added.

The following example removes the workspace from the list. As in the Workspaces window, its folders, jobs, and scheduled tasks are not touched:

WebWorks.Automap.exe --removeworkspace="Docs 2026.1"

The following example lists the workspaces on the computer, one per line, with the name, jobs folder, and staging folder separated by tabs. The Default workspace is not listed:

WebWorks.Automap.exe --listworkspaces

These options run on their own, without a job or project file. If you change the workspaces while the Administrator is open, it shows the change the next time you open the File > Workspace menu or the Workspaces window, and changes you then make in the Administrator keep it. Destinations for a workspace cannot be added from the command line; add them in the Workspace window, or write the automap-workspace.xml file in its jobs folder. For more information about the options, see CLI Syntax and Reference.

Workspace Destinations

Destinations added in the Workspace window are saved with the workspace, in an automap-workspace.xml file in its jobs folder. Because the file sits with the jobs, the destinations travel with them, for example into version control. Every job in the workspace can deploy to them by name, including scheduled and command-line runs, and no credentials are stored. In the Deploy to list on a job's Target Configuration tab, a workspace destination is labeled with (workspace):

Product Help Site (workspace)

When a job runs, ePublisher AutoMap finds the workspace's destinations by looking for the first automap-workspace.xml file in the job file's folder or the folders above it. A jobs folder inside a folder that has its own automap-workspace.xml file, such as a repository root shared by several workspaces, therefore uses that file's destinations until destinations are added for the jobs folder itself. If two places define a destination with the same name, the first of these wins:

  1. A destination defined in the job itself, on the Job Deploy Destinations tab.

  2. A destination in a file passed with the --deploysettings command-line option.

  3. A destination saved with the job's workspace.

  4. A destination defined on the computer, in the Deploy Destinations window.

The job log names the workspace file it used:

Using the workspace destinations in 'D:\Builds\2026.1\Jobs\automap-workspace.xml'.

Note: An automap-workspace.xml file can also reference a deploy settings file that you maintain yourself, in the same format as a --deploysettings file. The Workspace window lists that file's destinations but does not edit them, and destinations saved with the workspace take precedence over them. The job log names the referenced file: Using the workspace deploy settings file '…' (named in '…'). If the workspace settings file cannot be read, the job reports the problem instead of deploying somewhere else.

Scheduling Jobs Across Workspaces

Windows Scheduler task names come from job names, waj followed by the job name, so same-named jobs in different workspaces share one task name. For example, the Product Help job in a 2025.1 workspace and the Product Help job in a 2026.1 workspace both use the task waj Product Help. ePublisher AutoMap handles this as follows:

  • When you click Run for a job whose task currently runs the same-named job in another workspace, ePublisher AutoMap points the task at this job's file, provided the task runs under your Windows account. If the task has no schedule, it does so without asking. If the task has a schedule, it warns you, names both job files, and moves the task and its schedule to this job only if you confirm.

  • If that task is running the other job right now, ePublisher AutoMap asks you to run this job again when that run finishes.

  • A job whose task runs another job file shows a note in the main window, for example The scheduled task 'waj Product Help' runs another job file: D:\Builds\2025.1\Jobs\Product Help\Product Help.waj.

A recurring schedule for a job name can therefore belong to only one workspace at a time.

When the Workspace List Cannot Be Read

If the list of workspaces cannot be read, the Administrator shows only the Default workspace and explains why. A Stationery-based job that runs without the -s command-line option stops with an error instead of staging into the Default workspace, because staging into another workspace's folder could overwrite the files of a same-named job.

Last modified date: 11/05/2026