Programming the Reader Configuration

When the reader is launched from rules or Java code, you can set options to tweak the reader's behavior.
A Java snippet is available in the Javadoc of the class DoorsReader.

Programming the items scope

You can define the scope of the reader, to restrict the modules to be read or to force them to be loaded at once, using a ReaderScope.

Programming the baselines

You can specify for each formal module which baseline should be used, using a BaselineDescriptor.

Programming the views

You can specify for each formal module which specific view should be used over the default one, using a ItemScope.

A Filter instance might also be set to introduce additional filtering on top on the one provided by the current view.

Note that a DOORS client doesn't provide any mean to read a baseline using a specific view when the baseline is not open and visible in the DOORS client.

Connecting to DOORS in batch mode

The reader usually requires a DOORS client to be open in order to access the data. It is possible to configure the reader so that DOORS is executed in batch mode, provided you give the reader the DOORS user identity to connect to. To use the batch mode, you need to set the Common.PREFERENCE_DOORS_IS_SILENT property, as described in the snippet in DoorsReader. The option Common.OPTION_DOORS_APPLICATION shall also be used to share a DOORS batch client between a model reader and a DXL command to update DOORS data

Note that, even in batch mode, on-demand loading is still supported (a hidden DOORS client is kept alive as long as data is retrieved).

Programmatic Properties

The model reader can be configured using many options, which are defined in the class Common.

Here is a list of the most significant options:

Related reference
Reading DOORS data