Options
  • Locked Locked
  • Replies 15 replies
  • Subscribers 9 subscribers
  • Views 1241 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using assignments and workflows to create a task with subtasks

jarlemag
I want to create a task or object representing an activity, "Source code review" (SCR), with several linked subtasks ("review step" tasks) which must all be completed to mark the task as completed. The subtasks should only be assigned to/be able to be completed by the person who has been assigned the main task.

The way I've approached this is to create a new object type, "validation task" and two classes, "source code review" for the main task type, and "source code review step" for the sub-task/step. I've added "Reviewer" (the person who should perform the SCR task) as a required property of the SCR object. I've also created two workflows, "source code review workflow" to use with the main SCR object, and a "Pass/Fail"

However, I can't see any way to make the workflow state transition for the main object dependent on the workflow state of the linked objects. Is this possible without scripting?

I've attached an export package with the metadata objects/classes, in case my explanation is not precise enough. It can be summarized as follows:

Object type: Validation task

Class: Source code review
Required property: "Included source code review steps" (multi-select from list of objects with class "source code review step")
Workflow: "Source code review workflow" (SCR Pending (object is automatically assigned to user specified in "reviewer" metadata) -> SCR complete (PASS) or SCR complete (FAIL) )

(The SCR workflow will be more complex in its finished state, so it can't be the same PASS/FAIL workflow used for the sub-steps)

Class: Source code review step
Required property: Acceptance criteria (free text description)
Workflow: PASS/FAIL (no state -> PASS, FAIL or "Not Applicable")
SCR metadata.zip

  • Sorry, I haven't worked more on this. Would still like to get it working...


    Thanks for your quick response.

    Maybe tigu managed to get it working.
  • Dear DL,

    Unfortunately I never got this working.
    We realized that concept of Assignments was not applicable for our use case.


  • Unfortunately I never got this working.
    We realized that concept of Assignments was not applicable for our use case.


    Thanks for letting me know.
  • In the meantime I have had a chance to try out the Hierarchy Manager add on (Part of Compliance Kit). It is designed to handle situations like this. For instance I have configured a situation where 30 - 50 objects each have to complete a small workflow and reach a specific state. When all of them have reached that state the Hierarchy Manager triggers a transition in the primary workflow. The add on has a price tag, but it really can manage situations like this one.
  • For anyone looking for information on marking an assignment completed in a script/VAF application, here are a couple of tips from my colleagues:

    - Just adding the user toMFBuiltInPropertyDefCompletedBy is not enough, but you also need to remove the user from MFBuildInPropertyDefAssignedTo for the assignment to be properly marked as completed.
    - There's a handymethod MarkAssignmentCompleteByUser for doing all that stuff that should be also future-proof should more tricks appear in the future that are required.
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.