General Authoring
Help for everyday Requirements authoring
- Selecting Multiple Elements/Attributes/Nodes
- Working with Tables
  How to create and work with table structures in the Outline Editor tab.
- Signature Areas
- SignatureDateField Element
- Working with Images
  The various types of graphics and how to use them.
- Working with the Find feature
- Finding Rules Across a Collection
  How to search the active collection or repository.
- Exporting Field Grid Information
  How to export Field Grid information as an XML file.
- Duplicate PTRs Report
- Output Formats
  Descriptions of the various output formats associated with Requirements Editor.
- Using the Field Grid to Navigate to a Data Point Location
  Navigating using the Field Grid.
- Defining Measurement Values
  Applying measurement values to various attributes defining the dimensions (length, width) at the element level.
- Using Text Formatting Tags within DataPoints
  Adding formatting within DTAs.
- Using Spell Check within Documents
- Author Fillable Field or Fillable Checkbox
- WKES AcroFields & Fillable Forms
- Authoring for TILA/RESPA Rounding
  The elements and attributes created to support the TILA/RESPA rounding method.
- The Role Attribute As Used in Expere
  Values for the Role attribute honored by Expere stylesheets.
- Refreshing Schemas
  When schemas are updated and how to update them manually.
- Removing the Tagline Print Date
  How to remove the Tagline Print Date element.
- Instance Properties in Documents
  The proper usage of Instance Properties inside discrete and static documents.
- Discrete Party
  The proper use of Discrete Party elements inside Dynamic and Static Documents.
- Creating a Document List

WKES AcroFields & Fillable Forms

AcroField Naming Convention

WKES looks for the following information in the AcroField name:

FieldType	The expected values for the FieldType would be as follows: signature: a Digital Signature AcroField signdate: a Text Field AcroField initials: a Text Field AcroField checkbox: a Check Box AcroField name: a Text Field AcroField numeric: a Text Field AcroField alphanum: a Text Field AcroField
UserEmail	The expected value for the UserEmail would be the signers email address.
FieldOrder	The expected value for the FieldOrder would be an integer identifying the sequence number for each signer so that all other fields are completed first. This is to ensure it matches the logic is in the Expere Engine.
Mandatory/Optional/blank	By default, all AcroFields are mandatory for the signer to fill, however the following AcroFields can be marked as optional; initials checkbox name numeric alphanum If _O or _M is not present on this set of AcroFields, WKES will assume the AcroField is mandatory. Note: The presence of signature or signdate in the Acrofield name always indicate that the Acrofield is mandatory.

WKES expects AcroField names in the following format (generated by the Expere engine based on authored content):

WKES_FieldType_UserEmail_FieldOrder
WKES_FieldType_UserEmail_FieldOrder_M/O