The execution control service ECS, enables users to change dynamically the running queue
of a business process.
The ECS can be used,for example, to separate FTP from SFTP traffic, VIP from non VIP customers,
slow from fast customers' trafficäó_ . The queues are dynamically changed during runtime depending
on some logic implemented in the BPs.
However, the queue change is lost if a BP goes into the waiting on IO state.
When the BP is resumed, after waiting on IO, it will be started (bootstrapped) on its original queue taken
from the workflow definition and not the dynamic queue assigned by the ECS service during runtime.
The ECS dynamic queue should be stored in memory or database. So the queue is not read from
the BP definition when the BP is resumed after WAITING ON IO.