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:
Add arrow positioning to both “Pause” and “Recreate flux” buttons, similar to the visual indicators used in the Workflow section
Adding clear arrow indicators improves user guidance and interface consistency. It helps users quickly understand button functions, enhances usability, and aligns visual behavior across sections. This consistency reduces confusion, speeds up task completion, and reinforces an intuitive user experience.