# Using read-only elements from Together

If you have a read-only element that you want to export to DOORS, and there is a possibility that the model element might change in the future, make the element writable before you send it to DOORS. Reset it back to the read-only state after you export. This ensures that the element is automatically updated in the future, even if it is read-only at the time of the update.

You can send a read-only Together element to DOORS, but Together DOORSIntegration doesn’t remember that the element was sent to DOORS (it can’t mark the element in Together as "sent" because the element isn’t writable). As a result, the corresponding surrogate object won’t be automatically updated during any subsequent updates.

To update the object in the surrogate module, you must manually select the object in Together and send it to DOORS again. You can optionally send other elements to DOORS at the same time.

If the model element is now writable in Together, Together DOORSIntegration automatically marks it as sent in Together when you send it to DOORS. All future updates will now automatically update the corresponding surrogate module object in DOORS, along with any documentation and class properties that were sent with the writable element. Future updates will work even if the element is read-only in Together at the time of the update.

See also:

Exporting a Together project to DOORS: Exporting new modeling elements

Next:

Updating the surrogate module