Freezing a WIP Revision as a New Model Version Revision

You can release a work-in-progress (WIP) revision that is stable enough to be used (for example, as an internal release) by other model versions by freezing it as a new revision.

Note: You cannot freeze a model version if it is in the Release or Obsolete state. Only the latest revision on a branch may be frozen as a new revision. To ensure this, the app checks that the selected revision is at the end of a branch (that is, that there are no revisions derived from it). If this is not the case, the command immediately fails and an error message is displayed.

The revision specified as the new revision may be an existing revision, provided that the specified revision is the one that the starting revision is currently derived from. This allows for the case where, for example, the latest revisions have been imported from DesignSync and the revision that needs to be frozen is the latest DesignSync version, which has already been imported as a revision that is the parent of this WIP revision.

Before you begin: Do one of the following:
See Also
About Defects and Defect Actions For WIP Revisions
  1. From the toolbar, select Actions > Freeze Model Version.
  2. Enter these details:

    FieldDescription
    RevisionThe name of the revision (for example, 1.42).
    TagA descriptive tag (for example, Gold).

  3. Click Done.
    The model version and all of its dependent model versions in the derivation chain are checked to ensure that there are no outstanding defects. Outstanding defects are those defect actions that are in either the Evaluate state (with a committed model version), the Open state, or the Test state. If there are outstanding defects, a warning message is displayed and you are prompted to confirm that you want to continue by clicking OK.

    If the number of defect actions found is below a certain minimum, then the name/revision and state of those defect actions is reported. If it is above the minimum, then a count is given. Your Business Administrator can specify this minimum using the emxSemiTeamCollab.OutstandingDefectReportLimit property.

If there are no outstanding defects, or there are but you confirm that you want to continue anyway, the new revision is created, linked into the derivation tree, and associated with the tag if one was specified. Once created, the defects attached to the original revision are re-attached to the new revision. The calling page either:

  • Displays the new revision, if the Freeze Model Version command was selected from the Actions menu for a model version revision.
  • Refreshes the display, if the Freeze Model Version command was called from the model version revisions table for a model.