When using the graphical scheduler application enhance the ‘Commit Changes’ functionality so users can commit just the work orders that they are working on

Description:

When using the graphical scheduler application enhance the ‘Commit Changes’ functionality so users can commit just the work orders that they are working on.

We believe this commit changes functionality is also present in the Graphical Assignment Application and it should be enhanced as well.

describe what you want:

When executing ‘Commit Changes’ action, apply existing commit functionality on WO records that are selected.

The workorders are selected using the standard checkbox for each WO record.

The existing functionality will always commit all the workorders even if the user is just working on a subset of the workorders.

The customer plans their workorders on a monthly basis and this can lead to 1,000 workorders being available to the scheduler application.

The user is making changes to 250 of those workorders.

The current functionality means that when the user commits the changes all 1,000 workorders are updated.

This means that 750 workorders being updated with the incorrect target start date and the user experiences a penalty because they have to wait for 750 workorders to be updated.

Applying the incorrect target start date also makes it very difficult to identify the remaining 750 workorders because they have been set with the incorrect date.

So the users experience several problems:

• There is a potentially serious business impact if the users forget to schedule an important piece of work that has a long lead time

  • in that case a failure to schedule the work could lead to extended delays before starting the work and knock on effects on the work

• Staff availability is likely to be adversely affected because scheduled work is not planned efficiently OR because people have to be taken off the scheduled jobs when the mistakes have been identified

• Waiting for 750 workorders to be updated unnecessarily

  • This can be a substantial delay when there are large numbers of workorders to save

  • The overall effect of this is that schedulers may not be able to schedule as many tasks as they could because they are having to wait

• System potentially triggers off save events, for automation scripts/java classes, for records that should not be processed

• Users have to use a custom query as a workaround to identify these records

  • This creates an unnecessary step that users will often forget to follow and so miss records

  • This will also lead to unnecessary helpdesk calls because users forgot to schedule the work

• Support staff will be delayed because they will have to work through log messages associated with the extra

Use case:

Scheduler users working on subsets of schedules with large numbers of workorders will benefit the most from this

They would select the work orders and use the “commit changes” button

The commit change could be provided using either of two methods:

1. Use the existing button and the code behind the button only commits the changes to the selected workorders

2. Add a new “commit selected changes” button that only commits the records to the selected workorders

   1. Existing customers would be able to use the existing functionality