It would be very helpful to have a fourth step available when adding Dynamic Operations to an Orchestration. Something that would run at the moment Processing starts but BEFORE BVDL start updating the CRM tables.

When we have a process (nearly all of ours right now) where we Stage the data but then have a user review the data before hitting Process, it would be helpful to run scripts based on what the User has done but BEFORE data is committed. Our two primary use cases are either to throw errors for things that violate our business rules (but a user maybe overlooked/couldn't see when updating staged data) or to clean data before it is updated (again in cases where it is after the user has made adjustments). Currently for this second use case, we are having to go back, identify something BVDL did and then "fix it". Not ideal, and a pain to identify if something was just updated by the latest BVDL process run.

What I think would make the most sense is to rename Preprocessing to Postvalidation, and then have this new step be named Preprocessing. That labeling better fits what is occuring when the initial import stops after staging the records.