Scheduled Event - Unable to select the target table in case of ”entire table" option

[Koichi_Tsuji]

I m not sure why and it is possible i overlook something, but we are currently not able to select the target table in case of Scheduled Event at the time we toggle OFF the “foreachrowintable” option.

Above screenshot is taken from app with existing Report where create report option is set to ForEntiretable. Then we select the target table name for fire the report.

Now looking into the BOT setting , where we are missing “ForEntireTable” option, but we only have toggle button for ForEachOfRowInTable option

When we turn OFF this option, I assumed it may mean “ForEntireTable” option was selected, but still not sure. At the same time, we are not able to select target table to fire ForEntireTable. ? How we can configulate? and select the target table, while we are missing the settings ? Or does this mean we may need to set up call a process settings, and push sort of expression as process input?

@prithpal
@Dan_Bahir

@Takuya_Miyai

[Koichi_Tsuji]

Not me, but BOT said so.

[Dan_Bahir]

The scheduled events events are either “For Each Row in Table” or a generic trigger that has no payload. A “For Each Row in Table” will run a bot for each row that matches a condition. The generic trigger will just trigger a bot with no input. That is why it does not make sense to associate a table with the generic trigger. And it allows the bot to have processes that do not rely on an input.

This worked in the same way in the workflows how ever the labeling here was misleading. It was called “For Entire Table” but the provided table name was not used and did not restrict you from having an email task on another table or provide any input.

I hope that clears it up.

Dan

[Koichi_Tsuji]

Hi @Dan_Bahir

Thanks for your clarification.
I m now revisit my past understanding, but the workflow which is displaying the selection of target table might have been mislead when we select For Entire Table option.
Without selecting the target table name or slice, we are able to place any sort of expression within workflow template to retrive target data and dump over the template. So we dont need to select the name of table/slice, again in case of For Entire Table.

Furthermore, in the process under the schedule event for entire table option, should contain the raw task, rather than call a process I assume.
Whenever we call the process externally, we need to pass ID value as initial process value. Probabaly we may need to any(select) type expressoin to give and pass the value to initial process, but it should not be a frequent case to call a process under the schedule event. Just place pure task should suffice business requirement I assume.