Request Bundle Task Status change with active assignments

Hi ​@Christian Hitzel ,

The difference comes from where the assignments sit. When tasks are bundled, the assignments on the individual tasks are cancelled, and only the Bundle Task has an active assignment. A status change on the bundle is then pushed down to the tasks in it. Those tasks have no open assignments, so the check you see on a normal Request Task doesn't block anything.

As far as I know, there's no setting in standard to turn this check on for Bundle Tasks. I was going through the documentation and I found two options:

   * Workflow: Add a "Before" workflow on the Bundle Task status change to Work Done. Have it look for assignments that aren't Completed/Cancelled and throw an error if it finds any. This gives you the same behavior as normal Request Tasks.
   * Support case: If you think bundles should behave like normal tasks out of the box, raise a case so it can be checked as a defect or enhancement on https://support.ifs.com/csm portal. The team is going to take care of it.

Which version/update are you on, and are the status changes made in the web client or on mobile?

Best,

Gleb

 ​@Christian Hitzel not entirely sure I get what your flow is? 

Are you saying that someone has started a work assignment on a bundle and then someone else goes in and sets that to work done?

I tested this in 26R1 and got this error.
The task cannot be set to Work Done due to existence of active assignments.

 

Hi,

​@gleb.batov : Thanks for your reply. Bundle Tasks behave differently in other aspects as well. For example are workflow configurations based on Task Leaders not possible.
I will look into opening a support case.

​@anmise : Yes, exactly. The technician starts working on the Bundle Task assignment via MWO App. He doesnt complete it directly when the work is finished (for example if multiple technicians work on the same Bundle Task) and Service Sales / Backoffice wants to invoice the Bundle Task. They need it in “Work Done” so they change the Bundle Task status, despite not all Assignments being in status “completed”. For singular Request Tasks this is not possible, but for Bundle Tasks it unfortunately is possible by default.
We are on 25R2. So it sounds like it might be fixed in the next update.
Do you have the possibility to test the behaviour in a 25R2 environment to verify my finding?

Thanks,

Tested in 25R2 SU11 and I get the same error. Which SU are you on?
 

​@anmise : SU7. We will get SU10 in November.