This release includes a selection of the most hotly requested features by you, our customers. Highlights include:
A simplified Ops List in the native app (read more below, it's rather clever!)
Inline Op responses for quicker, easier Op completion
Ops that can span multiple days, weeks or even months
Optional Issue 'overrides' (enabling the performer to reclassify as appropriate)
Many other small improvements to make the system better for you each month
Simplified Ops List in the Native App
All Ops can now be seen in a single list (regardless of whether they were scheduled or started on-demand). This list can be filtered to show only the Ops that are of most interest using time-based filters (as well as Team and Role filters):
The list is sorted by the Op deadline date/time so that you see the Op that needs completing first at the top. Other indicators show whether they are started (In Progress) or not.
Note that the list now includes Ops that are due to start up to 24 hours in advance (read more about Ops that span multiple days below).
When starting a new on-demand (i.e. ad-hoc) Op, the user will be prompted to enter a deadline date and time. This has three major benefits:
The on-demand Op will appear in the single Ops list correctly prioritised based on the due date/time.
On-demand Ops are no longer forgotten about.
Notifications can be sent for On-demand Ops that are 'Late'
Inline Op Responses
To make completing Ops quicker and easier, responses to 'text entry' question types (such as numbers and free-text) are now entered 'inline' meaning there are no popups to open and close.
Ops Spanning Multiple Days, Weeks and Months
You told us that some of your processes do not necessarily need to be competed on the same day. For example, electrical testing can be completed anytime 'this week'.
To facilitate this Ops now have a Start and End Date (in addition to Start/End Time).
In addition to facilitating Ops with a duration of more than 24 hours, this means it is now also possible to schedule Ops to start in the future e.g. a daily check that you want to become active from the 1st of the following month.
Optional Issue Overrides
When carrying out a check, audit or risk assessment, sometimes a 'negative' response will be configured to trigger a follow-up Issue or action. The default settings for this are configured by Admins in the web app (on the Issue question type) and include, for example:
Type (which determines auto-assigning of the Issue)
Flag (normally used to indicate priority)
Where it is helpful to allow it, Admins can now allow the Op performer to override these default settings using their own expertise to reclassify the Issue - thus ensuring it is assigned to the correct people/team with an appropriate priority first time. This has the dual benefits of:
Quicker time to resolve Issues (as they are immediately assigned correctly)
Reduced Admin overhead with Issue management (reassigning and reprioritising)
In addition, the Op Question and Response are included in the Issue details to give the people working on it more context.