Table of Contents:

...

Quik! App Updates

New Features & Enhancements

...

• Special Character Handling in Salesforce Name Searches: Fixed an issue where searches for names containing special characters (e.g., O’Connor) failed. These searches now return results correctly.

• Form Search No Results Handling: Previously, searches that returned no matching results incorrectly displayed all available records. Now, empty searches correctly return no results as expected.

...

Quik! Engine Updates

New Features & Enhancements

...

• Radio Buttons/Checkboxes Processing Fix: Resolved an issue where radio buttons and checkboxes were not properly processed when using Form Group Instances with EnableESignEdits, particularly when the form was not the first in a packet. These fields now correctly flow through to Docusign in the /docusign/sign payload.
  Note: This fix was originally introduced in Release 92 but was later reverted. It has now been reintroduced in Release 93.

• Docusign Field Name Consistency with Form Group Instances: Field names sent to Docusign now match those in the HTML viewer for improved consistency.

  Example Update:

  • A field named 1acc.RegType-1000 in the HTML viewer appears as:
    → QuikRadio44252.1acc.RegType-1000

  • Previously, it was sent to Docusign as:
    → QuikRadio44252-1000-1acc.RegType-1000

  • Now, it is sent as:
    → QuikRadio44252.1acc.RegType-1000

  Note: The "-1000" extension was previously duplicated within the field name. This duplication has been removed to ensure consistency with the HTML viewer.Calculated Field Error Fix: Resolved an issue where percentage signs (%)at the end of a Calculated Field (e.g., 1own.LName) caused a FormsGenerationException (ErrorCode: 10099). Calculated fields with percentage signs now process correctly without errors.

• Fix for Ampersands in URL Encoded Sign Content Type: Addressed an issue where signContentType: "UrlEncoded" did not properly handle ampersands (&) in form data, causing the Docusign payload to split incorrectly. This has been fixed, and the payload now processes correctly.

• Printing Stability Update: Rolled back from iText8 to iText5 to ensure greater stability in document generation while preparing for a future upgrade.

  Note: The rollback had already occurred; this release simply clears out the code pipeline.

...