Lite Release Notes


Job - Resource Tab 

The tab for resources on jobs has been refreshed with a new design 

  • The 'New Appointment' button has moved to the top of the page and renamed to be Schedule Appointment
  • The buttons for Cancel, Reschedule and update have been placed in a Actions button
  • The appointment table use to display 3 appointments at a time, any more than 3 and you use to scroll within the table. We have removed the 3 appointment restriction so you will be able to see more appointments on the page.



Development IDSystem AreaDescription
OSD-4596 Calendar View The calendar view has been modified to use a different default colour pallet to display resources working/non working time and appointments. You will have the option to change the colour set against particular resources.
OSD-4473 Client Ref Field The length of the Ref field on the QJC which populates client ref was set to 50. The length on the modify job details screen only allowed 20 characters. We have increased this to 50 characters so it matches the QJC.
OSD-4363 Contact details on a job The job details screen will now show the preferred contact type by displaying (Preferred) after the number or email. This was added because you can have multiple contact numbers for each contact but it was difficult to determine what number should be used first.
OSD-4197 Job - Resource tab After scheduling or rescheduling appointments it will now return the user to the job resource tab instead of job details
OSD-4187 Mobile Appointment A new flag against resources has been created to limit the mobile device to only show one appointment at a time. This can be useful to ensure your mobile users complete the appointments in the order chosen by your schedulers. The next appointment in the Not Started list will only appear once the user has completed an appointment or marked one as additional appointment required. This option can be found on the Resource tab under the Admin Team section.
OSD-2235 Mobile Appointment Order The Mobile application displays Pending and in progress appointments in ascending order. We have changed the completed appointments from ascending to descending so engineers can easily find the last appointment they have completed
OSD-4449 Pooled Scheduler The pooled scheduler would use additional working time allocated to engineers before the standard calendar time started to display the travel time for the appointment. We have prevented travel or working time for appointments appearing in additional working time unless override priorities has been selected.
OSD-4449 Scheduler - Drive Time We have prevented the pooled appointment screen from allocating appointment drive time outside of working time and into additional working time allocated to the resource. EG Out of hours time assigned to engineer A from 06:00 till 09:00, calendar time starts at 9AM. The pooled screen would have added the drive time to the out of hour's 06:00 till 09:00 with the appointment time starting at 9am. Now the pooled screen will allocate the appointment working and travel time within standard working time unless override priorities have been selected
OSD-4332 Search Filters The basic filters on the search page had a filter called Search which has been removed now. This filter is not required as you have the main search box as default on every view.
OSD-4453 Search - Sites The field on the Sites page called 'code' has been added to the site search page as a column and basic filter
OSD-4475 Search - Save As The option to save as against existing views now has the option to select what group you would like to save it to. Before it use to save it to the group the original view was within
OSD-4591 Site Details - Area The field for Area has been added back to the Site Details page
OSD-4296 Team/Resource Working and Non Working time events When you hover over working or non-working events against Resources or Teams it will display the name of the user who created or modified the event. We did have a problem where the name was actually showing the name of the logged in user and not the user linked to the event. This has been resolved.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request