The workflow section of admin settings allows admins to customize their scheduling workflow.
Tip
Access to the admin settings is provided via the user profile button (at the top-right of the console).
In the jobs section the following settings can be configured:
If disabled, jobs are automatically accepted (confirmed) on behalf of the allocated resource(s) when the job is dispatched (also known as "Auto-accept").
The default value is ON.
Note
The nested options (relating to jobs being declined) are disabled when this option is deselected (OFF).
When this setting is enabled, resources have the option to decline allocated jobs from their mobile devices. When it is not enabled, resources can only accept jobs allocated to them.
The default value is ON.
Note
This setting requires "Resources need to accept or decline dispatched job allocations" to be ON before it can be enabled.
This allows the administrator to decide if resources should supply a reason for declining jobs (at the organization level). Once enabled, resources who decline allocated jobs from the mobile app are prompted to pick a reason from a drop-down menu.
The default value is OFF.
Note
This setting requires "Resources need to accept or decline dispatched job allocations" to be ON before it can be enabled.
When this setting is turned on, a resource in the field can cancel a job that they have already accepted (Note: a cancellation reason must be given). A similar option exists in Job Templates (for individual job types). If the setting is enabled on this screen (Workflow-Jobs) it will override the job templates setting, i.e., if enabled globally, the option is automatically selected and it cannot be changed per job template.
The default value is OFF.
With this setting applied, when a job is canceled, schedulers will see previously allocated resources as having free capacity again, i.e., they are available to receive another job. Applying this setting affects future job allocations (it is not applied retrospectively).
The default value is OFF.
Some organizations like to differentiate between notes and completion notes. Using this setting, admins can enable or disable the "Completion Notes" field on the mobile app, at an organizational level.
The default value is ON.
This setting allows an admin to decide if resources within the organization must enter "Completion Notes" when they mark a job as complete. For the mobile user, this can be more efficient as they are prompted to fill in notes rather than having to perform the action separately.
The default value is OFF.
Note
This setting requires "Enable job completion notes" to be ON before it can be enabled.
Once this setting is enabled, certain aspects of a job can no longer be changed using the Skedulo mobile app (i.e., completed jobs become read-only). These include:
Completion notes.
Manage times.
Attachments.
Signatures.
Notes.
Custom fields.
Features not affected are:
Custom Forms.
Visualforce Forms.
Chat (from within a job).
The default value is OFF.
With this setting is enabled, resources can skip job-related tasks and complete their jobs. The opposite is also possible, i.e., to make tasks mandatory, ensure this setting is enabled.
The default value is OFF.
This setting allows admins to enable or disable the action "Follow-up Job" in the Skedulo mobile app.
The default value is ON.
When this is enabled, the "Assign to myself" switch is made available in the Skedulo mobile app for "Follow-up Job".
The default value is ON.
Note
"Enable follow up jobs" must be ON before this setting can be enabled.
In the job status section the following settings can be configured:
This allows the scheduler to nominate one allocated resource to process jobs (from their mobile device) on behalf of all of the other allocated resources on the same job. This relieves the other resources from the responsibility of updating the job status, allowing them to concentrate on other tasks (applies when jobs are in status "In Progress" and "Complete").
The default value is OFF.
When a resource changes the job status on their mobile device, a timestamp is recorded against that action, and it is stored as a record of when each transition occurred. If a resource makes a state transition earlier or later than when they planned (e.g., by accidentally pressing a button), with this feature enabled, they can update the timestamps by selecting the "Manage Times" option from the "Actions" button of the Skedulo mobile app. This allows them to change the time and date of the following transitions: Start Travel, Check-in, In Progress, and Complete.
The default value is ON.
Admins can apply this setting to remove the "En Route" job status and "Start Travel" job allocation status if they hold no value in their business workflow. Enabling this setting will remove the "Start Travel" action button from the mobile app.
The default value is OFF.
Admins can apply this setting to remove the "On Site" job status and "Checked In" job allocation status if they hold no value in their business workflow. Enabling this setting will remove the "Checked In" action button from the mobile app.
The default value is OFF.
This allows the scheduler to stipulate how far in advance they will allow their resources to start their jobs (hours/minutes).
If "Prevent resources from starting jobs early" is checked, the scheduler can choose how long before a job activates the "Start Travel" button on the mobile app. The duration can be stepped in increments of 15 minutes, or the user can enter specific values. There is no maximum value.
For example, you want to prevent your field staff from arriving too early at customer premises. If you set this feature to 1 hour, your resource cannot tap the "Start Travel" button in their mobile app until they are within 60 minutes of the start time of the job.
The default value is OFF.
In the recurring schedules section the following settings can be configured:
By default, jobs in a recurring schedule are dispatched as a group. If an allocated resource accepts one job in the series, they automatically take all other jobs in that series as well. However, if resources are required to acknowledge each job individually, then "Dispatch and accept per job" needs to be configured. If it is set here, at a global level, it applies to all recurring schedules across an organization.
The default value is OFF.
After saving your selection ("Auto allocate" or "Scheduler controls allocations"), a confirmation modal provides the following information:
"This will affect all existing jobs or shifts under offer. Any existing offer responses may need to be reviewed. Are you sure you want to continue?"
To proceed with the changes, click the "Yes, update setting" button. Click "Cancel" to return to your previous saved state.
How do you want to allocate resources to jobs under offer?
Resources will be automatically allocated to the job when claiming their offer until the job is fully allocated.
The default value is OFF.
How do you want to allocate resources to shifts under offer?
Resources will be automatically allocated to the shift when claiming their offer until the shift is fully allocated.
The default value is OFF.
Comments
0 comments
Article is closed for comments.