Skip to main content

Hello,

 

We have been experiencing inconsistent behavior when WT status set to Work Done (Automatically) when the Assignments belong to the Work Task get completed. In some instances, the Work Task status stays in ‘Work Started’ Status without changing to Work Done. 

 

In this Example, the WT has a single Work Assignment and the MWO user completed the Work Assignment and Returned to  mobile. The IFS Cloud Work Assignment Status is ‘Completed’ and the ‘Time to Completion’ filed is ‘0’. 

 

 

 

 

But the Work Task is still in ‘Work Started’ status. Are there any other rules that could affect  changing the Status of the Work Task to ‘Work Done’. ? Also this behavior is intermittent as well.

 

Thanks and Regards,

 

 

 

The work task status is also driven from the resource demands.  If there are still resource demands present that have not yet been consumed, then the work task status will stay as Work Started regardless of the status of the work assignments.

We had a lot of issues early on after go-live where coordinators were using direct allocations instead of assigning against a resource demand, thus leaving the demand unconsumed.  Once we cleared that up, the issue went away.

Did your task use a Workflow Configuration? I saw a similar issue with workflow where the task remained in Work Started, w/o Workflow it went to Complete.

Hi @PLabor , Yes I was able to recreate this. In my example the a resource demand line was not consumed. Thank you!

@Alexander Heinze Yes we are using workflow configurations, but in this scenario it was due to unconsumed resource demand line.  Thanks!

Reply


Terms & ConditionsCookie settings