How to trigger Flow on extended tables

[Tim84]

Hi all,

so I'm trying to run the same flow on multiple tables, that all have a extension relationship.

Let's say I want a flow to run for ALL task tables and I create a flow based on [task]. This Flow will only trigger for records directly on [task] but not for any extended tables. Can I somehow get this flow working for all the extended tables aswell?

[quintenvandenb1]

Could you please clarify your statement "This Flow will only trigger for records directly on [task] but not for any child tables".

If you are talking about incident, change, problem, these are not child tables but tables extending the task table. In fact you should not create task records directly without a class.

[Tim84]

Hi Quinten,

I use terms child table and extended table synonymously (if this is wrong from your POV, maybe you can clarify why that is).

In this case:

"This Flow will only trigger for records directly on [task] but not for any extended tables".

--> but of couse I want this flow to trigger on extended tables, because I do not create any records directly on task.

[quintenvandenb1]

The reason why extended and child is different, a child table is a table that has a reference to a parent table. For incident, change, etc , these are all tables extending task, meaning, they don't have a reference to a parent record, they are the record itself.

To give an answer on your question, you could use a flow designer or workflow that triggers on task directly however I don't recommend you doing that.

The task table is a table very high in hierarchy and you are potentially putting yourself for blocking issues if you are going to trigger a workflow or flow designer for the entire task table.

Also your workflow will only be able to access fields that are specific to the task table. Example, no incident_state.

Only try to touch the extending tables, not the task table.

[Tim84]

Hi Quinten,

thanks, for the clarification, I edited the question to be easier to understand.

I understand your reasoning for not creating a flow for the task table and I understand the limitations that come with it, I was just curious why Business Rules trigger by updates from an extended table and Flows do not.

Task was just an example to visualize what I'm trying to achieve. We are using Cases and extended custom tables to represent different Case types (which is SN best practice), but I don't want to create a Flow for every single one of these tables.
Especially if i want to change the flows later on, I will always have to update multiple Flows.