Summary
Workflows are useful in controlling how your work is carried out on Oneserve. Below are some typical examples of how you can set up workflows for different types of work.
Examples
Standard/Simple Workflows
The standard steps have been included in this simple workflow. You can have your jobs flow in different directions: they can go backwards, forwards, or round in a loop until the steps have been completed.
- The steps used by the mobile application on this flow would be
- Oneserve Workflow Builder - The flow diagram above will appear like this in Oneserve
Void/Planned Workflow
The standard steps have been included in this simple workflow. You can have your jobs flow in different directions, they can go backward, forwards or round in a loop until the steps have been completed. Void works tend to have a Pre-inspection phase to capture what work needs to be completed and post inspections to check everything has been finished to the company standards.
- Oneserve Workflow Builder - The flow diagram above will appear like this in Oneserve
Servicing Workflow
The standard steps have been included in this simple workflow. You can have your jobs flow in different directions, they can go backward, forwards or round in a loop until the steps have been completed. The important part for Gas servicing is the loop for additional appointments, after 2 or 3 subsequent appointments you may need to add a legal stage. This will allow a report or search view to flag jobs that require urgent actions.
- With servicing you can trigger different letters to inform the tenant of the pending appointment
- Oneserve Workflow Builder - The flow diagram above will appear like this in Oneserve
Quoted Work Workflow
The standard steps to include the steps for raising and using quotes. You can have your jobs flow in different directions, they can go backward, forwards or round in a loop until the steps have been completed.
- Oneserve Workflow Builder - The flow diagram above will appear like this in Oneserve
Transition Rollbacks
Each step can have a number of transitions, this can be to move the job onto two different steps or move backwards to fix mistakes.
The Transition for the rollback will look something similar to this:
- Transition View - If you use the Basic or Advance screen you will be able to add notes as to why the job requires a rollback
- Transition Note Types - One of the options is Job Rollback Reason, you will be able to add you own reasons to this note type so when your users move the job it will display a drop-down of reasons to select from.
- Button Sequence - This would be 2 or higher so it doesn't affect the job moving automatically on the mobile
- Condition - There is a default Rollback Job right but you will be able to create a new right and assigned it to the required user types
- Post Functions - Use a standard Event or rollback or you can create individual events to represent the status the job will move from or to.