Need a better way to promote processor parameters, like "Concurrent tasks" from development to production environments.
Bryan Bende suggested:
I think we may want to consider making the concurrent tasks work
similar to variables, in that we capture the concurrent tasks that the
flow was developed with and would use it initially, but then if you
have modified this value in the target environment it would not
trigger a local change and would be retained across upgrades so that
you don't have to reset it.
I would extend this Jira to similar parameters, that need to be changed manually now when promoting flows to production from dev/test environments and they cannot use expression language or variables.