CSV File Extension Handling
Fixed an issue where uploading CSV files with uppercase extensions (e.g., .CSV) caused a service error. The platform now accepts CSV files with both lowercase and uppercase extensions.
A bug is a flaw in software that causes incorrect results, unexpected behavior, or malfunction of an application.
Fixed an issue where uploading CSV files with uppercase extensions (e.g., .CSV) caused a service error. The platform now accepts CSV files with both lowercase and uppercase extensions.
We fixed an inconsistency in the scheduled notifications module where some messages were delivered before or after the selected time.With this update, the system accurately matches the chosen time and the user’s timezone, ensuring punctual and consistent delivery. Additional validation was added to prevent drifts due to time/locale changes.
We fixed an issue that prevented deleting a signer while the workflow was Paused.With this update: Delete signer is enabled in Paused state as long as the signer has no valid signatures recorded on the current document. Step assignments and workflow status are recomputed after deletion. The audit log is updated and notifications remain consistent …
We fixed an issue in the Cloud certificate upload that allowed files with invalid extensions to be submitted.With this update: Both UI and backend restrict uploads to .pfx or .p12 only. File extension and type are validated; other formats are rejected with a clear message listing allowed types. This improves security and UX by preventing …
Fixed cloud certificate upload: only .pfx / .p12 allowed Read More »
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 …
Fixed expired-date selection in expiration field Read More »
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.
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 …
Fixed blank screen when starting a chat or sending a request Read More »
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 …
We fixed a bug in the signer access flow that prevented users from opening the document from the signing link (it showed an error or redirected without loading the file).This update adjusts link validation and access permissions, improves session handling, and standardizes redirects.Signers can now open the document and proceed with signing directly from the …
Fixed access issue preventing users from opening the document to sign Read More »
We fixed a bug in the FEA enrollment flow that, during identity verification/PIN creation, could trigger a service error and block the cloud signing process.With this update, enrollment now completes reliably; data is properly stored and users can proceed with cloud certificate signing immediately, with correct status updates and full traceability.