Table of Contents
An indicator has been added next to the DB label and the 'RESET' option next to labels only appears on items that have been changed
Purchase and Invoice Functions on Work Orders
Added the ability to delete line items on the Purchase and Invoice functions on the work order record. This action is FAL controlled so that it can be managed in a controlled way.
Asset Maintenance Required Y/N flag
Introduced a 'Maintenance Required' field to the Asset record. This allows users to see if an asset needs to be included in planned maintenance schedules and whether these will be seen in any asset filtering when raising SR's and WOs.
This field can also be updated via the imports and bulk edit via the shelf
Added two new Classifications to the Access principles. This action function is controlled by giving relevant user profiles to either include or exclude the options.
Adding Child Assets
We've enhanced the Assets module to allow better controls and visibility when assigning child assets to a parent. Users can now add a child asset by selecting the '+Add Child Asset' button in the child asset widget.
The button takes users to the create asset screen. Once the record has been saved, the user will be returned to the parent asset screen and can see the child asset appear in the list.
If the user is on the child asset record, then they will be able to see the Parent asset details as shown below and vice versa. User can navigate to and from assets using the links.
Note: A child asset cannot also be a parent.
Added the ability to set up different working patterns so that these can be applied to relevant priorities, such as business hours during the day/week and out of hours overnight and weekend hours. This will then give flexibility to apply appropriate SLA's against priorities
To access the working patterns section, user will require admin privileges
From Tools > Site Admin > Calendars > Working Patterns
The following admin screen is displayed. Select 'ADD PATTERN' to create a new working pattern
Populate the required fields to build the pattern, and then finally select 'Apply' to save
To edit a pattern, select the 'Edit' button next to the working pattern. The 'Assign' button is to allocate a working pattern to a contacts working schedule
Maintenance > Reactive > Work Order Priority Response Times
When setting up priorities, select the Working pattern and flip the toggle in the Use working pattern column, this can be done on new priorities or on existing ones.
The Target Start and Target Finish Dates on the Work Orders will take in to account the working pattern hours when calculating the dates.
Inserting a Website URL/Web Address Link into a UDF Field
Users are now able to insert web URL or website links within UDF fields.
This is for both regular UDF fields and Tabular Ones
Users will need to add a title and URL in to the UDF section to create a clickable link.
Engineer Assign/Re-assign During Absence
This functionality allows users to search for work assigned to an individual and then either individually or bulk assign to other resources accordingly.
Tools > Site Admin > Power Menu > Functional Security > Maintenance > Maintenance Work Order>
A new menu has been introduced as shown below
This takes us to a new screen which shows all work orders that are currently un-assigned. Once the work orders are assigned, they disappear from this list
Users can individually assign or bulk assign to supplier/engineer.
The main screen will not consider the following statuses (For Reactive and Planned types)
· Work Done
Notifications for P1 and Self-Serve Service Requests
We've introduced notifications for when a Priority 1 and Self-Serve service requests are raised, so that key individuals are kept informed.
A new config key has been added to switch on SR mailing groups
Tools >Sys Admin> Content> Configuration
Setting up mailing groups for notifications for P1 and Self Serve SR's
To set up the mailing groups so that the required individuals are notified when P1 and self serve Sr's and P1 work orders are raised
Go to Subscriptions > Manage Subscriptions
Then select the '+ADD NEW ITEM' button
The new Mailing group add option is displayed. The user will set up two mailing groups to cover for the P1 and Self Serve SR notifications groups, selecting update button after each
Note: ensure you enter the underscore
Add contacts to the mailing groups
To add contacts to the mailing groups, to select the relevant group by checking the checkbox next to the item. This then allows you to add contacts in the Manage Members section
Once the contacts have been added to the members section, select the Save changes button. Notifications now will be sent when the relevant SR's are created. P1 will be driven by the priority and the Self serve SR will be driven by the SR type.
Note: Also, if the self serve is a P1, then both notifications will be sent out
The email notifications that are sent are dependent on which way the SR / WO is created
P1 Service Request Email content will say - This is a notification that a P1 Serve Service Request, reference - SRXXXX, has been raised.
If a P1 Work Order is created from this SR, the email content will say - This is a notification that a P1 Work order, reference - WOxxx-x, has been raised.
Self Serve SR = P1, email content will say - This is a notification that a P1 Self-Serve Service Request, reference - SRxxxx, has been raised. This requires to be Triaged before assigning to a work order for assignment
If a Work order = P1 is created from these Self-Serve P1 Service Requests, then email content will say - This is a notification that a P1 Work order, reference - WOxxx-x, has been raised.
Self-Serve SR any other priority (Not P1) email content will say - This is a notification that a Self-Serve Service Request, reference - SRxxxx, has been raised. This requires to be Triaged before assigning to a work order for assignment
No WO notification email will be received in this instance
When creating an ad-hoc Work Order, the engineer is auto assigned, and an associated SR is created in the background
WO email content should say - This is a notification that a P1 Workorder, reference - WOxxx-x, has been raised.
No SR email is required
The following is received by the users nominated to receive notifications when a P1 SR/WO and a Self Serve SR are raised
When selecting the 'Click Here' link, you are directed to the Notifications widget which shows a list of the Service Requests/ Work orders that have been raised for P1 and Self Serve. You can then review each by clicking on to see the detail. When viewed, these will be marked as 'Read'
We have introduced a new admin function the ability to delete access principles
To get to the menu option, the user would navigate via Tools > Site Admin > Power Menu > Access Principles
Upon selecting the 'Delete' button, the user will be presented with a couple of alert pop up messages. These are dependant on if the Access Principles are associated to a System Role or not
With system role associated
Or without a system role associated
In both cases, the user can select 'Delete' or 'No, Close' buttons
When bulk changes are made on work orders, users will now see a Before and After confirmation pop-up message that displays the changes that have taken effect.
We've updated our terminology from 'Shelving' to 'Basket' across all record types for better user understanding.
The character value within the Special Condition field on the Lease Clause has been increased to allowing users to enter more detail in this section
Users now can set a remedial type of work order to an 'INVESTIGATE' status so that these can be reviewed before a decision is made to carry out work before submitting to external systems
When selecting the Investigate option, users have the option to add a comment.
To progress the work order, select 'APPROVE AND SUBMIT' (the tick)
If there is an issue with submitting to external systems, the status will be updated accordingly, and a pop up shown to the user. Users will have to use the Approve/Submit option again to resend.
Note: Users can set up a widget to show all remedial Work Orders that are at Draft, Investigate and Submission Failed to monitor these submissions.