Comments

15 comments

  • Natasha Hunter

    Hello, these functions aren't set up yet but should be later this week. We will send out an announcement when they're available. Thanks!

    0
    Comment actions Permalink
  • Ted Allen

    I haven't seen any announcement regarding this functionality.  When is it expected to be available for testing?

    0
    Comment actions Permalink
  • akohlsmi

    what is the expected time frame for the "update"and "correction" functionality to be added?   I may be missing something, but it appears that the only option for existing tickets is "relocate ticket"

    Additionally, when working on an existing ticket; when the "relocate" option is selected, I can change all of the following parameters: Province/Territory, Ticket Type, Type of work, Activity, excavation method, depth, start date, user reference, working of behalf of, utility/authority, onsite customer name, onsite contact number, and property location.  

    Is this behavior expected?  The ability to change the information listed above does not seem appropriate in a "relocate" request as some of these changes constitute an update or correction.

    0
    Comment actions Permalink
  • Natasha Hunter

    There's a bug with the ticket edit functions at the moment so the feature is only available to internal AOC agents. I don't yet have a date for when this will be fixed but I suspect it should be early next week.  Thanks for the catch on relocates. some of those fields should be editable but other, like the province, should not. I'll get that reported

    0
    Comment actions Permalink
  • akohlsmi

    Is there any news on the cancel, update and correction functionality?   We are two weeks out from the cutover date and we would like to have the opportunity to test things before the changeover.

    0
    Comment actions Permalink
  • Natasha Hunter

    Hello, yes an email was sent out some preliminary testers but we haven't rolled out to everyone as we came across some things that were causing issues. However- the issues seem to be affecting only members who use FTP so if you want to give it a shot please see the below.  Please email me directly at the below email and I can send over the spreadsheet. Thanks

     

    Hello, ticket edits (corrections/updates) are now ready to be tested. If you would like some edited tickets sent please go ahead and place some routine requests on your end and fill out the attached spreadsheet with the required information. In the columns “Correction” and “Update” please use an X to indicate whether you want the ticket corrected or updated. Please only pick 1 edit function per ticket.  Corrections are used to change information that is not pertinent to the job being done (i.e the onsite contact phone number) and updates are used to change information directly related to the job (i.e the address)

     

    Please note that all ticket edits will cancel the original request and generate a new ticket number so once we have completed the edits we will send back the spreadsheet with the new ticket numbers. Please send your response to thunter@albertaonecall.com

    0
    Comment actions Permalink
  • Regan Brown

    Hi Natasha,

    To clarify for myself, based on your above comments, any edit action on a ticket (whether it's a "correction" or an "update") will always cancel the original ticket and generate a new ticket number?  If this is correct, does it mean that in an FTP environment the BYDP software would send an .xml for the original ticket with a TicketStatus of "Cancelled", and would also send an .xml file for the newly generated ticket with a status of "Update" or "Correction" ( not a status of "Original" )?

    0
    Comment actions Permalink
  • Natasha Hunter

    Hi Regan, yes you are 100% correct

    0
    Comment actions Permalink
  • Kevin Grice

    Tasha, is there any update to the issues I sent about not always receiving cancel tickets for change tickets?  There are more details on the thread about the file naming issue.

    Kevin

    0
    Comment actions Permalink
  • Natasha Hunter

    Hi Kevin, yes the update is on the other thread. I copied it below. Can you let me know what you think?

    upon further testing we are seeing the FTP transmissions work as expected. The original ticket comes through to the ftp, if the correction comes through before the file is transferred off the ftp by the member's systems then the original is over written. If members can set their FTPs to retrieve the files every minute or so then it will prevent the original ticket from disappearing from the FTP. Some may have issues when the file hits their own systems as they may have parsing rules in place to remove "duplicate" files. If members can adjust their parsing rules to not remove duplicates then they should be able to see all versions of the tickets.  Can we move forward as is?

    Note that we WILL still be moving ahead with getting the file name to include the time stamp but we would like to hold off on this until after cutover as extensive testing will be needed. 

    0
    Comment actions Permalink
  • Kevin Grice

    Tasha, The file naming convention issue is separate from the cancel ticket questions.  I think there may have been hope that it did, however, the original tickets were not overwritten by the cancel tickets as we do not get cancel tickets in the scenarios I have described.  I think I had sent you the information where I identified when cancel tickets are not received in our system.  Let me know if you need more detail as this will need to be resolved as soon as possible for our UAT testing before go live.

    Kevin

    0
    Comment actions Permalink
  • Adam Spragins

    Hi Tasha, we had not received any cancellation tickets either for the Update test you for us did earlier this week. Cancellations did come through for our Corrected tickets however. We're only using the email tickets currently so not sure about the FTP files.

    Thanks,

    Adam

    0
    Comment actions Permalink
  • Patterson, Julie

    FYI there is a number of threads on this topic - we also have experienced  inconsistency if a 'cancel' notification is sent for an edit ticket (correction/update) using FTP. BC Hydro

    1
    Comment actions Permalink
  • Kevin Grice

    Tasha & Sher.

     

    We will need an update on this issue as soon as possible for our UAT testing.  It will be very hard to get user acceptance if these issues are not resolved in time to get complete testing.  As soon as this is resolved, we will need another round of test tickets sent to us.  Also, this issue is not related to the file naming issue.

     

    Once again the issues include:

    1. For an update ticket where the ticket type is changed from regular to emergency the cancel ticket is sent every time.  No other update tickets that change the ticket type did we get a cancel ticket.

     

    Ticket 20190200089 had update ticket 20190200120 but no cancel ticket was received.  This ticket changed from “Regular” to “Planning & Design”.

     

    Whereas ticket 20190200096 had update ticket 20190200124 and cancel ticket was received.  This ticket changed from “Regular” to “Emergency”.

     

    2. For correction tickets the only thing I noticed was that when the correction was to the field “working on behalf”, we did not get a cancel ticket.  There were no corrections for fields “user ref” or “authority” to check.  If the correction was for “onsite contact name” or “onsite contact phone” or “remarks”, we did receive a cancel ticket.

     

    Ticket 20190200082 had correction ticket 20190200116 but no cancel ticket was received.

     

    Just to be clear; an update ticket allows changing the ticket type, a correction ticket does not.  This is according to the edit matrix that Tasha sent me.  Also, I am assuming/hoping that the Pelican system validates any changes to dates where they have to be the correct allowable ranges on any change ticket.

    0
    Comment actions Permalink
  • akohlsmi

    we have found that cancelled ticket can be submitted for relocate, thus generating a new ticket.  In a few cases, the original ticket was cancelled as part of a ticket edit.   After the relocate request was submitted on the cancelled ticket, there are now two open tickets for the same job.   What is the rational for allowing edits and relocates on a cancelled ticket?

    0
    Comment actions Permalink

Please sign in to leave a comment.