Receive next task when previous is already done?

​@Miruna M as far as I know, when data is commited in PSO, the assignment it’s not automatically transferred to MWO. 

For MWO transfer to happen automatically you’ll need to schedule Transfer Work Assignments to Mobile. There you have TRANSFER_WINDOW parameter that could be set to 1 → then your technician will only get in MWO the tasks for that specific day.

I don’t think there’s any functionality to transfer to MWO only one task at a time. ​@Alexander Heinze would you have any idea on this?

What about configuring drip-scheduling in PSO i.e., only commit the next task to the technician? And once it’s committed, send it to PSO.

Hi ​@Alexander Heinze - how would you set this up please? using Commit rule - Maximum Activities = 1? Besides this we are going to create database task schedule to move the task to MWO automatically.

The example in IFS Cloud - Scheduling demystified (24R2) | IFS Community has exactly that as an example.

​@roman.fara see page 59 in Scheduling Demystified 24R2.

Hi ​@Alexander Heinze and ​@Marcel.Ausan,

We tried to set those rules, we created a rule, a rule collection, we checked the modelling dataset...everything is fine. We created 2 tasks and both of them were allocated to the same resource. We changed the status to ,,Committed,, for the first activity and I was expecting that the system would not let me change the status for the second activity as well. But I could do it….so, at this moment, I have two activities in status ,,committed,, for the same resource even if i set the parameter ,,MaximumCommitedActivities,, to 1. It s not fine, I guess...

My wonder is whether this rule only applies when the system changes these statuses automatically or does it also applies when I change the statuses manually in PSO?

Thank you in advance for your help!

Regards,

Miruna

The goal of this rule is to automatically commit allocations, not to constrain manual updates. Have a look at the PSO documentation, document Status Changes.