Behavior Changes - ReadOnly Attribute

This section lists the behavior changes in several collaborative products and Designer Central features when MCADInteg-FileReadOnlyBehavior is set as TRUE.

Behavior Change on Checking in a File

This section describes the behavior change when checking in a file, depending on whether you checkKeeped Checked Out in the ENOVIA Check In dialog box.


  • If you check Keep Checked Out, then the file is writable after the check in completes.
  • If you do not checkKeep Checked Out, then the file remains read-only after the check in completes.

Behavior Change When Checking Out a File

This section describes the behavior that occurs when you check out an object, either using the ENOVIA Check Out command in the ENOVIA CommandManager or when checking out a file from the browser.

From ENOVIA

If you click Check Out, ENOVIA retrieves the latest version of the file for editing. If you select Check Out, the Get check box is also selected.

If you click only Get, ENOVIA retrieves a read-only copy of the latest version of the file.

From Browser

The following behavior changes occurs during check out when the Load option is not selected in the Checkout page:

  • If the user checking out the object has locked the object, then Designer Central makes the corresponding file "writable" after downloading it.
  • If the user is checking out a design locked by another person, then Designer Central makes the corresponding file "read-only" after downloading it.
  • During checkout, if the user selects the Lock option in Checkout page for an object which is not locked, then Designer Central makes the corresponding file "writable" after downloading it.
  • If the checkout directory is the RFA directory, then no changes are done to the file in the RFA directory.

Behavior during Lock/Unlock from browser

The read-only property of a file is affected by Designer Central depending on the lock status of the design's corresponding design object.

Behavior from Local Workspace Manager

Update Feature Behavior

When you update a file that is writable on the disk from the local workspace manager, then the file is made read-only.

When you update a file that is read-only on disk, then upon update, the file is overwritten and is left as read-only.

Revert Feature Behavior

When a file which is not locked by the user is reverted,

  • If the file is already read-only, then it remains read-only after reverting.
  • If the file is already writable, then it is made read-only after reverting.

When a file that is locked by the user is reverted,

  • If the file is already "writable" then it remains "writable" after reverting.
  • If the file is already "read-only" then it is made "writable" after reverting.

Behavior Change in Configurations

The following are the behavior changes while managing configurations in ENOVIA depending on the lock status of the files.


  • If family object is locked, then the files that are downloaded upon checkout, are writable on the disk.
  • If a configuration is unlocked which causes unlock of all the instances also, then the files are writable upon checkout.
  • If the instance objects of a configuration is locked, then upon checkout the files are made read-only on the disk.