Notes for Release 4.33

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

Stage environment: Scheduled for release on: 03/02/2026

Production & Pre-Production Environments: Scheduled for release on:16/02/2025

Enhancements

BPMN Process Deduplication

This update introduces a Deduplication Mechanism for BPMN processes. The goal is to optimize resource usage by reusing active process instances when identical requests are made, rather than spawning redundant workflows.

How It Works

The system evaluates incoming requests based on specific input parameters.

2. Lookup Logic: The system searches for an existing process matching both the BPMN ID and the inputs value.
3. State Evaluation: * Active: Returns the existing instance.
   • Terminal (Failed, Finished, etc.): Creates a new instance.
   • Metadata: New hashes are stored in process metadata for future lookups.

⚠️ Important Constraints & Usage Guidelines

While deduplication improves efficiency, it must be implemented with the following technical limitations in mind:

First Session Limitation

The deduplication algorithm is designed to track the first session of a process.

• If the first session is completed but the overall BPMN process is still running (e.g., stuck in a later gateway or service task), the client will receive an “Unavailable” response.
• The system will not automatically trigger a new process if the original is still technically “active” globally but the entry session is closed.

Security & Parallel Sessions

Use this function only when the process points to a single initial session.

• The Risk: If the start node points to parallel sessions, the system cannot guarantee which session will be returned to the user.
• Security Breach: Returning an unintended session in a parallel flow could lead to unauthorized data access or process interference.
• Recommendation: Do not enable deduplication for workflows involving parallel execution paths at the start.

Process Reuse Logic & Return Conditions

Existing Process State	Process Structure	Result	Client Response
No Match Found	Any	Create New	Success: New Instance ID
Active	Single Session	Reuse Existing	Success: Existing Instance ID
Active (1st Session Done)	Single Session	Blocked	Error: “Unavailable”
Active	Parallel Sessions	Security Risk	Not Recommended (Unpredictable)
Finished	Any	Create New	Success: New Instance ID
Failed / Canceled	Any	Create New	Success: New Instance ID
Expired	Any	Create New	Success: New Instance ID

UI Changes

Bug fixes

• N/A
  

Security

Recipient IP “Allow List”

You can now whitelist specific IP addresses to streamline the user journey for trusted partners or internal networks.

• Logic:
  • Whitelisted IP: Recipients bypass the reCAPTCHA challenge and gain immediate access.
  • Non-Whitelisted IP: Standard reCAPTCHA verification remains mandatory.
• Affected Resources:
  • Client Forms
  • OTP Challenges
  • Password Challenges

A new configuration section has been added to the Project Settings -> Security Pane.

• New Section: “Verification Bypass IPs for end users.”
• Formatting: The system supports multi-value tags for specific IPs (e.g., 192.168.1.1)

Maintenance

N/a