Topic Options
Rate This Topic
#140877 - 12/16/08 12:19 PM UUID in Incident Management?
remedybuff Offline
Stealth Member

Registered: 05/05/06
Posts: 76
Loc: New Jersey, USA
Hi All,

I remember that with 6.3 there was a field called UUID which uniquely identified records across various applications.

I haven't found that in version 7 Incident Management OOB form. Has the field name changed?

Also, does anyone have any idea as to how that UUID is generated? Is there a limitation on how many records it can handle?

Thanks.

Top
#140878 - 12/16/08 04:38 PM Re: UUID in Incident Management? [Re: remedybuff]
Matt Reinfeldt Offline
Old Hand
***

Registered: 06/12/01
Posts: 1419
Loc: Madison, WI
Are you talking about 'instanceId' (field id 179)? That is pretty much the key in ITSM 7. Field ID 179 is special in that it auto-populates a GUID in that field on submit, so each record has its own GUID to use as a reference. Now, when talking across applications (SLM, CHG, etc) you'll likely see fields like objectID, SourceInstanceID, etc. that refer back to the instanceId (field 179) from the other form(s).

Confusing? smile They tried to make it easy to follow... you just gotta track it all back to the source form to know where to look for what.

HTH,
_________________________
Matt Reinfeldt
I belong to the following Professional Networks:
http://www.naymz.com/search/matt/reinfeldt/1524717
http://www.linkedin.com/in/mreinfeldt

Top
#140881 - 12/17/08 12:10 PM Re: UUID in Incident Management? [Re: Matt Reinfeldt]
remedybuff Offline
Stealth Member

Registered: 05/05/06
Posts: 76
Loc: New Jersey, USA
Thanks Matt!

Any idea how it is generated? Meaning, how that 30 char string is built and what values it can take.

I am trying to find out what is the limitation of the GUID, like how much time before it overlaps?

Thanks,
Anuj.

Top
#140882 - 12/17/08 12:16 PM Re: UUID in Incident Management? [Re: remedybuff]
Matt Reinfeldt Offline
Old Hand
***

Registered: 06/12/01
Posts: 1419
Loc: Madison, WI
Anuj,

Here's the answer straight from the KB. smile
Quote:

Question
What is a GUID (Global Unique Identifier), and why would I need to use one? Why is this a better unique identifier than the entry-Id?

Answer
A GUID, or Global Unique Identifier is a 30-character unique string. To create one, reference KB entry 11650. This KB discusses the why, not the how.

A unique string is indispensable when creating parent-child relationships, or any other 1-to-many or many-to-many relationship. Before the advent of GUID's such relationships were bound together using an entry-Id. This was sufficient, but had the following two weak points:

1) An entry-Id does not exist at create time. When a user is submitting an entry, they may want to define the child entries before hitting submit, but the entry-Id does not exist until after the user has hit submit.

2) An entry-Id is only unique on a per-form and per-server basis. The entry Id may be duplicated in other forms, or the same form on another server. Also, in the event of a hardware failure where lost data is eventually restored from backup, duplicate entry-Id's may have occurred during the outage that conflict with the restored data.

A GUID is unique globally. The data can move to other forms on other servers at other companies in other parts of the world, and the mappings that are defined by the GUID's will remain true.


Enjoy,
_________________________
Matt Reinfeldt
I belong to the following Professional Networks:
http://www.naymz.com/search/matt/reinfeldt/1524717
http://www.linkedin.com/in/mreinfeldt

Top
#140883 - 12/17/08 12:18 PM Re: UUID in Incident Management? [Re: Matt Reinfeldt]
Matt Reinfeldt Offline
Old Hand
***

Registered: 06/12/01
Posts: 1419
Loc: Madison, WI
More detailed information for you:
Quote:

The length of the GUID as generated by the Application-Generate-GUID command is 30 characters and will be a combination of upper and lower case letters as well as numbers.

The 30-character GUID is composed of:

- 2 char prefix, padded with underscore if necessary
(default prefix is "ID" if no prefix is supplied)
- 12 char server MAC address, truncated or padded with zeros on the left as necessary.
- 8 char datetime (seconds, hex, since start of 1 Jan 1970)
- 8 char clock ticks (hex, since start of server, with rollover)
returns 30 char GUID + 1 char string termination.
or NULL on error;

Note: This is subject to change between releases.
_________________________
Matt Reinfeldt
I belong to the following Professional Networks:
http://www.naymz.com/search/matt/reinfeldt/1524717
http://www.linkedin.com/in/mreinfeldt

Top