Build Lists

This chapter covers the concepts of build lists, the Build Lists pane, and how to create/edit build lists in Capital Teamwork.

Build Lists Overview

A build list is a container for designs, representing a subset of a vehicle's connectivity and topology at a single point in the design life-cycle. Any number and configuration of build lists may be created for a project.

Capital Teamwork supports five types of build list: Analysis, Function, Harness, Logic, Topology. Once you specify a type for a build list, you can add only designs of that type — the build list type cannot be changed.

A build list can only contain one design revision from each of a project's designs (e.g., you cannot select design 1/revision a AND design 1/revision b in the same build list, but you can select design 1/revision a AND design 2/revision a).

Deleting a build list has no effect on the designs listed in that build list.

Build Lists Tabs

The Details pane for the Build Lists workflow contains the Build List Type dropdown (Analysis, Function, Harness [default], Logic, Topology). Below the Filter field, build lists in the selected project are listed. Icons let you search, create a new manual or plugin-driven build list, copy a build list, and toggle list/table view.

Selecting a build list shows tabs: Details, Designs, Attachments, Properties. Icons also let you release/delete the build list, download VEC and xHCV data, or run DRCs on demand.

Tip: Downloaded xHCV data includes the harness design configurations associated with the build list, and any reported DRC failures and created Issues. Additional content (e.g., ELOG packages) can be associated to the xHCV data via a plugin.

Details Tab — attributes:

• Name — Unique identifier of the build list.
• Release Status — Current release level; dropdown lets you select the next transition level (per the "Design Attribute Changes" behavior).
• Description — Comments/notes.
• Abstraction — Restricts designs addable to the build list based on Design Abstractions; can configure a dynamic build list to contain only designs with a specific abstraction. Additional column names correspond to attributes/properties configured for the Details tab.

You can filter columns (Filter icon) — see "Filtering Tables." Add/delete designs — see "Editing Build Lists." Note: Add/Delete icons are unavailable for plugin-driven build lists (list determined by plugin).

Attachments Tab — Attachments as supporting info; synchronized files from third-party apps shown by default. Columns: Name, Type, Key, Modified, User Prop (up to 4 additional user properties configurable in buildlistconfig.json — see "Configuration JSON Files"). Filter via Filter/Dropdown icons — see "Filtering Tables." Add/delete via icons — see "Using Attachments."

Tip: File sizes up to 300 MB; edit buildlistconfig.json for larger files.

Properties Tab — User properties specified in the source application; delete/add as Name/Value strings — see "Using Properties."

Using Build Lists

Covers creating/editing manual build lists and configuring a plugin to auto-populate a build list.

Restriction: Refresh the web page or start a new Capital Teamwork session to activate domain access modifications. Without domain access to a build list, it displays in the workflow but you cannot view designs, edit it, or select it as an Issues container. See "Domain Restricted Visibility" in the Capital Access Manager User Guide.

Copying a Build List

Reuse an existing build list (design associations, attachments, properties) as a base for a new one. Copy actions are available in List and Tabular views.

Restrictions:

• Cannot use Copy Latest on plugin-driven or dynamic build lists (revisions are plugin/Dynamic-flag driven).
• If Edit Attached Data permission is cleared, attachments copy but cannot be created/deleted in the new build list.
• If the Build List Editing behavior is not on the Draft release level, the transition applies the next release level that includes it. If no release level includes Build List Editing, you cannot copy.

Prerequisites: Build Lists permission assigned (see "Edit Project User Permissions" in Capital Access Manager User Guide); project has one or more build lists.

Procedure:

1. Build Lists workflow → select the source build list.
2. Click Copy Build List (copies all design revisions as-is) or Copy Latest Build List (updates revisions to the latest in the Capital database).
3. The new build list shows copied Designs, Revisions, Dynamic flag/Effectivity values, Folder container and Abstraction, Release Status = Draft by default, and (for plugin-driven) the generating plugin.
4. Type a unique name, optional description, modify Designs/Attachments/Properties tabs as needed.
5. Click Create.

Related: "Creating a Build List Using Effectivity" (Capital Project Manager User Guide), "Creating Plugin-driven Build Lists," "Engineering Change Orders" (Capital Design Tools - Common Functions User Guide), "Release Level" (Capital Project Manager User Guide).

Creating a Manual Build List

Create a build list and add Capital or third-party designs manually.

Restrictions: No backslashes in new folder names. If a Design Abstraction is assigned, you cannot save a build list containing designs with different abstractions, nor add designs with different abstractions.

