My answers are inline:
Let me assume a simple case.
We have two tables.
Each table has one bot, so in total, app has 2 bots. Meaning we have two process as well, each assigned to each bot.
A table doesn’t have any bots! A bot binds an event to a process. A process is connected to a table (entity) that is also referred to as the process input.
Then we keep working on BOT1. When we modify the step or add new step, select call a process.
Then we are able to select the Process which is living in other table…
I am assuming that you mean that this process is connected to a different table
My understanding Process can live with only a single table.
Correct, a process is connected to only a single table at any point in time,
Likewise, when we select task as step, then the listed up task (actions) are only related to that table where bot lives.
Is this behavior intentionally?
Yes. Any steps/tasks/actions in a given process (p1) are always related to the table (t1) that is the process input.
For me, it is apparently confusing and I dont come up wiht use case where we select process wihch resides in other table.
This is a very common use case. Imagine that you have an process called “Approval Process” (that is connected to the “approval” table - which has a set of generic inputs you need to make approval decisions). You have a requirement to provide approval capability in multiple bots. Many bots (each of the processes in these bots will be connected to their own tables) can re-use this same “Approval Process” by simply using a “Call process” step.