Fixed expired-date selection in expiration field
We fixed an issue in the expiration date picker that allowed selecting and saving dates prior to today even after showing a warning.With this update: In the UI, all dates before today are disabled; manual/pasted input is also validated. On the backend, invalid dates are rejected to prevent inconsistencies (including via the API). Timezone handling was adjusted to avoid edge-case errors near day boundaries. The flow now prevents saving expired dates and shows a clear message indicating the expiration must be today or later.
Dashboard: new Pending filters (Simple & Advanced signature)
What it is: Two new filters were added when opening Pending from the Dashboard: Simple signature and Advanced signature. You can still filter by Approve or reject, Pending deletion, or view All. Why it matters: Faster prioritization by signature type. Cleaner, more focused lists. Clearer operational metrics for each team. How to use: On the Dashboard, click the Pending card. In Select pending, choose Simple signature or Advanced signature (or any other filter). Click Next to open the filtered list.
Tickets: unified entry points, new Create ticket button & “My tickets”
What it is We shipped usability improvements to the Tickets area: “My tickets”: renamed and icon updated to clearly identify your ticket list. Create ticket in the toolbar: the create ticket action was moved to a dedicated toolbar button (My documents / files view), removing the duplicate action from the support panel. “Support” button (header): now opens Legale support directly to contact our team. Why it matters Less friction: fewer clicks, clearer paths. Prevents confusion between create ticket and support. Consistent, discoverable navigation across the app. How to use To create a ticket, click Create a ticket in the toolbar. To view your list, open My tickets (new name/icon). To contact our team, use Support in the header (opens Legale support panel).
Menu reorg: Certificate and Notifications moved to Settings
What it is: We reorganized the dashboard navigation: Certificate and Notifications, previously listed in the main sidebar, have been moved into Settings. This centralizes configuration, making it easier to find and maintain. Why it matters Less fragmentation: configuration unified in Settings. Fewer clicks and clearer navigation. Simpler onboarding and support for teams. How to use Go to Settings → Certificate to manage cloud/local certificates, passwords, and related parameters. Go to Settings → Notifications to define templates, rules, and conditional notifications. Notes: Access permissions remain the same; only the menu location changed. Image:
API: choose advanced signing method and country
What it is: We added parameters for signing method and country to the Advanced Signature API. Each request can be routed to the correct provider/rule per jurisdiction (local requirements, validations, cloud/local certificates) while preserving evidence and traceability.
Conditional variables and multi-condition notifications
What it is: We added conditional variables and multi-condition support for notifications. Compare form variables with a value and chain additional conditions to control when a notification is sent and with which content. Why it matters Truly contextual notifications driven by document data. Less manual routing: more automation and accuracy. Reusable templates with clear, maintainable logic. How to use Open the form and go to Notification → Condition. In Variable, pick the field (e.g., {{RUT}}). In Logic condition, choose the operator (e.g., =). In Value compare, enter the target value. Select the data source (Field or Fix). Click Add condition (+) to append more rules (you can combine several). Configure Email, Subject, Suffix, and Message, then save. Notes: Conditions are evaluated when the notification is sent; make sure variables reference existing form fields.
Automatic evidence_ prefix for evidence downloads
What it is: We introduced a standard naming convention for evidence files: when you download evidence, the file name is prefixed with evidence_ followed by the original document name.Example: Contract.pdf → evidence_Contract.pdf. Why it matters Simplifies audits and search. Prevents confusion between the original document and its evidence. Improves consistency across repositories and automated processes. How to use Open a document that has generated evidence. Click Download evidence. The file will be saved as evidence_{OriginalName}.{ext} (the extension is preserved). Notes: The original document name and extension are preserved; only the evidence_ prefix is prepended. Example:
Fixed error when applying a previously saved workflow to a new document
We fixed a bug where selecting a previously saved workflow for a new document failed to apply steps, assignments, and validations correctly, or triggered a service error.With this update, workflow templates are now copied in full (steps, assignees, rules, and due dates), validated before creation, and the document status syncs properly with the defined transitions.
Fixed blank screen when starting a chat or sending a request
We fixed a UI issue where starting the chat or submitting a request could lead to a blank screen, preventing the flow from continuing.This update improves error handling and loading-state management to avoid empty renders on slow or failed responses.Now, when chatting or making requests, the app shows a proper progress state or an error message when needed, and the process completes reliably.
API approval error fixed
We fixed a bug in the API approval flow that caused 4xx/5xx responses or left approvals unregistered, resulting in inconsistent document/request states.This update enforces permission and token scope checks, validates the payload and identifiers, and adds idempotent handling to avoid duplicate operations.With this fix, approval calls made through the API are reliable, and the status updates immediately to reflect the operation’s outcome.