Why can't multiple engineers edit a job within the Job Sheet App?

Only the Primary engineer on a job can update the majority of the fields such as "Actual work done" etc within the Job Sheet App. 

The reason for this is because otherwise there could be situations where the changes from one engineer would overwrite (and therefore completely lose) changes made by another engineer.

Consider the following scenario:

• Engineer A and Engineer B have both downloaded the latest version of a job to the Job Sheet App.
• Engineer A makes changes to the "Actual work done" field and saves it.
• Engineer B also makes changes to the "Actual work done" field without getting the latest version of the job and therefore the version of the job they have on their device would not include the changes that were recently added by Engineer A
  (this could happen if Engineer B updated the job at the same time as Engineer A, if they updated the job without refreshing the list of jobs or if they did not have an internet connection when they were updating the job because the Job Sheet App still works when they are offline).
• This would mean that the changes Engineer B made would completely overwrite the changes made by Engineer A and the changes made by Engineer A would be completely lost.

When we first wrote the Job Sheet App we did consider the possibility of allowing multiple engineers to edit all fields and for there to be a warning when saving to alert users of the fact they would be overwriting changes made by other engineers, however, this would have meant that we would need to allow engineers to possibly merge the data in what could be a multitude of fields (our customers can add custom fields to the system so there is no limit as to how many fields could be updated by an engineer in one go), engineers may not necessarily know what data to merge (i.e. what should be kept etc) and the whole process could get very complicated and confusing. 

A similar problem would be likely if we set it up so that someone in the Management Console had to merge the data, it could become a massive overhead of having to merge various data on each job every time engineers save their changes.

The example above is only if 2 engineers were assigned to a job and only if the "Actual work done" field was updated, if a job had more than 2 engineers assigned and/or more fields were updated at the same time then the whole problem gets compounded further and it would be completely unmanageable for anyone that had to try and merge the data from multiple engineers.

You can change the Primary engineer of a job on the "Engineers" tab within the job in the Management Console, therefore, allowing you to switch to a new primary engineer based on who will be attending the job next, this would then give control to that engineer allowing them to update all the fields for that job.