New Tekumo Features 08 11 23

Written by Ishraq Sadhan

Last published at: November 26th, 2024

Done

  • Modified the "Site Completed" tick to the following: 
    • Yellow circle = From ticket creation until the SC step has been marked or a child order has been completed/canceled 

      The original flow will remain the same. Example: If Child order #2 completed the site, then it will have a Green tick, while the parent order and child #1 will have orange ticks 
    • Green tick = If the current ticket (Child #2) has completed the site 
    • Orange tick = if a PARENT/CHILD (Parent and Child #1) have NOT completed the site  

    • Red cross = if the SC step on current order OR child order is marked “Incomplete
    • When one of the orders is copied manually (not as a child order), then the “Site Completed” field will reset as a yellow circle (in progress) 
      Original Order: 

      Copied Order: 
  • Revisit (RE) modifications
    • When a work order is rescheduled from the workflow, the following text box will pop up stating the following: "A new child order will be created."  
      The buttons on that popup window will be the following: "Copy Current Details" OR "Create New" 
       
    • When clicking on "Copy Current Details," it will use the same work order and reset the workflow. Example: 
      Before clicking on "Copy Current Details" 

      After clicking on "Copy Current Details" (the workflow has been reset) 
    • When clicking on "Create New," it will create a new/child work order and not reset the workflow 
    • When clicking on the RE step and selecting "Completed" then clicking on “X” in the popup window to close it, the RE step will change color to green 
    • The revisit counter for the “RE” step will only count revisits if the step status is changed from 'N/A' or 'Has Issue' to 'In Progress'/'Completed'; otherwise it will not automatically count revisits. Also, when clicking on "Copy Current Details," the RE counter will not automatically update, but that can be changed manually 
  • Added a new column on Bill Tracker for ”Order Delay Reasons”
  • Added "Arrival Due Date" to Job Tracker layou ts
  • The Revisit counter will count all revisits using child orders. The total revisits will be displayed on parent and child orders 
  • Removed the popup dialog when setting up/changing the SLA in order creation
    • There used to be a popup that appears after choosing an SLA, and the user had to choose either 'Yes'/'No' to changing due dates. That popup dialog has been removed and changes will simply take effect without further confirmation
  • Started automating SLA due dates: We have automated SLA Due Dates based on the Parts Confirm (PC) step in the workflow
    • When clicking on the "PC" step, there will be a date and time fields in the step dialog that is called "Estimated Delivery" where the dispatcher can fill that out 
    • When the PC step is not green (In Progress), the “Estimated Delivery” field will not be mandatory 

      When the PC step is green (Completed), the “Estimated Delivery” field will be mandatory 

      Based on that date, we will calculate a new due date for "Arrival Due Date" following the rules for that specific SLA code 



      Added a new column under "Customers" > Customer name > "SLA Code" tab. 
      The name of the column is "Auto Update SLA Due Date" and the input will be Yes/No 

      The auto calculation feature can be turned on or off for each SLA Code 
  • Billing: Exception vs Standard: When a technician has exceeded the allotted time to complete an assignment (“Tech Time on Task” or TTT), there will be a flag to mark it as either “Standard,” “Exception,” or “Check” 
  • The TTT time can be set under “Billing Rates,” which will automatically mark the flag under “Invoice” based on the logged timecard  

  • If it’s within the TTT plus 30 minutes = Standard (green flag)
  • If it’s greater than TTT plus 30 minutes, and there’s a delay reason = Exception (red flag) 
  • If it’s greater than TTT plus 30 minutes, and there’s NO delay reason = Check (orange flag), then the dispatcher will have to check the WO and classify it as either Standard or Exception. When clicking on “Exception,” the dispatcher will have to choose a delay reason 

    Exception Flag – Options:  
    TTT = None 

    TTT = Standard 

    TTT = Exception 

    Note: When selecting “Exception,” the dispatcher should assign a “Delay Reason” from the dropdown menu and assign delay time in minutes as shown below.  

    The list of Delay Reasons can be managed under Customers > “SLA Root Cause” 

    TTT = Check 
  • Parts/Shipments Tracking 
    • Can create/edit/delete shipment details in TEK (order create/edit page and from bottom-left side in Order details tab)  

    • When we send order to FN, it will also send shipment details
    • When we update shipments in TEK, it will be updated in FN. Updating shipment in FN doesn't trigger any specific webhook event by FN and it will not automatically update that one card on Tek. We can do force re-sync with FN to get the latest shipments added/modified in FN 

    • WM doesn't provide us a way to send shipment information to them, so that part is not done for now  
  • Customer Portal-Order “History“ tab will now be shown to customers
 
 

Bugs

  • Fixed emails that had no body when routing orders to techs 
  • Fixed an issue with order stage when it comes to unassigning techs on WM where the vendor details card was updating but the stage stayed 
    "Assigned"  
    After assigning on WM: 

    After unassigning on WM: 

  • Internal tasks on project templates are not appearing on work orders 
    (couldn’t reproduce this issue) 
  • Field nation messages received from the tech are not populating in TEK 
    (couldn’t reproduce this issue) 
  • Bulk Import Duplicating Orders (couldn’t reproduce this issue) 
  • Fixed an issue where Tekumo templates were reverting data when adding 
    FN/WM vendor 




     
 
 

 

Related Articles