Prerequisite: A project is selected.

Procedure:

1. Build Lists workflow → Build List Type dropdown → choose Analysis / Function / Harness / Logic / Topology (only designs of this type can be added).
2. Click Create New Build List icon.
3. Specify attributes/properties (mandatory fields marked *). Release Status defaults to Draft.
4. (Optional) Choose an Abstraction to restrict addable design types.
5. (Optional) Set Folder (existing or new name; browse via ellipsis).
6. Click Designs tab → Add icon → Select Designs dialog.
7. (Optional) Use Search Criteria icon to filter by Abstraction etc.; browse Folder via ellipsis; check Include Child Designs to search derivative/module designs; click Search/Reset/Cancel.
8. Filter the table if needed (see "Filtering Tables"); select designs → Insert.
9. Click Create.

Result: Build list name appears below the Build List Type dropdown and in the Designs folder in Capital Project Manager.

Creating Plugin-driven Build Lists

Configure a plugin to populate the build list with designs automatically — run at intervals via an FEM task, during data sync, or manually via the Create plugin build list action.

Restriction: No backslashes in new folder names.

Prerequisite: A plugin created using the Build List Content Provider interface.

Procedure:

1. Build Lists workflow → click Create New Build List from plugin icon.
2. Specify attributes/properties (mandatory *; Release Status defaults to Draft).
3. Set Folder (existing/new; browse via ellipsis).
4. Choose a plugin from the Plugin dropdown — this enables the Plugin driven design list check box.
5. Ensure the check box is selected so the plugin populates designs.
6. Click Create.

Result: Build list name appears below the Build List Type dropdown and in the Designs folder in Capital Project Manager.

Configuring an FEM Task to Run Build List Plugins

Use parameters in capital_install\config\buildlist_content_update_task_configuration.xml to auto-run build list plugins at regular intervals and on each Integration Server start:

<BuildlistContentUpdateTask autoschedule="false" cronexpression="0 0 0/6 1/1 * ? *" store_logs_per_execution="true">

Procedure:

1. Set true/false to activate the plugin on Capital Integration Server startup and to store a log per run.
2. Edit cronexpression to set run intervals.

Converting Dynamic Build Lists to Static Build Lists

If a dynamic build list is frozen and no further automatic updates are needed, convert it to static and continue to add/remove designs manually.

Restriction: This conversion is irreversible.

Prerequisite: The project contains one or more dynamic build lists. See "Build Lists and Effectivity" (Capital Project Manager User Guide).

Procedure:

1. Select the dynamic build list — Designs tab is read-only (Add/Delete unavailable). You can still filter designs and edit Details/Attachments/Properties tabs. The Effectivity value on Details is read-only.
2. Clear the Dynamic check box → Confirm dynamic behavior change dialog → click Proceed (implied).
3. Add/Delete icons become available on the Designs tab for manual editing. The Effectivity value remains read-only.

Related: "Editing Designs," "Filtering Tables," "Using Attachments," "Using Properties."

Editing Build Lists

Manually add/delete designs from a build list; refresh or save a plugin-driven build list as manual.

Restriction: Cannot add/delete designs in a plugin-driven build list (plugin-determined).

Prerequisite: A build list is selected below the Filter field.

Procedure (choose the action):

If you want to...	Do the following...
Download VEC or xHCV data	Select the build list → click Download VEC or Download xHCV icon. Accept/Cancel the Confidentiality Disclaimer if configured (accepted once per session — see "Configuration JSON Files").
Delete a build list	Click the Delete icon → confirm Yes/No.
Add a design to a build list	Designs tab → Add icon → Select Designs dialog → choose designs → Insert → click Update.
Release a build list	Click the Release icon → confirm Yes/No. Release Status updates and all open Issues related to the build list are closed.
Delete a design from a build list	Designs tab → choose designs → Delete icon → click Update.
Assign/edit a Design Abstraction	Abstraction dropdown → choose an abstraction to restrict addable design types.
Edit the build list's folder location	Folder field: specify existing or new folder name; browse via ellipsis.
Edit the Properties tab	See "Using Properties."
Refresh data in a plugin-driven build list	Designs tab → Refresh icon.
Save a plugin-driven build list as manual	Details tab → clear Plugin driven design list check box (preserves existing designs as manual) → click Create.
Run a manual DRC on designs in the build list	Click Submit DRC Task icon. A message confirms submission; the Validated On date on Details updates when complete. See "Batch DRC Run" in "Issues Overview" for release-level-specific DRC runs.