As Part of one requirement, we added one invoke activity on the preprocessing of flow action, every time when a user start case creation /updating we are collecting some info and adding to the other table.
But when user click on “Save for later button” as well we observed that the invoke activity in preprocessing also triggering,
Are they any ways to conditionalize the pre-processing activity not to run on click of save for later button?
Do we any info on this “Save for later button” to conditionalize like
Any label name
Are we able to set some value to property and commit to use as conditionalize value.
@VenkateswararaoK i am struggling to understand the use case? Pre-processing will run when you open the step/assignment - save would save those changes, which would be expected?
IF you don’t want to make the change until after submit then why not add it to post processing or run a Data Transform in the process after this step/assignment? You could even set a flag on post-processing etc. that would do the updates you need, by elimination you would exclude ‘save for later’ processing then…
You could trace the DX API calls to see if there is something unique here, or maybe someone else in the community has done this, but it seems like an advanced route to attempt.
