Main task followed by related tasks using Process model

Hi team,

I have a use case where I need to create tasks for users, but there is a parent-child relationship between tasks. In one interface, I will collect the details of the task, and users can add additional tasks to an already existing task. So, a parent task will have N number of child/related tasks, which will be stored in a table called "task details". Daily, once I trigger a process, it will query the task details and create the tasks. The thing I need is for the parent task to be created first, followed by related tasks in the order the user gave them. It would be simple to achieve this using a subprocess and looping the task creation by sorting the data using datetime. However, I wish to use the startprocess MNI, as it won't affect performance and to avoid instances paused by errors (subprocess will stop in this case). I don't know how to order the data or loop the data to achieve this. Any suggestions?

Thanks in advance

  

 
 

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    Hi   Currently there is no specific volume of the tasks mentioned. When you go with MNI process,  MNI takes more memory.t is not good when we are using more than 1000 iterations, consumes more storage.using MNI does spawn all instances on the same execution engine. This can be an issue with a large number of instances (especially if your MNI is run on a sub-process node) because it can create a load unbalance between multiple execution engines. You would think of an alternative approaches like record/database approach

Reply
  • 0
    Certified Senior Developer

    Hi   Currently there is no specific volume of the tasks mentioned. When you go with MNI process,  MNI takes more memory.t is not good when we are using more than 1000 iterations, consumes more storage.using MNI does spawn all instances on the same execution engine. This can be an issue with a large number of instances (especially if your MNI is run on a sub-process node) because it can create a load unbalance between multiple execution engines. You would think of an alternative approaches like record/database approach

Children
No Data