Modifying the XTemplate in I32 Design 6

  1. Open the XTemplate in I32 Forms Design 6, then navigate to the folder where the XTemplate was stored to and change the Files of Type to XTemplate Document (.xml) rather than the default of .sfx.
  2. From the tool buttons, select the Signature Tool and draw a rectangle in the area of the signature to be highlighted.
    When creating an E-Signature Date, create a new field by selecting the Field Tool or update an existing field.



  3. E-Signature fields must have the .eSig extension and E-Signature Date fields need to have the .eSig.eSigDate extension. With the Signature/Date selected, under the Properties settings window, click the fields tab and make sure the field description has the proper extension.
  4. The Description names for the Signature (.eSig) and Date (.eSig.eSigDate) need to be formatted correctly. Example below: “EsignatureArea1”
    Note: Without this extension, the E-Signature and E-Signature Date will not work correctly for downstream workflows.
  5. When there are two Esig fields that are signed by the same person:
    1. The naming of the fields do not impact the functionality of E-Sign. They can be named different.
    2. The Data ID’s (Visible in I32) must be different (see REQ example below)
  6. When all signature areas have been defined, save the updated template as a .xml file.
  7. Import the updated XTemplate into Requirements Editor.