Hi @JoeM-AU,

FSM Mobile is very sensitive to increases in data traffic so you would run the risk of significant slow down by adding 5 times the tasks down to every device especially with how many changes throughout the day this is likely to have.

Would the parts required be none by the back office as well or is this something that the field techs determine? If known in back office then the parts can be added to the task, compared to the field techs on hand parts and a notification could be sent beginning of the week with the rough list of parts above what the tech has on hand. Something like that would be a lot lighter on the system whilst still providing the required information to the tech. 

The above might not be viable but is just an example of other ways around this sort of business need that better suits FSM’s design. Essentially, you will need to try to boil it down to what is the minnimum amount of information the tech needs, when and for how long and then do the work in the back office FSM to curate this data so you can send only that required information as and when its needed.

Kind regards,

Lee Pinchbeck

I don’t have time to flesh out the idea, but you could do something like the baseline MMA_TASK_HISTORY_VIEW to pull just the basic info you need for the future tasks and then display them on a configurable List screen.