Home
General Authoring
Help with common features for everyday Requirements authoring
Creating Requirements Files (REQ Files)
Creating the various types of REQ files
Requirements File created from an Existing File (Save As)

General Authoring
Help with common features for everyday Requirements authoring
- Assembling Documents
- Creating Requirements Files (REQ Files)
  Creating the various types of REQ files
- Document List
- Document Properties
  How to set and view specific properties associated with the current document.
- Elements and Attributes
- Fillable Field or Fillable Checkbox
- Field Grid
- Find feature
  How to search for specific criteria, with options that change based on the context of their focus and selection.
- Images
  How to work with images using a variety of methods.
- Instance Properties
  The proper usage of Instance Properties inside discrete and static documents.
- Measurement Values
- Output Formats
  Output formats ensure consistency and compliance with regulations in presenting certain values in the system.
- Refreshing Schema Files
  When schemas are updated and how to update them manually.
- Reports
- Role Attribute
  Values for the Role attribute honored by Expere stylesheets.
- Selecting Multiple Items
- Signature Areas
  The Requirements Editor provides elements to include signature lines within a document. Two types of signatures can be added - Signature element for within the body of the document and SignatureSection element for the entire document or agreement.
- Spell Check
  How to check the spelling of all text in any open document.
- Tables
  How to create and work with table structures in the Outline Editor tab
- Tagline Print Date
- Text Formatting Tags within DataPoints
- TILA/RESPA Rounding
  The elements and attributes created to support the TILA/RESPA rounding method.

Requirements File created from an Existing File (Save As)

The Save As command can be used to save an open requirements file as another file using a unique file name and document identifier. This command is mainly used to save an existing REQ file as a local copy for testing and development purposes but can also be used to save a copy to a network location or workspace.

In order to maintain the integrity of document identifiers (for example, the Document ID) and downstream impacts to content references in the REQ, you must enter a unique Document ID as part of saving an REQ file as another file (or copy). By default, the text _Copy is appended to the Document ID in the Document Properties. You may keep the defaults or define a unique name for both the file and Document ID.

Note: Save As can be used to save both locked (read-only) and writeable REQ files. When the source file is locked with the read-only restriction, the Save As operation removes the restriction and saves the file as writeable.