This content has been marked as final. Show 1 reply
In this regards task flows they are no different from 3GL functions and the same issues of the stability of the functions API applies. If you change the functions API/signature, you affect all the callers.
However some rudimentary testings shows:
a) If you remove the parameters from a fragment based task flow, but leave the parameters in the task flow bindings of the calling page, the excess parameters are just ignored.
b) In the similar case of calling a page based task flow via a task flow call, the task flow still runs. However the task flow call does flag that it doesn't recognize the deleted parameter that still embedded in the task flow call.
I wont test it as I suspect the result will be the same, but there's also a third way of passing parameters using a parameterMap.
Of course you could test all of this yourself with some simple examples to verify what I've said here and to reassure yourself that your strategy would work.
Note that I've tested all of this under 220.127.116.11.0, and there's no guarantees in the future Oracle wont change the implementation such there is a runtime check to enforce the excess parameters aren't removed.