Are you using ITSM? If so, the Request Id (field 1) is not the "Incident
Number".
If it's your own form, or you really want field 1, you can only copy it
after it has a value - which means after submit. So, you will have to set
it after the create succeeds which means there must be a time separation
between the submit and any workflow to set your field.
That can be done in many ways. Here are a few options:
Easiest option is this:
add a 179 field (or equivalent)
Add a filter to set 179 before submission
Do a push to a new form such as "gots to do work in my ticket form"
setting the 179 reference field (not 179)
Set up an escalation on the second form that issues an update to it
(Status != done or any extant records)
1) do a get fields to get the '1' from the ticket form
2) set the formatted value
3) do a push fields back to the ticket form using the 179 to select
it
4) delete the record or set the status = done
Make sure there's an index on 179 of the ticket (or equivalent) and (if
you decide to use a status) on the status in the second form.
This means that tickets can be in a state where the newly formatted field is
not ready (until the escalation is run). The escalation will run once for
each ticket so could be set to run each minute. It will not add too much to
the server load. In this case the "error" time could be from 0secs to
60secs
Other options include a Run Process (you'd have to write the process, but a
simple batch file or shell script should suffice) which will have '1'
available as it's fired after the submit (not a set fields run process).
A further option is a process (windows? Unix) where the run process simply
echos '1' to a file in a dir and a batch process wakes each second looking
for such files, processes them (ie updates that field) and then deletes the
file (in a loop). If the sleep is 1 s the amount of time the ticket could
be missing the info is from 0 to 1 sec.
Of course, with any process options you have to update an ARS record. You
could use Perl, Java, other things, or do the whole thing with Meta-Update
:)
It is not safe to check the next available id from arschema because of
threading and newer algorithms in the use of such.
Cheers
Ben Chernys
Senior Software Architect
Canada / Deutschland
Mobile: +49 171 380 2329 GMT + 1 + [ DST ]
Email: Ben.Chernys_AT_softwaretoolhouse.com
Web: www.softwaretoolhouse.com
Check out Software Tool House's free Diary Editor and out Freebies
Section for an ITSM 7.6.04 Forms and Fields spreadsheet.
Meta-Update, our premium ARS Data tool, lets you automate
your imports, migrations, in no time at all, without programming,
without staging forms, without merge workflow.
http://www.softwaretoolhouse.com/
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Mark Milke
Sent: April-20-12 11:48
To: [email protected]
Subject: Save the Request-ID to a field on Submit
Hello Listers,
someone is creating a ticket in my form. On submit I'd like to copy the
Request-ID into a field to in order to be able format it for another
purpose, but it's not working.
I've tried Set Fields: zzTmp_Request-ID = $Request-ID$ and zzTmp_Request-ID
= $LASTID$.
Any ideas how I can achieve this without into the same form on submit or
overwritting the filter phases of the filter creating the ticket?
Thanks
Mark
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12
www.wwrug12.com ARSList: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
