C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.head.xml
Jump to main content C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.before.body.xml

# Create a New Dynamic Requirements File

Before creating a new requirement file you should have available a requirements document that outlines the properties and design options for the new file.

1. In the File menu, select New.
2. In the New File dialog box, select Expere Requirement Files and then select Dynamic Requirement from the list of available options.
3. In the New File dialog box, select Open.
   The Document Properties dialog box opens.
4. Complete the file by filling in the text boxes with information from the requirements document. For details, refer to Document Properties.
   A dynamic requirement file document must have a Document ID defined in order to create the file.
   Note:
   - Line of Business and Type Description appear only if the Content Type is set to Policy or Org. Within the organizations.xml file:
     - if the SuppressDD attribute value is set to true, the LOBs are not displayed in document Properties.
     - if the Name and SuppressDD attributes are not present, the LOBs are not displayed.
   - Selecting Document List indicates that the document has been authored to list all of the documents that apply to the transaction.
     - You are able to author Document List on a Dynamic document. The dynamic document will present any Static or Dynamic document name in the list per the request.
   - Selecting eSignature Document indicates the document is an eSignature document.
5. Click OK.
   The dynamic requirement file is opened in Requirements Editor in the Outline Editor tab as NewFileNN.req.
6. In Requirements Editor, save the file by selecting File > Save. The best practice is to use the form name as the REQ file name; the target file name will, most likely, be defined in the requirements.

The dynamic requirement file is saved and available for authoring.
C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.after.body.xml