Workspace Projects

Now reading version 2.1. For the latest, read: Workspace Projects for version 5.0

This documentation page references NEXUS Server (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer and a connected Altium 365 Workspace. Check out the FAQs page for more information.

 

Parent page: Altium NEXUS Server

Altium NEXUS, in conjunction with the Altium NEXUS Server, brings support for Managed Projects. Managed Projects target the development stage of the project lifecycle, simplifying the creation and ongoing workflow for version controlled projects. Centralized storage under the control of the Altium NEXUS Server also enables this feature to be a foundation for other collaborative services.

Some key benefits to using Managed Projects are:

  • Simplified storage. No need to make decisions about storage locations. Backup and other basic services are taken care of.
  • Foundation for collaborative features.
  • Enforced version control.
  • Advantages of a dedicated commenting system.
  • Notifications and status. Document status including local modifications is visible to entire design teams.
  • Concurrent PCB design works without any complex setup.

Technically a Managed Project is the combination of meta information stored on the server, along with tight integration with the NEXUS Server's own Version Control service. The typical work flow is as follows:

  1. A user creates a new managed project via the NEXUS design client's Create Project dialog, from the NEXUS Server's browser-based interface, or by converting an existing project on the design client side. During creation, that user defines the project's name, description, and design repository.
  2. Access to the project is defined and managed in the NEXUS Server's browser-based interface, or directly within the NEXUS design client.
  3. All collaborators select the project for opening (either from within design client or from the server's browser interface) after which it is automatically checked out as design files.
A major advantage of Managed Projects is that they are version controlled by default, and can be collaboratively worked upon without having to worry about shared drives, servers, agreements etc.
Prior to creating a new Managed Project, or converting an existing non-managed project, ensure that a Design Repository exists in which to store that project, and all future projects. Design Repositories are centrally managed as part of the Altium NEXUS Server, through its Version Control service. A new installation of the NEXUS Server provides a single Git-based design repository – Versioned Storage – for accommodating all of your managed design projects. If you have upgraded your Server from NEXUS Server 1.0 (or Altium Vault 3.0) then use of SVN repositories will also be enabled, so that you can continue to use your previous (and established) design flow. In this case, you can create additional repositories through the server's Version Control service (SVN-only), or connect to external repositories (SVN or Git).

Creating a New Managed Project

There are three main ways in which a Managed Project can be created:

  • Creation of a new project from the NEXUS Server's browser-based interface, or from within the NEXUS design client.
  • Making an existing, non-managed project available on the Server from within the NEXUS client – that is, converting an unmanaged project to a managed project.
  • Cloning an existing Managed Project through the NEXUS Server's browser-based interface, or by cloning a project from the NEXUS client Projects or Explorer panels.

The following sections take a closer look at these methods of creating a Managed Project.

Through the NEXUS Design Client

From within the Altium NEXUS design-side client, a new Managed Project can be created using the Create Project dialog (File » New » Project):

If at least one process definition for the Project Creations process theme is active – on the Project Creations tab of the Processes page of the NEXUS Server's browser interface – the server will not be available as a target in the Create Project dialog's LOCATIONS list.

Instead, server-based managed projects are created using one of the process definitions that are available from the File » New » Managed Project sub-menu.

  1. Select the entry for your NEXUS Server from the dialog's LOCATIONS options (it will appear with the name you have specified for it, on the Admin – General page of the server's browser interface) – you must be signed in to the NEXUS Server with administrator privileges to access the server naming option.
  2. Enter a Project Name in the Create Project dialog and optionally, a project Description.
The project name should start with, and can contain A-Z, a-z, or 0-9. Underscores, dashes, and spaces are allowed, but the latter can only be used within the middle of the name (leading and trailing spaces will be ignored). You can not use the following words: AUX, COM1-COM9, LPT1-LPT9, CON, NUL, and PRN. In addition, the name cannot contain the following characters: \ . / ? % * : | " < >.
  1. The Project Type column allows you to select the type of project that is being created, and if an available Project Template will be used. The list of templates for each project type includes all compatible Project Templates that are available in the server.
  2. The Repository field will list all Design Repositories managed through the NEXUS Server's Version Control service, and which have been shared with you to use. Choose the repository in which to store the new project and its files – there is a single Git-based repository (Versioned Storage) available by default.
  3. Use the Folder field to specify where the folder for the project – within the server's folder structure – is to be created. The default path for new NEXUS Server projects is specified on the Admin – Settings – Projects page of the server's browser interface.
  4. Use the Local Storage field to specify where the project will be stored on your hard drive, prior to its committal to the centralized Design Repository. The default location is defined in the System – Default Locations page of the Preferences dialog.
  5. Use the  button to add parameter Name-Value pairs to the Parameters list. These Managed Project parameters are saved in the server with the new project, and can be edited within the server. By contrast, Project type parameters are saved in the project file (*.PrjPcb), and can be edited on the NEXUS design side. Both parameter types may be used as Special Strings in the design client.
The button associated with each entry can be used to browse to and select an alternative path/repository.

Setting up to create a new Managed Project from within NEXUS, courtesy of the New Project dialog. Note that only those central Design Repositories
that are shared with you will be available for selection from the Repository field.

After clicking , the new project will be created locally, in accordance with the defined Location. The project will be opened in the Projects panel, which will show the project as being Scheduled for addition, denoted by the associated  icon.

The project will appear in the Projects panel under an entry for the target Server, reflecting the name of that Server.

Right-click on the project in the Projects panel and choose the Commit Project command or the Version Control » Commit Whole Project command. You will be presented with the Commit to Version Control dialog. Select the files you wish to commit to the Design Repository and click Commit and Push (or Commit for a target SVN repository). Once added, the Projects panel will reflect the fully synchronized state that exists between the files in the server repository and the local working copy, as indicated by the icons.

Commit the newly created Managed Project to the target Design Repository. Commit the newly created Managed Project to the target Design Repository.

In addition, an entry for the project will appear on the Projects page of the NEXUS Server's browser interface.

The newly-created Managed Project, evident on the Projects page of the server's browser interface.The newly-created Managed Project, evident on the Projects page of the server's browser interface.

The project will initially be shared for Read/Write access with the designer who created it and all Administrators for the NEXUS Server. The project will also be shared to all server users, but with Read-only access. For more information on configuring project access permissions, see Sharing a Managed Project.

Through the NEXUS Server Browser Interface

A Managed Project can be created directly through the Altium NEXUS Server's browser interface:

  1. Sign in to the interface and access the Projects page. Any previously created projects will be listed here.
  2. Click the  button at the top-right of the page. The Add Project pop-up window will appear.
If there are any active process definitions available for the Project Creations process theme – defined on the Project Creations tab of the Processes page of the server's browser interface – then this button will appear as  . Click to access and choose the required process. The corresponding workflow for the chosen process will then be invoked.
  1. The window will initially present in simplified view. Enter the desired name for the project, a description (if required), and, if available, choose from any Managed Project Templates that exist in the NEXUS Server.
The project name should start with, and can contain A-Z, a-z, or 0-9. Underscores, dashes, and spaces are allowed, but the latter can only be used within the middle of the name (leading and trailing spaces will be ignored). You can not use the following words: AUX, COM1-COM9, LPT1-LPT9, CON, NUL, and PRN. In addition, the name cannot contain the following characters: \ . / ? % * : | " < >.
  1. To access more controls – putting the window in advanced view – click on the Show additional fields control. The following fields will present:
    1. Server (Vault) Folder – use this field to specify where the folder for the project is to be created within the server's folder structure. By default, this will be Projects\<ProjectName>. The default path for new projects is specified on the Admin – Settings – Projects page of the NEXUS Server's browser interface.
    2. Project Type – use this field to specify the type of project from a list of all project types supported by Altium NEXUS. If you have selected a managed Project Template to use, this field will not be presented.
    3. Repository – this field will list all Design Repositories managed through the Altium NEXUS Server's local Version Control service, and which have been shared with you to use. Choose the repository in which to store the new project and its files. By default, the Versioned Storage (Git-based) repository will be selected.
    4. Repository Folder – use this field to specify the name of the folder within the repository in which to accommodate the project and its associated files. By default, this will take the project's name. If the Versioned Storage (Git-based) repository is chosen, this field will not be presented.

Defining a new Managed Project directly through the NEXUS Server's browser interface.Defining a new Managed Project directly through the NEXUS Server's browser interface.

After defining the new project as required, click  – the new project will be created. You will initially be taken to the detailed view for the project (more on this below) Click the Projects entry in the navigation tree to come back to the summary-level listing of managed projects, where you will now see that an entry for your newly-created project has been added to the list.

An additional Managed Project, created through the browser interface. Click the Projects entry in the nav tree to switch back from the detailed project view to the summary-level view.An additional Managed Project, created through the browser interface. Click the Projects entry in the nav tree to switch back from the detailed project view to the summary-level view.

The project will initially be shared for Read/Write access with the designer who created it and all Administrators for the Altium NEXUS Server. The project will also be shared to all server users, but with Read-only access. For more information on configuring project access permissions, see Sharing a Managed Project.

Conversion of an Existing Non-Managed Project

You can also create a Managed Project from an existing non-managed one by converting the latter to the former. To do this, open the existing non-managed project as normal in the NEXUS design client, then right-click on its entry in the Projects panel and use the Make Project Available on Server command from the context menu.

If at least one process definition for the Project Creations process theme is active – on the Project Creations tab of the Processes page of the NEXUS Server's browser interface – the Make Project Available on Server command itself will not be available in the NEXUS design client.

Instead, the command entry presents a sub-menu that offers those active process definitions from which to choose. The corresponding workflow for the chosen process will then be invoked.

If the project is currently under Version Control in a local Design Repository, it can not be converted directly. A message will alert you to this, with the option to essentially convert the project to a Regular project first – ignoring SVN revisions and changes log – and then converting that Regular project to a Managed one.

The Make Project Available on Server command opens the Make Available on Server dialog, which allows you to determine the project's name and its description. By default, the name will be that of the original (source) project.

Further setting are available by opening the Advanced options:

  • The target design Repository in the NEXUS Server that you are currently signed into. Choose from all managed repositories shared with you, and that are defined through the server's Version Control service (on the VCS page (Admin – VCS) of the server's browser interface). By default, the Versioned Storage (Git-based) repository will be selected. Note that if you are converting a VCS-type project, and that project already exists in an SVN design repository provided by the Server, then that same repository will be used – you will not be able to choose a different one.
  • The Repository Folder within an SVN repository when this type is selected. This option is not available when the default Versioned Storage (Git-based) repository is used.
  • The server Folder entry represents the target path for the new project entry within the server's folder structure. By default this will be Projects\<ProjectName> but may be edited to suit, where the server Folder setting will also define the location in which data for the project will be released when using the NEXUS client Project Releaser.
