Notes for Release 4.22 Estimated reading: 2 minutes 590 views In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed. Release rollout schedule Production & Pre-Production Environments: Scheduled for release on: 17/09/2025 Enhancements Dynamic redirect We’ve expanded the auto redirect to support an additional redirect method at the end of a session. Primary option: Redirect to a URL taken from a selected form field (if the field contains a valid value). Secondary option: If no valid field value is found, the system falls back to the predefined URL.This improvement provides greater flexibility and control, allowing redirects to be dynamically determined based on user input while still supporting a fixed destination as backup. Read more Bug fixes Auto-selection in cascading selects with groups is now fixed. When a parent is chosen and it has only one child, the child is automatically populated Fixed API documentation for BPMN and OTP activation Security Client SSO We’ve introduced support for authenticating external end users via SAML authentication. When a client accesses a form link, they are redirected to their organization’s Identity Provider (IdP) for secure login. As an optional configuration, Cellosign can validate a unique identifier from the SAML claim against the customer ID defined in the form. Matching values grant access, while mismatches result in access being denied. This enhancement strengthens security by removing the need for OTP challenges and provides a seamless authentication experience through the customer’s existing SSO system. IP Whitelisting for Client forms You can now configure an IP address whitelist for client forms. When a request comes from a whitelisted IP, reCAPTCHA validation is skipped. Requests from other IPs will continue to require reCAPTCHA. Read more Archive fallback to storage Currently, when an archive API request fails, Cellosign uses a fallback email containing the session data. In cases where the session includes sensitive information that cannot be sent by email, projects can now configure storage integration as the fallback method. When enabled, session data will be posted to the selected storage integration if the archive API cannot complete. This enhancement provides a secure and compliant alternative to the existing email fallback. Read more Maintenance Software component upgrades Deprecation notice N/a Notes for Release 4.22 - Previous Notes for Release 4.23 Next - Notes for Release 4.22 Notes for Release 4.21
