**
Joe,
many thanks for your tips.
However, I still do not see how to built something to flip my Request_ID
I created 2 triggers to update my T and H tables on insert.
I noticed the API was somehow building the ID but nothing got inserted.
So I am wondering whether now I need to combine my triggers with the
arsignal or do I need something else?
I don't really see how I should use the arsignal. I am not refering to
the syntax.
Could you help more please?
Thank you
Serouche
PS: and I am on ARS 6.01
Joe D'Souza wrote:
**
Serouche,
Use it in an
Escalation in a Run Process if the change to the default prefix is at a
definite interval after changing the prefix using a Direct SQL
Syntax:
/install/path/of/your/application/bin/arsignal
-g <hostname>:<port number if applicable>
If the change in
prefix happens on an event rather than a interval, try creating a form
and set an entry to it on that event that triggers the above..
Cheers
Joe
** Thank you Joe,
This seems to be fine. Tickets in that schema are not created that
often.
But I don't really see how I could use the arsignal in my flow ...
could you tell me more please?
Thank you
serouche
Joe D'Souza wrote:
**
What exactly
do you want your Request Id to be?
The Run
Process you thought might help as Martin pointed out is to convert
internal meta data that represents run if qualification into what you
see in the Admin too and vice versa.
Dynamically
changing prefixes of Request ID's can be done provided you recache the
definition immediately after triggering the change in the default value
of the prefix. You can do this using the arsignal command with the -g
switch.
Having to
recache the definitions obviously mean you cannot do it too often (like
every 5 minutes) because it would hammer your performance..
Cheers
Joe
** I just tried your idea. I get the following:
Next available ID produces an Entry ID that overflows Entry ID field --
contact the Administrator (ARERR 305)
This is probably because we already have 8000 rows in the form.
The idea is to have every year <some string>YEAR0001, <some
string>YEAR0002,<some string>YEAR0003,<some
string>YEAR0004, ...
So right now what I do is every year after the first ticket is created
I export the row in a arx format. I manually make the change. Then
import with the import tool.
And this way the next id gets the right format. And we are safe for the
rest of the year.
But I'd like to have this self-service by Remedy itself.
I am starting to doubt in the power of this tool. So it has at least
one limitation.
Conny Martin wrote:
**
this special run process
wouldn't help you.
Documentation says: "Converts an
internal representation of a qualifier into a qualification string
using ID format. "
It deals with qualifiers not
request_id formats.
What about setting the
Default-Value of the request_id field to <some string>YEAR ?
You have to adjust this every year, but it's simple.
Kind Regards Conny
** Dear listers,
some of my users would like to have a fancy Request_ID in the following
format:
<some string>YEAR<Id number in 4 digits>
After many unsuccesfull attempts, I believe the Process Application-Format-Qual-ID could help
The problem is I don't get it work.
Could somebody give a hint on how to use this Process?
Or simpler, if anybody has a better idea, please share.
Thanks
Serouche
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___
|