Using Fillable Fields and Checkboxes

Fillable Field naming for Embedded PDF, dynamic, and static REQ files

The following is the naming convention for fillable fields, including checkboxes and field names:

  • An example FillableField element value could look like this: BR_1_Name_VA. The naming convention must avoid the use of "." (periods / dots).
  • An example FillableCheckbox element value could look like this: BR_1_Cbox_Past_VA_Disability_Yes. The naming convention must avoid the use of "." (periods / dots).
Note:
  • The FillableField and FillableCheckbox naming conventions must avoid the use of "." (periods / dots) and instead use "underscores" between words within the naming convention value.
  • With static and dynamic documents, Expere will automatically change periods / dots (".") to underscores ("_") for fillable fields (i.e. Checkboxes and Text Fields); therefore, no user action is required for the Expere content. However, it is expected that Embedded PDF REQs (custom and base) are authored to follow this naming convention as Expere will not update those field names.
  • When a PdfMerge or MergedCopyPdf ancillary output is used, all fillable fields including but not limited to, text fields, checkboxes, radio buttons, etc, will contain unique IDs within individual documents within the merged PDF. Expere will append a ‘_#’ to the field names to ensure they are unique within the merged PDF files.