Hi I would suggest that you raise an SR.
I did Viktor. It's been a week almost. No response yet :)
1 person found this helpful
Though I do not consider it as a bug, but would be a good feature to have.
In the mean time, you may try following workaround to achieve same result.
I suggest, you create one more function - Function C and set the dependencies in PS1 as Function A -> Function B and Function B -> Function C
Also, in the last stage of decomposition of FunctionC (ie SignificantUpdate) set a condition, so that FunctionC Executable component will be created for DELETE line.
Similarly, in the last stage of decomposition of FunctionA (ie SignificantUpdate) set a condition, so that FunctionA Executable component will be created for ADD line.
Obviously, you have to take necessary care to ensure, both of the executable components (A, C) send payload to same target system.
I am going through this conversation and understanding the solution aspects for this type of scenario.
What do you mean by SignificantUpdate? Is that something OOTB related feature?
The OOTB O2A PIP cartridges have the following stages -
- Determine Fulfillment Function
- Determine Target System
- Determine Processing Granularity
- Determine Significant Updates
I hope that helps
Did solution mentioned by Sumanta worked in your case or you implemented any other solution?
Please let us know your comments because we came across same situation.