Why are date fields on my Dynamic Files not populating correctly during counter-signing, and how can I get this fixed?

Date fields on Dynamic Files sometimes need configuration adjustments within the PDF Engine to ensure they populate correctly during the counter-sign process. Common issues include:

- Date fields not auto-populating for the applicant/caregiver when the document is signed or counter-signed.

- Custom date inputs (e.g., Hire Date) not mapping to the correct fields on specific pages of a Dynamic File.

- Date fields populating when they should remain blank until the counter-sign step is completed.

These are PDF Engine configuration issues that require a backend adjustment by the Bolt support team. They cannot be resolved by agency users directly.

What to do if you encounter this issue:

1. Identify the specific Dynamic File name and the page number(s) where the date field is not behaving correctly.

2. Note the expected behavior — for example: 'Date should auto-populate when counter-signed,' 'Hire Date input should populate on page 23,' or 'Date should NOT populate until counter-sign.'

3. Submit a support request to Bolt, including:

- The Dynamic File name

- The specific page number(s) affected

- A screenshot highlighting the problematic date field(s)

- A description of the expected behavior (e.g., populate on counter-sign, populate from a custom input, or remain blank)

- A link to the caregiver or patient record where the issue is visible

4. The Bolt team will update the PDF Engine mapping for the affected Dynamic File so that date fields populate at the correct step and from the correct data source.

Once the fix is applied, it will take effect for all future uses of that Dynamic File across your agency. Previously generated documents may need to be re-sent if corrected dates are required.