We are currently migrating our on-premise Exstream deployment to the Exstream Cloud Communication Platform and have encountered a challenge with variable handling and event timing.
On-Premise Setup:
- Multiple queues based on page count (There are 4 Queues)
- Each document has barcodes on odd pages with 20-digit composition
- One byte in the barcode serves as a document separator, calculated using a function that:
- References previous customer context from the driver file
- Assigns values to variables at Queue composition time
- Executes at each customer reset event
Cloud Migration Challenge:
We're unable to replicate this functionality in the cloud environment due to the following limitations:
- Events created in the cloud lack the granular control over "compose time" and "reset time" options available on-premise
- We cannot assign values to variables in the same manner as on-premise (Example few system variable only available at Queue composition, and Post composition values by the time are reset)
- When attempting to use queue-level variables, the values reset after customer composition, losing the previous customer context needed for our document separator calculation
Question:
Is there a workaround or alternative approach in Exstream Cloud that would allow us to:
1. Maintain customer context across document compositions for barcode calculation?
2. Assign and persist variable values similar to on-premise customer reset events?
3. Preserve variable values at the queue level without post-composition resets?
Any guidance on achieving equivalent functionality to our on-premise setup would be greatly appreciated.
