Done
- TekCloud
- Added "Labor Total" column
- Added "Labor Total" column
- Customer_users won’t be able to edit Custom Fields without admin verification
- If the customer doesn't have permission to edit any of the listed Custom Fields on an order, they will see the following message letting them know why they can’t edit those custom fields
- If the customer doesn't have permission to edit any of the listed Custom Fields on an order, they will see the following message letting them know why they can’t edit those custom fields
- Shipment Details card will now have an ETA field for each shipment
- Order Pay Rate(s) Modification - Remove ”Should take approximately …”
BEFORE AFTER
- Custom Fields – Added a “UI Visibility” column. This is designed to completely deactivate the field. In the next sprint, this feature will only affect the UI without completely deactivating the field. That means it will not appear on the Order Details, but the custom field can be still used under Tech Tasks
- Email Streamlining
We get to reduce email traffic related to Tekumo tickets as that is taking a lot of time from dispatchers to go through them. The purpose of the following changes is to mostly reduce the number of emails our team gets. One way is to communicate with customers, techs, and internal tram through Tekumo Messages rather than email. Those messages will be categorized as the following:- Messages will have a mandatory message category,
i.e. Escalation, Request, Notification, Chat.
If the message is API-generated, then the category type will be "None"
Note: “None” will be changed to “API” in the future
- Those categories are under the following:
"Admin" > "Data Elements" > “Message Categories”
- Any email notification that we receive from these messages will have a standard subject format: Ticket # - Category – Text
- Messages will have a mandatory message category,
- Automated the "Order Location" Card – In preparation for automating 80-90% of Tekumo's resource coordinating, this part of the ticket creating process will be auto-generated
- Moved “Location Name” to be on top of the “Order Location” card and made it a mandatory field
- The “Location Code” will be auto-generated and greyed out as only an admin can modify it at the Site Profile level
- Automated loading 2 Custom Fields into Order Details:
Issue: When Pomeroy creates a new ticket, they are only able to enter details in custom fields (SIMS Call Number/Client WO Number, and Client Ticket Number). When the operations team goes to complete ticket creation, they had to copy the data from these 2 custom fields to the Order Details fields ("Customer Work Order Number" and "Customer Ref Number").
Solution:- Make sure to map the “Customer Work order ID,” “PO number,” and “Ref
Number” with the Custom Field
- When creating an order from the customer portal, if the Custom Field maps with the WO ID, PO, and Ref number, the custom field value will automatically be set in the WO ID, PO, and Ref number fields
- Make sure to map the “Customer Work order ID,” “PO number,” and “Ref
- Customers now have access to VIEW their permissions page without giving them the ability to edit any of the information
- Disabled full page edit. Instead, allow edits directly into each card
(currently, not all cards have that feature) - The tabs at the top will be fixed on top even when scrolling down
- Hid the Customer Contact ID column as it's not necessary to show in Ul
- Allowed admins/RCs to edit customer contacts when clicking on each contact
- Moved "Task" to "Technician" card. Placed the "Task" heading as a second heading on the "Technician" card
- Had all tech tasks appear with checkboxes next to them so that they can be easily viewed and selected
- Combined the "Single Sign On" and "Netsuite" cards into one. Placed the "Netsuite" heading as a second heading on the "Single Sign On" card
- Disabled full page edit. Instead, allow edits directly into each card
- Re-arranged and improved UI for “Order Details” tab to the following:
Order Details- Current Summary
- WO Description - can expand (default just heading)
- Customer description (further expansion)
- Shipments
Note: Removed "Order Pay Rate(s)" card from Order Details tab
Internal Details- Tasks
- Notes
- Checkout Process
Ticket Details - Custom Fields
- Closing Order Notes – automatically populated from Vendor Closing Notes
- Tech Feedback
- Changes to Schedule and SLA cards
- Schedule (Our card)
- TimeZone
- Arrival Type – Window/Exact
- Dates – Start/End
Customer Dates (Sub Card) – All Edit - Schedule Type
- Start Date/End Date
- SLA (Our Card)
- SLA Code
- Acknowledge/Response/Restore (Default Response) – checkbox can choose all 3
- Receive Date (admin override only)
Customers Sub Card: (All Edit) - Customer SLA Due Date
- Customer SLA Type
- Allowed customers to search for tickets using customer WO number. When the customer searches by the SIMS work order details or by the store information, it will pull up all the tickets we have for that specific WO or site
Bugs
- Fixed a TekCloud issue where Techs who have sent applications through WM were showing as though they’re coming from FN, and techs weren’t getting assigned
- Adding custom fields to orders are now saving properly
- Tech Tasks are no longer duplicating. The issue was generating when customer_user was creating an order using a template which already has some technician tasks in it
- TekCloud
- "Reply Date" is now showing the correct date in the work order’s timezone
- Fixed issues with counter offers where we could not reject counter offers
- Fixed an issue when the counter offer has a new date AND time, then new date populates on the table under TekCloud, but not the new time
- When the “Vendor Details” card was showing blank, it was due to the template being used not having a set vendor, so the dialog didn’t have any pre-filled values
- Fixed an issue when Field Nation Counters were not populating
- Fixed an issue with Routes vs Counters where if we sent an offer to a technician, and they sent a counter offer back to us, they appeared twice on TekCloud: once under “Routes,” and another under “Counters”. The correction will be the following:
- "Reply Date" is now showing the correct date in the work order’s timezone
- If the technician was already routed and the technician creates a counteroffer, then the route will be removed
- If the technician has already sent us a counter-offer, then we will not be able to route an order to them
- Fixed an issue where the customer portal’s output dates don't match input dates. The issue was that when testing the SLA card on the Customer Portal, the customer inputted the following dates (see below), but after saving, the output view was subtracting 5 hours from "Customer Due Date" and "Customer Arrival Date"
- Our development team has investigated the “Failed to load invoice” error that was persistent on WO# 35190 and they found the following:
- Order 35190 is a non-billable child order of 35061
- Order 35061 is a non-billable child order of 34496
- Order 34496 is a parent order that can load the invoice without any error
For non-billable child orders, our back-end sends an error message indicating that this order cannot be invoiced and user needs to check its parent order. We are doing the following modifications: - Instead of showing "Failed to load invoice", we can show a proper error message
- As we know that non-billable child orders don’t have an invoice, we can omit that API call for non-billable child orders
- We also need to prevent child orders from being a parent of another order
