Know the context of the table and variant when starting a table task

There is no out-of-the-box solution for this. However, you could achieve this by updating the default value of the tab_variant_id column in each of the variant tables.

Depending on the number of variants involved, it may be more efficient to use the Dynamic Model for this purpose:
https://docs.thinkwisesoftware.com/docs/sf/dynamic_model

​@J. de Lange We developed a similar solution using Dynamic Model at Wagenborg, but can’t remember having this issue. Except for the fact that we stored a SharePoint link in the ‘Maintenance’ table and did an Open link action, I feel our implementation was very similar. I don’t remember us having this issue though. 

Could you shed a light on what is different in the Wagenborg model? Did we create different Tasks for each Subject perhaps?

Hi Sjoerd,

I assume the default value won't change on the current table variant when you're not adding/updating rows.So this may not work? 

Perhaps it's possible to create a task variant per table variant with a task_parmtr called tab_variant_id and filling the default value of the task_parmtr with each variant_table_id. 
So we still have one task as the starting point in the process flow and the task variant can return the current tab_variant_id as output.

Could this work?

Hi Kevin,

The current tab_variant_id does not change when adding or updating rows. However, by using the dynamic model you can update the default value per variant. This allows you to keep a single table task and map both tab_id and tab_variant_id.

Creating a task variant for each table variant is indeed another option, but it involves quite a few manual steps. Using the dynamic model can help avoid that overhead. That said, your proposed solution would also work.