About pub and xpb

Although you can run any workspace or runset from the command line, it is a best practice to run only a published runset or workspace as your production run.

When you publish a set of triggers from a workspace or a runset, Detect takes the set of triggers and does two things.

It creates a read-only production workspace named pub, which overwrites any existing pub workspace. If you publish a runset, all of the triggers you selected for the runset are included in pub. There can only be one published workspace. You can view this workspace in the Workspace area of Detect, but you cannot edit it. This provides enhanced control of the data resulting from the run.

It deactivates the existing pub workspace and archives it by saving it as xpb. This overwrites the existing xpb archive. There can only be one xpb workspace. If someone erroneously publishes a workspace or runset, you can restore the previous published set of triggers by publishing xpb. To preserve a copy of the components from the last xpb, you should copy or move those components into a new workspace before publishing a new workspace or runset.