📋 SecuForms: Best Practices for SecuFlows Advanced Integration and PDF Mapping

Etiquette for SecuFlows Advanced integration

Here you will find recommendations for creating SecuForms that are used in combination with data workflow automation (FTAPI SecuFlows Advanced).

The instructions refer to the naming of fields in the SecuForms form and in the Adobe PDF if one is to be filled with information from the SecuForm.

Background: Ensuring that the automation works flawlessly and that easy editing is guaranteed.

Note: SecuFlows Advanced licenses are required for data workflow automation with SecuForms. If you are interested, please feel free to arrange a personal consultation appointment.

Naming custom fields

1. Field names must not be repeated.
2. Use one SecuForms field per "information unit" (for transfer to third-party systems or for use as variables in process automation). Examples:
   • Query address in three fields: (1.) Street + house number, (2.) Zip code, (3.) City
   • Query business partner in seven fields: (1.) Salutation, (2.) Last name, (3.) First name, (4.) Company name, (5.) Street + house number, (6.) Zip code, (7.) City
3. Use Radio Button or Drop Down if only one of several answer options is to be selected.

Field mapping in fillable PDFs

We often transfer information from SecuForms into fillable PDFs in order to save them locally or forward them. A PDF template is required for this.

To ensure functionality and visual quality, the following should be observed when creating the PDF template:

1. Fields are mapped 1-to-1. That is, create one field in the PDF for each field in the SecuForm.
2. Choose a consistent font type and font size for PDF fields. Please note: There is no automatic adjustment of the font size according to the amount of text in relation to the field size. Therefore, the correct field size should be chosen in the PDF in advance.
3. Naming of field names:
   • short and concise
   • if possible, no punctuation marks (spaces are ok)
   • do not leave fields unnamed ("undefined")
   • Info: All punctuation marks are removed for the use of the field name in the configuration file of the Process Client.
4. Signature fields must be created either as image fields or as "Push button".
5. Checkboxes in the SecuForm should also be mapped as checkboxes in the PDF.

Notes on mapping in the Process Client configuration

If fields are used in an email based on an HTML template, there are two options regarding naming:

• do not use spaces in the field name
• rename the fields in the configuration (e.g., replace spaces with "_")

Related articles

📋 SecuForms: Create online form, configure layout and recipients