The button associated with each entry can be used to browse to and select an alternative path/repository.

Convert an existing project to a Managed Project.Convert an existing project to a Managed Project.

With the properties for the Managed Project defined as required in the Make Available on Server dialog, click OK. The project and files will be committed to the target Design Repository, with the Projects panel reflecting the fully synchronized state that exists between the files in the repository and the local working copy – as indicated by the icons.

The newly-converted Managed Project will subsequently be available from the Projects page of the NEXUS Server's browser interface.

The converted project is added to the list of centrally-managed projects.The converted project is added to the list of centrally-managed projects.

The project will initially be shared for Read/Write access with the designer who converted it and all Administrators for the Altium NEXUS Server. The project will also be shared to all server users, but with Read-only access. For more information on configuring project access permissions, see Sharing a Managed Project.

Browsing Managed Projects

Managed Projects are available to browse from the Projects page of the NEXUS Server's browser interface.

The Projects page of the NEXUS Server's browser interface.The Projects page of the NEXUS Server's browser interface.

Each project is listed in terms of the following information:

  • Name – the name of the project, along with its description (if defined).
  • Author – the user who created the project.
  • Last modified – the date on which the project was last modified.
The list of managed projects is automatically sorted by Last modified date, with the most recently modified project appearing first in the list. The list can be sorted by any of these data columns – click once within a column header to sort in ascending order, click again to sort in descending order.

