Parent page: Workspace Content Types
Altium NEXUS, in conjunction with your connected Workspace, caters for the ability to create and manage outputjobs (Outputjob Items) in that Workspace. Such outputjobs can be created:
- Through Direct Editing.
- By uploading the relevant Output Job Configuration file (
*.OutJob) to a revision of a target outputjobs.
Once an outputjob has been created (and data saved into a revision of it), it can be reused in future board-level design projects.
In addition, an Outputjob Item can be used as a configuration data item in one or more defined Environment Configurations. An environment configuration is used to constrain a designer's Altium NEXUS working environment to only use company-ratified design elements. Environment configurations are defined and stored within the Team Configuration Center – a service provided through the Workspace, and the facilitator of this concept of Environment Configuration Management. For more information, see Environment Configuration Management (for an Altium 365 Workspace or a NEXUS Server Workspace).
Folder Type
When creating the folder in which to store outputjobs, you can specify the folder's type. This has no bearing on the content of the folder – saving an Output Job Configuration file will always result in a corresponding Outputjob Item. It simply provides a visual 'clue' as to what is stored in a folder and can be beneficial when browsing a Workspace for particular content. To nominate a folder's use as a container for outputjobs, set its Folder Type as Output Jobs, when defining the folder properties in the Edit Folder dialog.
Specifying the folder type – its intended use – gives a visual indication of the content of that folder when browsing the Workspace.
Item Naming Scheme
Another important aspect of the parent folder is the Item Naming Scheme employed for it. This defines the format of the unique ID for each Item created in that particular folder. Several default example schemes are available, utilizing the short-form code for either the folder type (OUTC – OutputJob Collection) or the content type (OUT – OutputJob):
$CONTENT_TYPE_CODE-001-{0000} – for example, OUT-001-0001.$CONTENT_TYPE_CODE-001-{A00} – for example, OUT-001-A01.$FOLDER_TYPE_CODE-001-{0000} – for example, OUTC-001-0001.$FOLDER_TYPE_CODE-001-{A000} – for example, OUTC-001-A001.
Using a default naming scheme, the software will automatically assign the next available unique ID, based on that scheme, having scanned the entire Workspace and identifiers of existing content. This can be a great time-saver when manually creating outputjobs.
A custom scheme can also be defined for a folder, simply by typing it within the field, ensuring that the variable portion is enclosed in curly braces (e.g. OUTJOB-001-{0000}).
The Item Naming Scheme of the parent folder is applied to the Unique ID for each Item created within that folder.
The Item Naming Scheme employed for the parent folder can be changed at any time. The modified scheme will then be applied to any subsequent newly-created content within that folder.
Content Type
When creating a target Outputjob Item in which to store your Output Job Configuration, ensure that its Content Type is set to Outputjob, in the Create New Item dialog. If you are creating the Item in an Output Jobs type folder, this content type will be available from the right-click context menu when creating the Item.
Creating an outputjob within an Output Jobs folder – the correct Content Type is available on the context menu.
Item Lifecycle Definition and Revision Naming
When defining an outputjob, be sure to specify the type of lifecycle management to be used for the outputjob, and the naming scheme employed for its revisions, respectively.
Control over which content types can use a particular lifecycle definition or revision naming scheme, can be defined and enabled at a global level from within the Content Types dialog, when defining each schema. The default schemes assigned for use by an outputjob are: Generic Lifecycle and 1-Level Revision Scheme, respectively.
Once a template definition has been saved into the initial revision of an Outputjob Item, these schemes cannot be changed for that particular Item.
Specify the required schemes in the Create New Item dialog, using the Lifecycle Definition and Revision Naming Scheme fields respectively.
If the option to control use of lifecycle definitions and revision naming schemes per content type is enabled for any definitions/schemes, and the Outputjob content type is not set to use a particular definition/scheme, then that definition/scheme will not be available in the applicable drop-down list.
Selecting the Lifecycle Definition and Revision Naming schemes for a manually created outputjob.
Observing standard revision naming schemes and lifecycle definitions, across the various types of design content in a Workspace ensures smooth, consistent management of this content.
It is a good idea to add a Name and Description as part of the outputjob's definition. This information is used when searching the Workspace and enables quick identification of what an outputjob offers.
Saving an Output Job Configuration
Related page: Creating and Editing Content Directly through a Workspace
So far, we've discussed the support for an outputjob in the Workspace, in terms of related folder and content types. Saving an actual defined Output Job Configuration into a revision of an Outputjob Item can be performed in a streamlined way.
An Output Job Configuration can be edited and saved into the initial revision of a newly-created Outputjob Item, courtesy of the Workspace's support for direct editing. Direct editing frees you from the shackles of separate version-controlled source data. You can simply edit a supported content type using a temporary editor loaded with the latest source direct from the Workspace itself. And once editing is complete, the entity is saved (or re-saved) into a subsequent planned revision of its parent Item, and the temporary editor closed. There are no files on your hard drive, no questioning whether you are working with the correct or latest source, and no having to maintain separate version control software. The Workspace handles it all, with great integrity, and in a manner that greatly expedites changes to your data.
When you create an Outputjob Item, you have the option to edit and save an Output Job Configuration into the initial revision of that Item, after creation. To do so, enable the option Open for editing after creation, at the bottom of the Create New Item dialog (which is enabled by default). The Item will be created and the temporary Outputjob Editor will open, presenting a .OutJob document as the active document in the main design window. This document will be named according to the Item-Revision, in the format: <Item><Revision>.OutJob (e.g. OUT-0006-1.OutJob).
Example of editing the initial revision of an outputjob, directly from the Workspace – the temporary Outputjob Editor provides the document with which to define your configuration.
Use the document to define the Output Job Configuration as required. For more information on doing this, see Streamlining Generation of Manufacturing Data with Output Jobs.
Maximizing Reusability – Making Your Output Job Configuration Generic
A number of innovative features are available when configuring your outputs to make the resulting Output Job Configuration as generic as possible. By keeping an OutJob generic, you can effectively maximize its ability to be reused across future design projects.
Generic Data Source Names
Many output generators use a specifically-named underlying document as their source, from which the applicable output data is generated – for example Gerber files generated from the PCB document FluxTriangulator.PcbDoc. However, doing so locks the Output Job Configuration to being useful only with that document's parent design project. To keep things non-specific, a generic entry for the underlying Data Source is available for selection across many of the output generators. The following table summarizes which output generators are supported, and the generic entry (entries) available.
| Category |
Output Type |
Generic Data Source Entry |
| Netlist Outputs |
All |
[Project] |
| Simulator Outputs |
Mixed Sim
SIMetrix
SIMPLIS |
[Project] |
| Documentation Outputs |
Composite
PCB 3D Print
PCB 3D Video
PCB Prints
PDF3D |
[PCB Document] |
| |
PDF3D MBA |
[MBA Document] |
| |
Schematic Prints |
[Project Physical Documents] |
| Assembly Outputs |
All |
[PCB Document] |
| Fabrication Outputs |
All |
[PCB Document] |
| Report Outputs |
Bill of Materials |
[Project]
[ActiveBOM Document] |
| |
Component Cross Reference
Export Comments
Report Project Hierarchy
Report Single Pin Nets |
[Project] |
| Validation Outputs |
BOM Checks |
[ActiveBOM Document] |
| |
Component states
Configuration compliance
Electrical Rules Check |
[Project] |
| |
Design Rules Check
Differences Report
Footprint Comparison Report |
[PCB Document] |
| Export Outputs |
Ansoft Neutral (AutoPCB)
Ansys EDB
AutoCAD dwg/dxf PCB
Export IDF
Export PARASOLID
Export STEP
Export VRML
Hyperlynx (AutoPCB)
P-CAD ASCII (AutoPCB)
Save As/Export PCB
SiSoft (AutoPCB)
Specctra Design PCB |
[PCB Document] |
| |
MBA Export PARASOLID
MBA Export STEP |
[MBA Document] |
| |
AutoCAD dwg/dxf Schematic
OrCAD v7 Capture Design (AutoSCH)
P-CAD V16 Schematic Design (AutoSCH)
Save As/Export Schematic |
[Project] |
| PostProcess Outputs |
Copy Files |
[Project] |
Layer Classes
You have the ability to add named layer classes to configurations for the following output generators:
- PCB Prints
- Assembly Drawings
- Drill Drawings
- Final
- Gerber Files
- Mask Set
- ODB++ Files
- Power-Plane Set
This makes these output generators generically reusable. For example, add a class 'signal layers' and refer to it in the OutJob – any design that has a 'signal layers' class will be able to use that output generator without modification.
There are three relevant controls when direct editing, readily available from the Quick Access Bar (at the top-left of the main application window), or from the Job Manager Toolbar toolbar:
These controls are also available as commands – Save (shortcut: Ctrl+S), Save to Server (shortcut: Ctrl+Alt+S), and Discard Local Changes – from the main File menu and from the right-click menu of the outputjob's entry in the Projects panel.
The saved data stored in the Workspace consists of the Output Job Configuration, defined in the Output Job Configuration file (<Item><Revision>.OutJob). In the Explorer panel, switch to the Preview aspect view tab to see the outputs defined within the configuration.
Browse the saved revision of the outputjob, back in the Explorer panel. Switch to the Preview aspect view to see the outputs contained within the configuration.
Saving the Current Output Job Configuration File
You can also save the current Output Job Configuration file to your Workspace, directly from within the Outputjob Editor. To do so, choose the File » Save to Server command from the main menus. The Choose Planned Item Revision dialog will appear – use this to choose the next planned revision of an existing Outputjob Item, or create a new Outputjob Item on-the-fly.
If creating a new Outputjob Item, be sure to disable the Open for editing after creation option (in the Create New Item dialog), otherwise you'll enter direct editing mode.
After clicking OK, the Edit Revision dialog will appear, in which you can change Name, Description, and add release notes as required. Click OK when ready – the saving will proceed, with the resulting output job configuration, stored in the revision of the target Outputjob Item, available for preview through the Explorer panel.
Saving the currently opened Output Job Configuration file to a planned revision of a target Outputjob Item in the connected Workspace.
Uploading an OutJob File
You can also upload an Output Job Configuration file into the revision of an Outputjob Item. This can be performed in a couple of ways.
Upload Menu
An Output Job Configuration file can be uploaded by right-clicking on the required Outputjob Item in the Explorer panel, and choosing the Upload command from the context menu. The Create New Revision dialog will appear, in which you can change Name, Description, and add release notes as required. Use the Sources region of the dialog to load the required OutJob file. This can be performed by dragging and dropping the file from Windows Explorer, onto the region. Alternatively, click the 
button – the Add Files dialog (a standard Windows open-type dialog) will appear. Use this to browse to, and open, the required file (*.OutJob).
If the Item has no planned revision, upload will be to the next planned revision, created on-the-fly as part of the upload process.
Manually specifying the OutJob file to be uploaded to the target Outputjob Item.
Once the desired file is dropped in, or selected and the Open button clicked, an entry for it will appear back in the Sources region. Proceed with the upload by clicking the OK button. Switch to the Preview aspect view tab to see the outputs defined within the configuration, in the Explorer panel.
The content of the uploaded file can be inspected on the Preview aspect view tab for the revision of the outputjob.
Drag and Drop from Windows Explorer
An Output Job Configuration file can also be uploaded by dragging the selected file from a source folder in your Windows Explorer, and dropping onto the required target Outputjob Item in the Explorer panel. The Create New Revision dialog will appear, with the dragged file listed in the Sources region. Modify Name (which will be the file name, including extension) and Description (which will be in the format Uploaded from <FileNameandPath>, Size <FileSize>, Created on <FileCreationDate>), and add any Release Notes as required, and then click the OK button.
If the existing Outputjob Item has no planned revision, upload will be to the next planned revision, created on-the-fly as part of the upload process. If you drop the dragged file away from an existing Item, a new Outputjob Item will be created. The
Create New Item dialog will appear. The
Name of the Item will be the file name, including extension. The
Description will be in the format
Uploaded from <FileNameandPath>, Size <FileSize>, Created on <FileCreationDate>. Change these as required. The
Item ID will be in accordance with the Item Naming scheme defined at the folder level. If the folder has no naming scheme defined, naming will follow the
$CONTENT_TYPE_CODE-{000000} scheme.
Uploading an OutJob file using the drag and drop method.
Reusing an Outputjob
Related page: Controlling Access to Workspace Content
Once an Output Job Configuration has been saved to a Workspace, and its lifecycle state set to a level that the organization views as ready for use at the design level, that configuration can be reused in future board-level design projects.
When you are connected to your Workspace, you are free to manually reuse the revisions of any outputjobs that have been shared with you.
If you do not connect to your Workspace you can still work with Altium NEXUS (under your valid Altium NEXUS license), but you will not be able to access your organization's Workspace, or any other services it provides. You will therefore not be able to reuse any Workspace-based outputjobs. You will only be able to use file-based configurations defined locally.
Choose a revision of an outputjob to use from the Managed OutputJobs tab of the Project Options dialog. Click the 
button – the Select configuration item (Output Jobs) dialog will appear, listing the latest revision of all outputjobs in the Workspace that are available to you (shared with you). Choose the required outputjob and click OK.
Manually choosing a revision of an outputjob from within the Managed OutputJobs tab of the Project Options dialog.
Continue adding further revisions of different outputjobs as required. After clicking OK to exit the Project Options dialog, the chosen outputjob(s) will appear in the Projects panel.
A Workspace-based OutputJob is distinguished in the
Projects panel by the
icon.
The added revisions of outputjobs will be reflected in the Projects panel.
In addition to using the Workspace-based outputjobs, you are also free to create and use local, file-based Output Job files, should this be required.
Reuse as Part of an Environment Configuration
A released Output Job Configuration can also be used as a configuration data item in one or more defined Environment Configurations. An environment configuration is used to constrain a designer's Altium NEXUS working environment to only use company-ratified design elements. Environment configurations are defined and stored within the Team Configuration Center – a service provided through the Workspace.
Once you have connected to the Workspace, and chosen (if applicable) from the selection of environment configurations available to you, Altium NEXUS will be configured, with respect to use of Output Job Configurations. If the chosen environment configuration has one or more defined outputjob revisions, then only those defined configurations can be used. If the chosen environment configuration applicable to you does not have any outputjob revisions specified/added, then these will remain manually definable. In other words, you are free to manually reuse a Workspace-based Output Job Configuration and/or use local templates. For more information, see Environment Configuration Management (for an Altium 365 Workspace or a NEXUS Server Workspace).
Under the enforcement of an environment configuration, Altium NEXUS will be configured, with respect to use of Output Jobs, in the following areas.
Project Options Dialog
Revisions of outputjobs are specified for use from the Managed OutputJobs tab of the Project Options dialog, in much the same way when reusing them manually. The difference with their use under management of an environment configuration is that you can only add those revisions of outputjob defined for that environment configuration.
- Click the button – the Select configuration item (Output Jobs) dialog will appear.
- Use the dialog to choose which OutJob to use for the project, from the list of outputjob revisions defined as part of the environment configuration currently in-force.
- Add additional outputjob revisions as required.
- With all outputjob revisions added as required, OK out of the Project Options dialog – the chosen outputjob revision(s) will appear in the Projects panel.
Creating a New OutJob File
While you are only able to reuse the outputjob revisions specified in the active environment configuration, you are still able to create new, file-based output jobs if required. Commands for creating a new OutJob – either using the File » New » Output Job File command, or right-clicking on a project's entry in the Projects panel and choosing Add New to Project » Output Job File, will therefore still be available for use.
Trying to use an Existing OutJob File
Under configuration management, and when at least one OutJob is defined for the active environment configuration, this will no longer be possible. If you attempt to add an existing Output Job File to the project, by right-clicking on a project's entry in the Projects panel, choosing Add Existing to Project, and browsing for that file, a warning dialog will appear – alerting you to the fact that Output Jobs are being managed by the applied environment configuration, and that existing Output Job files cannot be added to the project.
OutputJob Editor
The OutputJob Editor – accessed when opening a Workspace-based OutJob – will reflect that the file is a Managed OutputJob Document, with an indication of the Item Revision, its description, and the parent Workspace in which that outputjob resides.
The Output Job Editor when viewing a Workspace-based Output Job.
Since the OutJob is Workspace-based, any controls that would otherwise effect its modification in some way, are disabled. So the following abilities ARE NOT available:
- Addition of new Output Generators.
- Configuration of existing Output Generators.
- Cut, copy, paste, duplication or deletion of an existing Output Generator.
- Addition of new Output Containers or Hard Copy Jobs.
- Configuration of an existing Output Container or Hard Copy Job.
- Cut, copy, paste or deletion of existing Output Containers or Hard Copy Jobs.
- Toggle the inclusion state of an Output Generator with respect to a valid Output Container or Hard Copy Job.
You can, however, still determine variant usage for the OutJob.
Re-Saving an Outputjob
At any stage, you can come back to any revision of an outputjob in the Workspace, and edit it directly. Right-click on the revision and choose the Edit command from the context menu. Once again, the temporary editor will open, with the configuration contained in the revision opened for editing. Make changes as required, then save the document into the next revision of the outputjob.
Right-clicking on the top-level entry for an outputjob itself, will edit the latest revision of that outputjob.
Accessing the command to launch direct editing of an existing outputjob revision.
Updating an Outputjob
If you need to change the output job configuration stored in an Outputjob Item, and you have the updated OutJob file, you can upload that file to that Item – the new file will be stored in the next revision of that Item.
Downloading Saved Data
Download the data stored in a revision of an Outputjob Item by right-clicking on that revision and choosing the Operations » Download command from the context menu. The Output Job Configuration file will be downloaded into a sub-folder under the chosen directory, named using the Item Revision ID. The file can be found in the Released folder therein.
Access the Download command from the top-level entry for an outputjob itself, to download the Output Job Configuration file stored in the latest revision of that outputjob.
Click the Explore button in the Download from Server dialog, to quickly explore to the download folder.
Soft Deletion
When connected to a Workspace, flexible functionality is available for removing an outputjob directly from within Altium NEXUS, from the Explorer panel. Right-click on the outputjob's entry in the panel and choose the Delete Item command from the context menu. The Delete Items dialog will appear, in which to confirm the deletion. The action is actually a 'soft delete', whereby the outputjob will be moved into the Trash area of the Workspace. The Trash is essentially a recycle bin into which any content within your Workspace can be moved (through a soft delete action). It is isolated from the rest of the Workspace.
With the soft-delete facility, you are able to delete an outputjob that is currently being used.
Multiple outputjobs can be deleted in a single action. Select all required outputjobs using standard multi-select controls (Shift+Click, Ctrl+Click), then right-click and choose the Delete Items command from the context menu.
Soft deletion of an outputjob. The outputjob will be moved to the Workspace's Trash area.
To proceed with the deletion, click the 
button. The outputjob will be removed and a Deletion Summary dialog will confirm successful deletion. If there was an issue with deletion, this will be flagged to you.
All content deleted in this manner can be found on the Trash page of the Workspace's browser interface. Note that you can only view the content that you have personally soft deleted. Administrators will be able to see the full content of the Trash page – so all content that has been soft deleted.
Things to consider in relation to a soft deleted outputjob:
- The outputjob will not be available from your design software, or from within the Web interface.
- Anywhere the outputjob was being used will reflect that the outputjob has been deleted.
- An outputjob can be restored, or permanently deleted from the Trash page, provided you have editing rights. Permanent deletion is only possible provided it is not being used by a parent Item.
Note that if you have soft deleted an outputjob – moving it to the Trash – you can create a new outputjob with that same name again. If you were to subsequently restore the original outputjob, and the original name is taken, an integer suffix will be used, to keep its name unique within the Workspace.
