DigTix v2.21.2 Release Notes (Contract Copying, Infrastructure Rendering, Incidents from Locate Requests, and More!)

Posted 10 months ago by John Gayness

J
John Gayness Admin

CONTRACT COPYING


DigTix now allows the creation of a new member code from an existing member code. To do so, head to the "CDCs" section of the Administration page, click on the member code you want to duplicate, then click the new "Create From Existing" button at the top of the list.



Figure 1: New "Create From Existing" CDC Button



DigTix will prompt for what the new member code is. Type the new CDC and hit the "Submit" button. DigTix will copy all of the close codes, billables, and positive response integrations from the existing CDC to the new one!



Figure 2: Creating a New CDC from an Existing CDC




INFRASTRUCTURE RENDERING



Users may now configure the order in which infrastructure layers are rendered. This is useful for ensuring DigTix users have a complete picture of the area they're locating without having to worry about assets that exist above or below other assets. Within the "Infrastructures" section of the Administration page, a new "Render Order" field specifies what layers are drawn on the map before others.


Layers with a smaller render order (e.g. 1) are rendered before layers with larger render orders (e.g. 5). Layers with higher render orders appear on top of layers witch lower render orders.




Figure 3: Infrastructure Layer "Render Order"



Users can more easily manage large numbers of infrastructure layers via two new buttons added to the tickets page:


  1. At the top of the "Map" tab, a new "Select / Deselect All" button will check / uncheck all infrastructures in the list. This is useful when users want to see everything, or perhaps only a few layers at one time.
  2. A new button has been added to the map toolbar which toggles the display of the selected infrastructures on the map. This is useful when the user wants to temporarily remove all layers from the map to see other geospatial information (tickets, fleet tracking, map notes, base imagery, etc) more clearly.




Figure 4: Infrastructure Layer Select / Deselect All and Toggle




INCIDENTS FROM LOCATE REQUESTS



An incident may now be created directly from a locate request. A new button "Create Incident" can be found on the ticket window's "Actions" tab. Clicking this button will create an incident and migrate all pertinent information from the ticket to the incident (location, excavator information, request information, etc). This saves users the time and hassle of manually filling out incident information.



Figure 5: Creating an Incident from a Locate Request




WEEKLY DASHBOARD FILTERS



The weekly dashboard may now be filtered based on call center / project or customer! A new drop down provides the ability to see how different business segments are performing on a daily basis.



Figure 6: Filtering Weekly Dashboard Data


MISCELLANEOUS


  • This release includes many internal, behind-the-scenes improvements which will support many major features in upcoming releases.
  • Performance improvements to the loading and management of Quick Filters.
  • Improvements to the file upload and attachment process.
  • Report inputs specifying a user now support free-form typing to filter the user list.
  • Incidents may now be assigned upon creation.
  • Fixed issue where circular references may lead to multiple open windows with the same information.
  • (Optional) Close codes may now be reset when an update to an existing ticket is received.
  • Minor bug fixes and improvements.

0 Votes


0 Comments

Login or Sign up to post a comment