02-10-2017 01:27 PM
I should clarify, it's the act of re-mapping the sequence parameters that causes it to break.
02-10-2017 01:36 PM
Quite interesting - b/c if missing parameters really use default values, then calculated value in the expression will contain division on 0 - what should drop an error at the end... Can you check during run-time, what is the value of the resulting (calculated) parameter for that expression?
By the way, did you use "Check Expression for Errors" for the expression step? It also does not drop an error?
Call sequence by expression - this is option for Sequence Call step type (there is checkbox upper than "Use Current File" option, for selection of subsequence to call). It allows to select sequence to call by expression, not in the fixed way.
02-10-2017 02:04 PM
@kosist90 wrote:
Quite interesting - b/c if missing parameters really use default values, then calculated value in the expression will contain division on 0 - what should drop an error at the end... Can you check during run-time, what is the value of the resulting (calculated) parameter for that expression?
Yes, it isn't using default values, it's actually using the values passed in! I am monitoring the value of the calculation during runtime.
By the way, did you use "Check Expression for Errors" for the expression step? It also does not drop an error?
If I check for errors, it does tell me that the parameter does not exist.
Call sequence by expression - this is option for Sequence Call step type (there is checkbox upper than "Use Current File" option, for selection of subsequence to call). It allows to select sequence to call by expression, not in the fixed way.
I see, thanks!