Job Planning & Management Ideas Portal
Description: What problem is the customer facing?
Old logic PRE-appointments dictated that tenants create different jobs within a project for multi-day jobs which would put the most recently created job at the top of the list.
New logic with appointments allows a job to have multiple appointments and even appointments scheduled for the same time (to allow users to assign separate technicians to separate appointments without the risk of one technician affecting another technician's workflow). However, when scheduling a second appointment for the same timeframe as the first appointment, the order of appointments is skewed. Instead of the appointment ending in -1 always being the first of {however many appointments there are}, the new appointment(s) ending in -2 or -3 get bumped to the top of the appointment order. (Screenshot attached of current logic putting a later-scheduled appointment, indicated by the -3 at the end of the appointment #, taking order precedence despite being scheduled after the first appointment.)
Why is it useful?
To ensure that the main tech and the main appointment, which ends in -1, remains at the top of the sequential ordering of appointments.
Who would benefit from it?
All tenants with this workflow
What value does it provide the business?
Alleviates confusion, allows appointments to be viewed in order of priority and creation
Do you have a recommended solution?
It would be beneficial if the system logic takes into account both the appointment Scheduled time and the appointment CreatedOn time. So that if the Scheduled time is the same for many appointments, the CreatedOn time determines the order of appointments (1 of 3, 2 of 3, 3 of 3, etc) matches user logic.
This allows the first appointment to be considered the main appointment, is kept at the top of appointment lists because of its priority status as the main appointment, and any additional appointments scheduled for the same time follow it in order presented.