For each project, the following controls are provided (and detailed in the linked sections that follow):

 Open – open the project via its detailed view.

 Edit – edit the project in terms of its Name and/or Description.

 Share – access controls with which to configure project access permissions.

 Remove – remove the project from the server.

Detailed Project View

Clicking the Open control ( ) associated with a managed project or its its name will give you access to a detailed view of the Project.

Accessing the detailed view for a managed project.Accessing the detailed view for a managed project.

This view of a project can also be accessed within Altium NEXUS, through the Explorer panel. It is the default view style, available once the project has been released to the NEXUS Server. If you are viewing your project-related Items in the Classic View, you can switch to this detailed view by clicking the  button at the top-right of the panel, and choosing Project View from the associated context menu.

The following tabs are available within the project detail view:

  • Parameters – a listing of parameters (as Name/Value pairs) associated with the Managed Project that are grouped under three parameter type headings:
    • Project file – parameters stored in the project file (*.PrjPCB) that can be added/modified through the Project Options dialog in Altium NEXUS.
    • Managed project – parameters stored in the server with the Managed Project that can be added in the Create Project dialog in Altium NEXUS, or added/modified by editing the project in the server's browser interface.
    • Analytics – parameter data automatically extracted by the NEXUS Server from the Managed Project.

The Project and Server -type parameters will be available to use as special strings in Altium NEXUS – access from the Properties panel with a placed Text String selected in the design workspace. Parameters defined for the project can also be viewed on the Parameters and Server Parameters tabs of the Project Options dialog (Project » Project Options).
  • Preview – an interactive graphical preview of the design source. Zoom, pan and double-click entities in the main preview window to navigate around the design. The preview screen supports the display of both Schematic and PCB documents, where the latter also offers Layer selection () and 3D view () capabilities. The Preview features are a subset of those available in the Browser-based Web Review.

