As part of #2341, we added support for customizable message TTL in 8.6.0-alpha2. The default value is currently configured in the element template and is set to 0.
This might cause issues for our users who already use inbound connectors and may rely on the TTL being set to 1 hour implicitly (the 1h default originally comes from the Zeebe Java client, see https://github.com/camunda/camunda/issues/10937). We need to set the TTL to 1h again by the 8.6.0 release.
At the same time, it would be useful to be able to define the message TTL as an application config concern, and not specify it in the BPMN.
To accomodate both requirements, we should:
Make the TTL field optional in the element templates
Set it to 1h by default
Add an environment variable / spring config property to the runtime that will change the implicit default value
However, the value specified in the BPMN should have a priority (WYSIWYG)
What should we do?
As part of #2341, we added support for customizable message TTL in
8.6.0-alpha2. The default value is currently configured in the element template and is set to 0.This might cause issues for our users who already use inbound connectors and may rely on the TTL being set to 1 hour implicitly (the 1h default originally comes from the Zeebe Java client, see https://github.com/camunda/camunda/issues/10937). We need to set the TTL to 1h again by the
8.6.0release.At the same time, it would be useful to be able to define the message TTL as an application config concern, and not specify it in the BPMN.
To accomodate both requirements, we should: