Later this year we intend to upgrade table, task and report variants to first-class citizens so that they can also, for example, be used for access control by Indicium. Once that has happened, this idea will probably quite easy to implement.
In the mean time, you can always just create a copy of your task.
Once this is implemented, can we than get one task for "follow trunk" and one task for "follow branch" in the merging screen of the SF?
In case of large sets of conflicts, it happens that I need to wait for the popup to display in the first place, select either branch or trunk, click OK and then wait for the actual execution of the task.
If there were two distinct tasks from the outset, I could select all the actions that follow 'branch', click the task and do something else without interruption halfway.
Isn’t it as simple as just additionally adding column “task_variant_id” to PK of table “tab_task” ? (as this is the error I get when trying to add a variant of a task to the same table)
Isn’t it as simple as just additionally adding column “task_variant_id” to PK of table “tab_task” ? (as this is the error I get when trying to add a variant of a task to the same table)
Thanks
On first glance, it looks that way but we have investigate this earlier and decided to not pursue the implementation yet.
Currently the Key of Tab_task is tab_id and task_id. All GUI's, context logic inside the GUI's and Indicium, Drag-drop, scheduler and other components are not made to handle this at the moment.
It would be quite the idea to implement due to the complexity.
This is definitely on my radar as Product Manager. The Thinkwise Platform is all about rapid development and re-using as much as possible, and this issue doesn't fit in with that concept. We'll have a prioritization session in September, and depending on the decisions taken there we will be able to tell more about expected timelines.
Once this idea is going to be worked out, don't forget to include this idea as well. This will allow for more generically applicable tasks, so less control procedures and less template parameters:
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.