The Preview functionality is also available under the Releases tab (as outlined below), where the Schematic and PCB previews will apply to the currently selected Release (shaded blue).

  • Part List – a simple listing of all managed components in the design, as automatically extracted from the design source by the server. This includes the Item ID and revision status for each server component used in the design.

  • Working files – the source design files of the project, which can be downloaded in a single Zip file.

  • Releases – presents every release of the project, with the latest release at the top of the list. Each entry on the left shows a snapshot of the date/time of release, along with what packages are included in the release. Use the Search field to quickly find a specific release (very useful if you have released the project many times).

As you click on a release summary entry on the left, the following sub-tabs on the right populate with information that applies to that specific release:

The currently selected release can be downloaded by clicking the  control, to the far right of the tab. The Download Configuration pop-up will appear, with which to specify what data you wish to include in the download (e.g. source, fabrication and any assembly packages).

Once you have configured the download as required using the available check boxes, click the  button. A master zip file will be downloaded to your browser's default downloads folder (named according to the format: SRC-<ProjectName>-<ReleaseRevision>(<IncludedPackages>).zip, for example SRC-WiFi_miniPCIe-2(pcba,fab,src).zip. This contains individual zip files of the packages selected for download.

You can also initiate a Web Review for the currently selected release of the project (highlighted in blue). Click the  control to open a Web Review instance in a new browser tab.

  • Stream – detailing recent activity for the project.

  • Activities – a listing of activities associated to the project. A designer can start a dedicated activity for a managed project using predefined Project Activity process workflows that have been defined for the company. Available Process Workflows can be initiated from the Altium NEXUS design client, the server Process Management page (Admin » Processes), or from the  button menu available on the opened project page – as shown above.

Under the Activities tab, select the Active option to see processes that are currently running or the Closed option for those that have been previously run (not active) – or search for a specific activity of interest. Click on a listed entry to view a diagram of its underlying process workflow (on the Diagram tab below the list), showing what needs to happen for the activity to be completed, and where the activity is at along that flow, in terms of who now has a task to perform to move the activity along. Tabs are also available for seeing the data attached to the activity (Data tab), and also a history of actions taken along the activity's process workflow (History tab).

For a NEXUS Server administrator, the ability to terminate an active process is available – click the  control.

