發行管理

Onshape 發行管理為非阻塞模式，且直接建立在 Onshape 的設計與版本控制系統上，並不需要其他的產品、安裝或大規模的 IT 管理。會自動向您 Company 帳戶的所有使用者提供最新的工作流程設定，且更新也是完全自動的，因此不會有使用者用到過時平台的情況發生。

典型的工作流程是由找出要發行的物件開始，物件可以是零件、組合件、工程圖與其他匯入的檔案資料，然後將物件列為「發行候選」。取決於管理員所定義的工作流程規則，可以提交「發行候選」請求核准，或物件建立者可以立刻發行物件。

管理員可存取整體的 Company 設定，以定義每個發行的核准需求條件，並設定特定的條件來決定發行的有效與否。除了需要核准發行的使用者之外，也可將觀察人員指派給特定的發行，給予觀察人員檢視「發行候選」的權限但其無法或沒有責任核准或拒絕候選版本。這些類似的設定都可以根據公司的需求來加以定義。

Onshape 發行管理的其他主要面向包括：

• 使用者在等候「發行候選」核准的同時，仍然可以存取設計，絕不會被封鎖而無法編輯零件。團隊可以同時間繼續設計，無需等候核准者完成檢閱設計。
• There is never a question of "Do I have the latest changes?" Users receive notifications when a new revision of a released object is approved. Users are not notified when new versions of released objects are created, thereby preventing false notifications of updates.

  Enterprise users of custom multi-tier release workflows should keep in mind that notifications are sent within the tier the action takes place in. For example, when an approval in tier 2 of a multi-tier workflow is initiated, all approvers and observers in that tier are notified. No one in any other tier is notified except for the creator of the release; creators receives all notifications.

• 使用文件頁面原生的搜尋功能即可快速找出與存取已發行的物件，且可將物件與其他文件連結以在組合件、工程圖與 Part Studios 中使用。

Onshape 發行管理中使用的數個術語與概念對於了解這個強大工作流程工具組的細節是相當重要的：

• Version - A progress marker in the history of a document. Versions are immutable and capture the complete scope of a workspace at a particular point in time for future reuse or to revert a set of changes.
• Workspace - An active modeling/design space within a document.
• Active branch - The branch of the document in which the currently open version or workspace is located.
• History entry - A record of a change made to a document workspace at a particular point in time. You can compare history entries and restore the document to a particular history entry (point in time) through the context menu in the Versions and history panel.
• In progress - The default release state for unreleased workspaces and versions. Objects in progress are either fully editable (in workspaces) or have editable metadata (in versions).
• Pending - The state of a Release candidate (and its revisionable objects) while awaiting approval by one or more approvers.
• Rejected - The state of a Release candidate (and its revisionable objects) that one or more approvers chose to reject.
• Released - The state of a Release candidate (and its revisionable objects) that was either successfully approved by one or more approvers or was immediately released by its creator.
• Observer - Any member or members, or team of a company who needs to be informed of the status of a release, but whose approval is not required in the release workflow. Any number of observers (or none) can be included on a Release candidate. An observer must have view permission on the document in order to observe the Release candidate.
• Approver - A company member, members, or team whose approval is required in the release workflow. An approver has the ability to Approve or Reject a Release candidate. An approver must have permission to edit the document in order to approve or reject a Release candidate.
• Revisionable object - Any part, Assembly, Drawing, Variable Studio, and file in an Onshape document can be revisioned and released in Onshape.
• Release candidate - A user-selected group of revisionable objects that moves through the release workflow together. A Release candidate may contain a single part or an entire product including parts, Assemblies, Drawings, Variable Studios, and other files.
• Not revision-managed objects - Objects that may need to be included in a Release for reference purposes but whose revisions do not need to be tracked. You can mark entire Part Studios, Assemblies, Drawings, Variable Studios, parts, and files as Not revision-managed. Keep in mind that setting the entire document as Not revision-managed includes all parts.

Onshape Release management is integrated directly into Onshape's underlying version control system. The Release workflow starts in a workspace where all parts, Assemblies, Drawings and other revisionable objects are editable and have, by default, an In progress state.

During the design process, you may create any number of versions to mark your progress.

從進行中的工作區或版本中建立發行時會提示您填入一個「發行候選」。完成之後，取決於公司定義的工作流程設定，您可以送交「發行候選」以供核准，或是立即發行。

When a Release candidate is submitted for approval, a version is created, the version is automatically named for the Release and marked with an open triangle icon in the Version and history graph. The state of the revisionable objects within the Release candidate is also set in the version, to Pending.

When a Release candidate is approved (released), the version is marked with a solid triangle, , and the state of the revisionable objects within the Release candidate in the version are set to Released.

Similarly, if one or more approvers rejects the Release candidate, the version is marked with an open triangle, , and the revisionable objects within the Release candidate reflect a state of Rejected.

If one or more objects in the Release are obsoleted, the version is marked with a solid triangle with a dot, , and the obsoleted objects within the Release reflect a state of Obsolete.