Welcome to Good Training Sign in | Become a member - FREE!
 

Ticket Number Format

Last post 11-26-2008, 5:08 PM by Mike Spragg. 3 replies.
Sort Posts:
  •  11-26-2008, 1:10 PM 1582

    Ticket Number Format

    I apologize if I am asking a question that has been posted somewhere else. I’ve searched through the help files and several different SLX forums but have not been able to find an answer to the following.

     

    What is the purpose of the Ticket number format?

     

    XXX-XX-XXXXXX

    (3-2-6)

     

    I have found documentation in the SLX help that states in regards to the Ticket ID, “You cannot change the ID.”

     

    Why the hyphenated format and why the need for so many digits? Is there some dependence of the database on this number format? My understanding is that the numbers will just work in sequence. For example, when Ticket one million is reached the ticket number 001-01-000000 will be assigned.

     

    The Ticket number’s format doesn’t represent a large issue for us, but the management and users have both inquired why it is necessary to have so many characters which add a minor visual inconvenience. Fewer numbers would be easier to recognize.

     

    Thanks in advance for the expertise.

  •  11-26-2008, 4:06 PM 1583 in reply to 1582

    Re: Ticket Number Format

    Essentially, it's to separate remote offices and remote users (as you can't have a UniqueID that's sequential due to sync).

    Site Identifier - The first three digits of the prefix identifies the site. The host database's site

    identifier is 001. Remote Office databases are assigned site identifiers in the 100-199 series.

    Remote user databases are assigned site identifiers in the 200 and up series. (Note that the site

    identifiers are not necessarily assigned in sequence.)

    Key Base - The last two digits of the prefix represent the revision number of the database. If

    you create a new database for a Remote Office or user, this number is incremented.

    When a user creates a defect or return, the system assigns the

    the correct prefix followed by a six-digit,

    auto-generated suffix (for example, 001-01-000015).

  •  11-26-2008, 4:20 PM 1584 in reply to 1583

    Re: Ticket Number Format

    Thank you, Mike. I appreciate the info.

    By the way, some months back we discussed ways to associate multiple Tickets together. Recently I received information from Brianna from GoodTraining regarding a "plug-in" which seem like it does exactly what we were talking about. Its called Workslip and allows users to manage handled of multiple Tickets which are related to the customer's single request. I was wondering if you have looked into this and if so, any thoughts? (See link below) BTW: We're currently getting ready to install SP2 for 7.0

    http://customerfx.com/pages/cfxproducts/2008/08/05/power2workslips-for-sage-saleslogix.aspx

    Thanks again for your help,

     

    David

     

  •  11-26-2008, 5:08 PM 1585 in reply to 1584

    Re: Ticket Number Format

    Hi David

    Personally, no - I saw an email about today strangely enough !

    What I can say is, that it comes from the stable of CustomerFX so I would imagine it will be excellent !! Especially if Ryan has anything to do with it !

    Regards
    Mike

View as RSS news feed in XML