The user that a process activity is assigned to – the Assignee – can access and act on the workflow from the server's Task Management page (Admin » Tasks), or from the Tasklist panel in the Altium NEXUS design space.

Additional reporting features are available through a CSV export function for Activities. Available to users in the Administrators role group, the CSV export button ( ) creates a detailed comma-delimited *.csv report file which includes all Activities (Process Workflows) that are currently listed. Both Active or Closed Activities can be exported, and the list may be filtered using the process name Search field. The function is also available in the NEXUS client Explorer panel.

► See a server Activites Export example.

Project Functions

A number of general controls are also available for (and apply to the latest revision of) the open project:

  • VCS Location – the URL to the project inside its parent design repository. For a project stored in an SVN-based design repository, click this link to open that design repository, in which the project resides, in your external SVN client browser.
  • – this button is available if the server detects that the existing project structure is incompatible with the server's advanced data analysis and generation capabilities. This will be the case for managed projects that were created in server versions prior to Vault 3.0. The button, which is available to administrators only, is used to convert the structure of the 'legacy' projects to work with current NEXUS Server. Expand the section below for more information:
  •  – click this button to open the project within Altium NEXUS (by opening the X2.exe file). If the design software is already running, the project will be opened in that instance.
  •  – click to initiate a project Web Review, which will open in a new browser tab.
  •  – click to choose from and start any available process workflow from the drop down menu.
    Three predefined process definitions for Project Activities are activated for use out-of-the-box (Ad Hoc Review, Handoff Review, and Milestone Review). These can be found on the Project Activities tab of the Processes page of the NEXUS Server's browser interface. Use these, modify them, or create your own as required, to suit the needs of project-related activities within your company. In addition, more sample process definitions are available relating to publishing of content to a PLM – Publish to PLM (User selects), and Project Releaser with Publish. These cannot be activated and used as is. Each of these is therefore more like a 'template' – edit to suit your company's PLM, name, and save as a new process definition, which you can then activate and use, along with all other definitions in the Project Activities process theme.
  •  menu – select this menu to expose the additional functions for a released project, which include:
    • Edit – select to access the Edit Project window. From here, you can change the project's Name, Description and any applied server Parameters. All other fields are non-editable, providing information only.
    • Share – select to access the Manage Permissions window, with all the controls necessary to share the project with other users. See Sharing a Managed Project for more information.
    • Clone – select to access the Clone Project window, providing the controls to make an identical copy of the project. See Cloning a Managed Project for more information.
    • Watch – select to follow the project. You will receive applicable notifications related to the project (e.g. updated, released, permission changes) on the project's Stream tab, as well as the main Home and Stream pages of the browser interface. The creator of the project will automatically be set to watch that project. Select the option again to stop following the project and receiving notifications.
    • Remove –select to remove the project from the repository, rendering it no longer managed. If you have checked out the project locally, you will still have this local working copy.

Project Data Update

When a project has been externally updated, say after being edited in Altium design software and the changes committed back to the NEXUS Server, the server will automatically re-process the project data to update detailed information such as Parameter Analytics and the extracted Part List.

After a substantial project update has been committed to the server, the project's detailed view may include a progress warning as the data is updated. Once complete, the message will request a page refresh to display the new data – click the offered refresh link or press F5 to update the page.

Sharing a Managed Project

Once a project is managed, you'll want to determine which users can actually access that project. This is done by sharing the project, or rather, by configuring its access permissions. Remember that a managed project – newly created or converted – is shared, by default, with the following:

  • The designer who created (converted) the project: full (Read/Write) access permissions.
  • The Administrators role group: full (Read/Write) access permissions.
  • All server Users – denoted by the presence of the Anyone entity: with Read-only access permissions.

Configuration of access permissions can be performed through the NEXUS Server's browser interface, and also directly from within Altium NEXUS.

From within the NEXUS Server's Browser Interface

To configure access for a project from the NEXUS Server's browser interface, from the Projects page of the interface click on the project's associated Share control ( ).

Also available by clicking the  button, from the detailed Project view.

The Manage Permissions window will appear, with all the controls necessary to share the project with other users.

