Paul,

What you are looking for cannot be done using any Out-Of-The-Box features of
Remedy.

Having said that, it is however possible to implement what you want by
creating a custom field to store this ID that you wish to generate. The
easiest way to achieve this would be to create a counter form that would
keep the counter (in your example 123), that would reset to 0 at midnight
every night using an escalation.

On creation of a ticket, you perform a push field action, preferably as the
last execution order of a filter which has a phase override, to this form
containing the counter, to set the counter to existing counter value + 1 and
retrieve this set value to your current transaction. Retrieve this value set
on that form, and set it to the current $YEAR$ + $MONTH$ + $DAY$ + $counter$
on a character field that would be used as that custom ID.

Do not forget to index this ID as I'm pretty sure you will be using it to
retrieve either through user searches on that table or perhaps through
workflow.

Cheers

Joe

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Paul Blasquez
Sent: Tuesday, September 18, 2007 7:45 PM
To: [email protected]
Subject: Custom Request ID/GUID


Hello,

Are any of you using the ticket identifier format of
<year><month><day>-<unique number>?  For example, issue 123 for today would
be ticket number 20070918-123.  I have been a user on a system that used
this format, and I appreciate its intuitiveness.

What is required to implement this? Is there simply a format/pattern applied
to the request id field?  Or is it a bit more involved?  I can't seem to
find anything about it in the Basic/Advanced guides nor in the ARS archives.

_______________________
Paul Blasquez
Remedy Developer/Senior Network Engineer
Equinix, Inc.
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.487 / Virus Database: 269.13.22/1015 - Release Date: 9/18/2007
11:53 AM

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to