I posted the same into QA section, but let me post to Feature request category this time.
For schedule event, we are able to apply "Condition" when the BOT is fired or not with the arbtrary detailed conditions. For instance, we set event to run on every Monday, but we wish NOT to run the BOT if the Monday fall on 1st day of each month. Then we pass an expression to the condition, something like
Weeknum(TODAY())<>2
However, oddly enough, this condition field disappear when we turn on "ForEachRowInTable" option.
This does not make any sense to me.
Regardless of "ForEachRowInTable" option is on/off, the condition should be available for either case.
By turning on this option, yes, we will have "row filter condition", but why we are currenly not able to set "Condition" if or not to run the BOT?
"Condition" and "Row filter condition" are completely different things.
In this sample case, when we wish to run a scheduled bot on every monday, then we simply pass Weeknum(TODAY())<>2 expression to "condition" field in case where the ForEachRow condition is OFF.
However, the condition field is made not avaialbe for "ForEachRow" option. To do the same, we need to pass the same expression VC of the source table. This is only workaround, but we need to mix two different things,
1) contidion when the bot is to work,
2) Row fIlter condition
We have to nest the 1) into 2), which is tedious.
The best solution is to keep the "Condition" option availale all the time.
The previous post link