Release June 22, 2025

This release brings a “decline to sign” option to Workflow documents and a description that gives the customer more context for Document Requests. We continue to upgrade our interfaces with improved UX in the Forms and HTML directory pages. Finally, Forms are now identified in the Workflow completion event.

New Collaboration Room features

Decline to sign and continue the Workflow

You can now configure a PDF step to allow participants to decline signing and continue through the Workflow. This provides more flexibility for handling cases where a participant is unable or unwilling to sign, without blocking the rest of the process.

The decline action is reported in the audit trail and in the Workflow completed event (state parameter).

For more information, see Add PDF Templates to a Workflow.

Document Request description for end-customer

You can now add a description to a Document Request to give customers more context about what is required (for example, “Electricity bill from the past three months”).

The description can be added in two places:

• Workflow builder - When configuring document requests in a Workflow; see Add Document Requests to a Workflow

• Agent console - When an agent is allowed to select and add custom document requests during a session; see Send a Workflow that requires agent input

Collaboration Room Improvements

Forms and HTML directory

We’ve added UX improvements to the Forms and HTML directory pages including:

• Same look and feel of the new Workflows directory

• Icons to differentiate between the different types of HTML documents (Dynamic, Tick-box, and Static Documents)

• Search function

Forms identified in step completion event

Forms are now reported in the Workflow step completed event with the following information about the Form: name, template ID, instance ID, and Attributes included in the Form.

For a full reference to this event, see Workflow step completed event in the Lightico developer center.

Fixes

Collaboration room

Resolved the following issues:

• An incorrect value would show for aggregate function.

• Fields were not aligned horizontally in a visual cart.

• Android devices were only allowing 2 wrong PIN attempts instead of 3.

• Missing custom file names and Workflow steps after Workflow completes.

• A Workflow was not completing when more than one PDF with "any signer" enabled was included in the Workflow.

• An agent form text Attribute did not enforce the maximum character limit.

• Visibility issues with the values displayed in dropdown lists within nested fields.

Studio

Resolved the following issues:

• Unable to create a Workflow in a new/empty folder.

• Unable to import HTML with a system value.

Campaigns

Resolved the following issue:

• 500 error presented when exporting a failed campaign.

Case Manager

Resolved the following issues:

• Renaming the Form step in the Workflow builder did not reflect in the case type title.

• Distorted date format in some cases.

Settings

Resolved the following issues:

• Signature / approval consent missing in the team settings.

• Adding a new asset to a shared folder did not make the asset available to users in teams to which that folder was associated.

• If short url was enabled and a session was re-engaged, then the event did not include the new name and phone number.

System Usage

Resolved the following issue:

• Deleting a session via the admin history page displayed an error.

API

Resolved the following issues:

• Incorrect response code when using the Authenticate user endpoint with an incorrect user password.

• Sending a Workflow that included a function and document, incorrectly responded with a 400 error even though it was added to the session.

Events

Resolved the following issues:

• Participant completed event sending multiple times.

• If a payment step is included in a Workflow, the Workflow completed event was incorrectly sent in two separate events.

• The invokeData was not sent back for the esignDocument portion in the Workflow completed event.

Release timeline