With projects centrally managed in a NEXUS Server, sharing with others is simply a case of managing each project's permissions.With projects centrally managed in a NEXUS Server, sharing with others is simply a case of managing each project's permissions.

Things to be aware of:

  • In terms of permissions, a user/group has Read/Write access when the Can Write option is enabled. If this option is disabled, they have Read access only.
  • To remove an existing user/group from having shared access to a project, click the associated Remove control ( ).
  • All users of the NEXUS Server will by default be able to see the project. If you want to lock access down to a specific set of users and/or groups, you must remove the Anyone entity.
  • If you remove the Anyone entity, it can be added back again using the Add Anyone control. Be aware that doing so will, by default, grant Read/Write access of the project to all NEXUS Server users.

From within Altium NEXUS

Access for a project can be configured directly from within Altium NEXUS by using the Share command. This command can be accessed for the active project, or a focused project:

  • Active project – with a source document for the project open as the active document, choose the Project » Share command, from the main menus.
  • Focused project – access is made from the Projects panel by right-clicking on the entry for the required project and choosing the Share command, from the context menu.

The Share For – <ProjectName> dialog will open in which you can configure sharing as required.

Configure access to your Managed Project directly from within Altium NEXUS.Configure access to your Managed Project directly from within Altium NEXUS.

Opening a Managed Project

To work on a managed project, you effectively check it out as a local working copy. This can be performed in two ways:

  • Directly from within Altium NEXUS – use the File » Open Project command. The Open Project dialog will appear, from where you can choose which managed project to open from the NEXUS Server. Only those Managed Projects that have been shared with you (you have permission to access) will be listed, and from across all managed Design Repositories shared with you.

Choose which managed project to open, from within Altium NEXUS, from those currently shared with you.Choose which managed project to open, from within Altium NEXUS, from those currently shared with you.

You have the option to open the project to the default checkout path, or use the  drop down menu to specify a custom path. The default checkout path is taken from the Document Path field, on the System – Default Locations page of the Preferences dialog.
  • From the Projects page of the NEXUS Server's browser interface – click the Open control ( ) associated with the project. From the detailed view for the project that is then presented, click the  button.
After clicking the  button, a dialog will appear asking for confirmation to open the DXP Protocol – the Altium NEXUS underlying executable. Click the Open URL:DXP Protocol button to open the project in the running instance of Altium NEXUS (or to launch the last used instance of Altium NEXUS). Check the 'Always open...' box to avoid this step in the future.

Access the control to open a managed project from its detailed view within the NEXUS Server's browser interface.Access the control to open a managed project from its detailed view within the NEXUS Server's browser interface.

Editing a Managed Project

To edit the properties of a Managed Project at a later stage, click its associated Edit control ( ).

Also available by selecting the Edit option from the  menu in the detailed Project view.

The Edit Project window will appear. From here, you can change the project's Name, Description and server Parameters. All other fields are non-editable, providing information only.

You can edit the Name, Description and Parameters for a Managed Project at any stage.You can edit the Name, Description and Parameters for a Managed Project at any stage.

Cloning a Managed Project

To clone an existing managed project, access its detailed Project view and then select the Clone option from the  menu. The Clone Project window will appear.

If there are any active process definitions available for the Project Creations process theme – defined on the Project Creations tab of the Processes page of the NEXUS Server's browser interface – then the  menu will offer Clone (process) options that correspond to the available process workflows. When selected, the defined workflow for that process will be invoked.

You can clone a managed project – creating an identical copy of it, along with its working files.You can clone a managed project – creating an identical copy of it, along with its working files.

Use the Clone Project window to set the naming, description and storage paths for the cloned project. By default, the original project name will be used with the suffix ' – Copy'.

The cloned project will be made in the same design repository as the original – you cannot change this as part of the cloning process.

After setting the fields as required, click the  button – the original project will be cloned, and the clone opened within the interface at the Parameters tab of its detailed Project view.

Removing a Managed Project

To remove a Managed Project, click its associated Remove control ( ) in the Projects page listing.

Alternatively, in the detailed Project view of the project select the Remove option from the  menu.
If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.
Content