--- title: "Release June 21, 2026" slug: "release-june-21-2026" updated: 2026-06-25T10:04:56Z published: 2026-06-25T10:04:56Z canonical: "knowledge.lightico.com/release-june-21-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.lightico.com/llms.txt > Use this file to discover all available pages before exploring further. # Release June 21, 2026 This release expands agent and admin control across the platform β€” from how documents are collected and verified in Collaboration Room, to how cases are structured and managed in Case Manager, to how extracted data is reviewed and confirmed in Document Analyzer. ## New features This release includes the following new features: ## Collaboration Room ### πŸ“‚ Agent control over Document Request requirements Admins can now give agents greater flexibility over how document collection is enforced within a Document Request step. Two new controls are available when enabled by the admin: - **Minimum required:** Agents can set the minimum number of documents a customer must upload before the step is considered complete β€” defaulting to all selected documents, but adjustable down to zero. - **Step exclusion:** Agents can exclude the Document Request step entirely when document collection isn't needed for a particular customer interaction. When excluded, the customer doesn't see the step and the Workflow continues automatically to the next step. For more information, see: - [Add Document Requests to a Workflow](/v1/docs/add-document-requests-to-a-workflow#minimum-required-documents) - [Send a Workflow with a Document Request step](/v1/docs/send-a-workflow-with-a-document-request-step) ### πŸ“Ž Agent control over External Document steps in Workflows Admins can now configure any External Document step in a Workflow as optional. When a step is marked optional, agents can choose to skip it during the session β€” and any skipped step is automatically excluded from the customer's view. For more information, see: - [Add External Documents in a Workflow](/v1/docs/add-external-documents-in-a-workflow#edit-the-external-document-step) - [Send an External Document](/v1/docs/send-a-workflow-with-an-external-document#optional-documents) ### πŸͺͺ More flexible photo ID verification Photo ID verification Workflow steps now give you more control over how document types are handled β€” both during verification and in the Workflow logic that follows. **πŸ”¬ Control photo ID type matching** Photo ID verification steps now include a Classification validation toggle, so you can set per step how strict verification should be: - **Toggle on (default)** β€” the document must match the requested type. Existing Workflows behave as before. - **Toggle off** β€” any authentic supported document continues down the step's pass path, as long as it clears quality and authentication checks. **↗️ Route customers by the identified document type** The document type identified during verification β€” such as a driver's license, passport, or residence permit β€” is now available as a system value when building Workflow conditions. Use the #IDV_DOCUMENT_CLASS# system value to guide customers down the appropriate path based on the document they actually uploaded, even when it differs from the type originally requested. For more information, see [Add Document Requests to a Workflow](/v1/docs/add-photo-id-verification-to-a-workflow#configure-the-photo-id-verification-step). ### πŸ“ Set table widths as relative or fixed in Dynamic Documents You can now set a table's width in a Dynamic Document as a percentage of the screen, in addition to the existing fixed pixel option. A relative width lets short, summary-style tables resize cleanly across mobile and desktop, avoiding horizontal scrolling in mobile-heavy journeys. Fixed pixel widths remain the default and are still the better choice for tables with longer text, which can become cramped at relative widths. Existing tables are unaffected unless you switch them. For more information, see [Create Dynamic Documents](/v1/docs/design-dynamic-documents#set-the-table-width1). ### βš™οΈ Control auto-cropping behavior from System Settings Admins can now enable or disable auto-cropping directly from System Settings, without needing to contact Customer Support. This makes it easy to adjust the setting if auto-cropping isn't producing the expected results. --- ## Case Manager ### πŸ‘οΈ Hide tasks from the agent view based on conditions A new **Hidden** behavior option is now available in the case type builder, alongside **Read Only** and **Disabled**. When the configured condition is met, the task is removed from the agent's task navigation entirely β€” not visible, not selectable. When the condition is no longer met, the task reappears automatically. For more information, see [Configure a case type](/v1/docs/configuring-a-case-type#configure-task-behavior). ### πŸ”„ Hit the ground running with a ready-made case lifecycle Case Manager now initializes new case types with a three-state default lifecycle β€” **In Progress**, **Completed**, and **Cancelled** β€” rather than a single bare step. Business configurators have a ready-made starting point for every new case type they create and can build on or adjust the lifecycle from there. ### πŸ› οΈ Fix customer contact details without restarting the session The re-engage feature is now available in customer engagement task. Re-engage enables agents to correct a customer's contact details and resend the collaboration session invitation without losing any existing session content. For more information, see [Complete a case](/v1/docs/complete-a-case#reengage-a-customer1). ### πŸ“¬ Case assignment email notifications Agents in Case Manager can now receive an email notification when a case is assigned or reassigned to them. When enabled, each notification includes: - The case title and a direct link to the case - A configurable subject line supporting static text and dynamic case values - A customizable email body via HTML upload, with a system default available For more information, see [Configure Case Manager settings](/v1/docs/configure-case-manager-settings#case-assignment-notifications). --- ## Document Analyzer ### πŸ› οΈ Resolve extraction gaps directly in Document Analyzer Agents can now edit extracted Attribute values directly in Document Analyzer β€” including entering a value for an Attribute where no extraction point was found, or marking an extracted value as "missing" when the document does not actually contain that data. Previously, incomplete or inaccurate extractions could cause rules to fail with no way for agents to correct them in context. With this update, agents can resolve these gaps in real time, reducing rule failures caused by missing or incorrect extraction data and avoiding the need for manual workarounds outside the system. ### πŸ—‚οΈ Edit and manage your data schema Business Configurators can now update an existing data schema without deleting and re-uploading it. Changes are made directly in the custom integration hub **Data Schema** tab, with Attribute mappings preserved throughout. New capabilities include: - **In-place editing** β€” add, edit, or delete objects and key-value pairs directly in the schema - **Export schema with mapping** β€” save the schema and its current Attribute bindings as a portable file - **Import schema with mapping** β€” restore a previously exported schema, including its bindings - **JSON view toggle** β€” see which Attribute is bound to which key at a glance For more information, see [Custom integration hub for API and events](/v1/docs/api-and-events-integration-hub#schema-mapping1). ### πŸ” Confirm STP analysis results without making changes Agents can now submit an STP document analysis package without making changes, formally confirming the automated results were reviewed and accepted. Previously, Submit was only active when a manual override was performed. --- ## Fixes ### Collaboration Room Resolved the following issues: - The audit trail text in completed sessions was displayed in English even when the platform language was set to Portuguese. - Options selected in a previous Workflow were incorrectly retained and displayed in a subsequent Workflow within the same session when hidden Form sections were involved. - In a multi-signer Workflow, Participant 1's signature was applied to signature fields assigned to Participant 2. - An agent was incorrectly presented with a **Sign Document** button when set as the last step in a Workflow PDF without any assigned signature fields, preventing the Workflow from completing. - Attributes from the same Form failed to display in a rich text section on a subsequent Form page. - Special characters from languages including German, Spanish, and French were not rendered correctly in Document Requests and appeared to fall back to ASCII encoding. - The embedded external HTML frame in a Dynamic Document appeared too small during customer sessions. - A table border set to transparent in a rich text Form section was visible to customers during a session, despite displaying correctly in the Form builder. - In a Form with visibility conditions, required Attributes in a section that was hidden again after being revealed continued to block form submission. - The customer and agent document upload interface was not translated to French when the platform language was set to French. - Several button labels in the Portuguese (Portugal) localization were updated to use European Portuguese equivalents. --- ### Admin Center Resolved the following issues: - An SFTP hub integration could not be saved when the server address began with "sftp". - When setting a table's width to a percentage value in the Dynamic Document table style editor, the setting reverted to a fixed pixel value after saving and refreshing. - When adjusting table width in the Dynamic Document designer, the change was not reflected in the editor preview, though it rendered correctly in the customer session. --- ### Case Manager Resolved the following issues: - In Case Manager, the task list scroll position jumped to the bottom whenever data was entered into a form field. - In Case Manager, OTP contact details for a co-signer were not saved between tasks, requiring manual re-entry each time a subsequent task was sent. --- ### Document Analyzer Resolved the following issue: - Occasionally, Document Analyzer analyses that were initiated did not complete and returned fatal errors, preventing completion events from being sent. --- ### Events Resolved the following issue: - Duplicate **Participant Completed** events were sent for the same items in certain sessions. --- ## Release timeline | NA1 | EU4 | EU2 | | --- | --- | --- | | July 21, 2026 7:00 AM UTC | July 22, 2026 8:00 PM UTC | July 29, 2026 11:00 PM UTC | A module within the Lightico Platform that enables you to complete all parts of a customer journey from a single, chat-style interface. You can obtain signatures, verify ID, collect supporting documentation, collect payments and more. An interaction in a Lightico session that enables customers to provide supporting documentation by uploading a file or scanning the document using a mobile device. A series of customer interactions that must be completed in a certain order. Workflows are configured by a business configurator (BC) and added to the session by an agent or API. A PDF document that is uploaded to a session from a source other than Lightico, for example, from the agent’s computer. Values that the Lightico system either generates or regularly records from session, case, or analysis data. For a full list of available system values, see [System values](/v1/docs/system-values). Documents created entirely in the Lightico UI, displayed as dynamic HTML and converted to PDF after signing or approval. A module in the Lightico platform that enables you to collect and manage customer information in a standardized, organized, and efficient way. A module in the Lightico platform that performs an AI-based analysis of uploaded documents to extract structured data, classify document types, and evaluate business rules. The interface enables agent review, feedback, and corrections. An identifying label that you bind to data in a session that enables you to organize and make use of the data during the session. Digital form that captures information provided by the customer or agent during a session. A user that communicates with end-customers to complete tasks in a Collaboration Room session or a Case Manager case. Area of the Lightico platform where you will find all settings, user management, and asset configuration pages. Access to this area is defined by a user's role and permissions.