Description
Today when we use an update activity in a workflow, we force the targeting dimension to change from the actual dimension to the one set in the update activity. It would be great to be able to NOT change automatically the targetting dimension
Why is this feature important to you
This feature would help to have, visually, a less complex workflow and to encourage best practices in order to use this OOTB activity
How would you like the feature to work
A checkbox option, in the update activity, that would allow us to stay on the actual targeting dimension. This would prevent to complexify actual workflows for nothing
Current Behaviour
Today, We have to use a change dimension activity after the update activity
Or use a fork activity before the update and join activity after it
Or worst: use SQL code activity as it's generally more performant (but less resilient) and it keeps the actual targeting dimension
