0
HI,
i am working with SBM composer, and trying to use multi relational field to check the states of sibling subtasks. I have two relational fields in same primary table, "parent task" which is a single field, "subtask" which is multirelational. In my workflow I have used post options to copy the id of created subtask item in the 'subtask' field of the parent item, and id of the parent item in the 'parent task' field of the new item. However, since both items are using the same form, they both have 'subtasks field' in their respective forms. When I create a second and a third subtask the existing field from the parent task gets carried over in this field. This ends up relating the sibling subtasks as parent and child of each other causing confusion using triggers. Hopefully, if someone can comprehend this issue and provide a solution I would really appreciate it.
Thanks.
P.S. I am trying to transition the parent task upon the subtasks reaching a common state etc using triggers.
Responses (1)
  • Accepted Answer

    Thursday, November 09 2017, 03:33 PM - #Permalink
    0
    Hi James, are you just using the standard config within Composer to populate the parent & subtask fields. We use this functionality a lot and have never had the situation where the "subtasks" get related to one another.

    I am assuming that what you are doing is going to the "parent" and creating sub-task 1 - then from the parent creating sub-task 2, etc, etc. In Composer the Post Options of the transition should be setup with:

    "Set new item in original item's field": SubTask field
    "Set original item in new item's field": Parent task field


    Where you could potentially be having issues if you are copying any of the issues, as the copy will copy the values from the fields - so that can lead to some odd data issues.

    Sorry I can't be any more help.
    The reply is currently minimized Show
Your Reply

Recent Tweets

Twitter response: "Invalid or expired token."