Whatโs happening is the Event and the Process are two distinct entities. Each one is associated with a table. Changing the table associated with the Event does not change the table associated with the Process (since the process might be used elsewhere). In fact, if you saved after changing the Eventโs table you would get an error that the event is not compatible with the process.
Tasks are associated with a table as well. You can see this by editing the task in the โTasksโ tab. We suppress it in the side-panel in an attempt to reduce what is (usually) redundant information.
What youโre attempted to do is change the table for all the Botโs nested entities. Currently (after changing the event table), you would need to update the table associated with the process (on the Processes tab) as well as any Task / Action used by said process in their respective tabs. This would run into issues if any of the entities are used in a context that requires their current table.
As you can see, the editor is not well suited for this operation. Iโm not sure if thereโs an easy fix but itโs something Iโll think about. Some good news is that a fix is in for the sorting issue (pending deployment). Hopefully that will help us avoid this situation entirely. You can also type the name of the table when the dropdown is open and it should select it.
LinkedIn
Twitter
