DigTix v2.27 Release Notes (Contract Locator Registry, OQ Expiration, and More!)

Posted 8 months ago by John Gayness

J
John Gayness Admin

CONTRACT LOCATOR REGISTRY


The DigTix Positive Response Service ("PRS") has been updated to register and maintain the user data submitted to it by third party locators. This provides visibility into who performed locate requests which were dispatched to a third party and allows the ability to track and maintain information about those individuals.


To access the Contract Locator Registry, navigate to the DigTix Administration page and click on the "Contract Locator Registry" section. All third party users who have submitted a positive response to the DigTix PRS will be listed in this section.



Figure 1: Accessing the Contract Locator Registry



Each registered user may be edited to include contact information. It is also possible to view the locate requests and incidents that each user has been involved with, along with the current status of each item. This provides an entirely new dimension of insight into your organization's damage prevention efforts, regardless of who is performing those tasks.



Figure 2: Editing and Viewing a Contract Locator User



NOTE: The Contract Locator Registry is automatically populated if the DigTix PRS receives data in the "user" field of the positive response data packet. The specification of the "user" field is optional by default. For more information, please refer to the DigTix Positive Response Service API Endpoint Documentation. If the "user" field is omitted from the positive response data packet or left blank, the Contract Locator Registry will not be automatically populated. Your organization may need to coordinate with your third party locators to submit this information to the DigTix PRS accordingly.




OPERATOR QUALIFICATION EXPIRATION


The expiration of operator qualification ("OQ") may now be managed through DigTix! This includes 1) internal DigTix users; and 2) third party users such as contract locators through the registry described above.


OQ expiration dates for internal DigTix users may be managed through the existing "Users" section of the DigTix Administration page.



Figure 3: Setting an OQ Expiration Date for an Internal DigTix User



If a DigTix user attempts to login after their OQ expiration date, the login attempt will fail and an error message will be shown detailing the date their qualification expired and how to renew / update the expiration date.



Figure 4: Login Failure Due to OQ Expiration



OQ expiration dates for third party locators are managed via the new "Contract Locator Registry" section of the DigTix Administration page, which is detailed above. For each registered user, an OQ expiration date may be specified.



Figure 5: Setting an OQ Expiration Date for a Contract Locator User



If a registered contract locator user sends a positive response to DigTix after their OQ expiration date, the positive response system will fail with error code 8 (operator qualification has expired for the specified user) and the locate request will not be updated within DigTix. For more information, please refer to the DigTix Positive Response Service API Endpoint Documentation.



MISCELLANEOUS


- Added new fields to log information regarding the contact which was notified when rescheduling a locate request: Contact Name, Contact Phone, and Notified At.



Figure 6: New Reschedule Contact Fields



- Added ability to export time card entry data within the "Time Clock Entries" section of the Administration page.



Figure 7: Excel Export for Time Card Entries



- Added confirmation prompt prior to creating a follow up via the locate request window.



Figure 8: Follow Up Creation Confirmation



- The "Payroll" report may now be run for a specific user or manager.



- A new field "Category" has been added to "Close Codes". This new field can be used to categorize similar close codes together for reporting purposes.

- Miscellaneous minor improvements and bug fixes.

0 Votes


0 Comments

Login or Sign up to post a comment