Enabling Non-Versioning Documents

You can allow non-versioning document object types in your apps. A non-versioning document type does not get versioned and therefore has no version identifier: all file check-in and check-outs are performed directly on the object instead of creating versions.

By default, all object types derived from type DOCUMENTS are assumed to be "versioning" documents and can be configured to be non-versioning.

Non-versioning types have these limitations:

  • If a user tries to check out a file, all files present in the Document object are locked. If a user checks-in a file, all files are unlocked at a time.
  • There is no update available for non-versioning types.
  • If a user tries to check in locked files, the Check-In page has 5 text fields with browse buttons next to each field, but none of the Checked-Out file names are displayed over the text fields on the Check-In page.
  • On the Check-In page, the Comments text field is not displayed for each file on the page.
  • Selective multi-file download/checkout is not available for non-versioning types. Download and Checkout commands in the Action drop-down menu are enabled without selecting any check box.
  • Non-versioning object files can be downloaded/checked out one file at a time or collectively as a zip file.

  1. Open the Run MQL window:
    1. From the compass, select Collaboration and Approvals.
    2. In the navigation pane, click Utilities > Run MQL.
    To run an MQL command, enter the command in the MQL Command box and click Run or press Enter.
  2. To set the context for the MQL session, run this command:

    set context user creator;

  3. To make a document object type non-versioning, run this command: 

    modify type 'Type Name' property DISALLOW_VERSIONING value True;

    For example: 

    modify type 'Eng Specification' property DISALLOW_VERSIONING value True;

    If the same file name is checked in, an append is performed and the user will receive a message stating the file name exists with an option to override.

    Dassault Systemes recommends that you first create a document type and then set it to disallow versioning. If you set existing versioning document objects to disallow versioning, you could have some objects of the same type with versions and some without versions.

    The DISALLOW_VERSIONING property can only be used with types derived from the DOCUMENTS type.