Greetings!
I have a form in ARS 9.1.02 where I’ve created a button to commit changes when
either creating or modifying a request. I use the $OPERATION$ keyword to
determine what mode I’m in. I change the label on the button to read “Submit
Ticket” for new requests, and to “Update Ticket” when
In general, when building a client/server application (Remedy server is the
client, DB is the server in this example), it's best to limit the
communication between the client and the server to the absolute minimum
necessary to get the work done. In this case, forcing every submit to a
table to do
Where is there a difference in the time to create the next ID
UPDATE ARSCHEMA SET NEXTID = NEXTID + 1 WHERE SCHEMAID = x
UPDATE ARSCHEMA SET NEXTID = NEXTID + 100 WHERE SCHEMAID = x
It is not like the database goes 1+1+1+1+1+1… with a save to the file each
time.
My db bottleneck was pure
Thomas,
Have you looked into the Application-Release-Pending command? This command
might be able to be used to submit the record, then get the request id,
then send out a notificationthe down side to it is that you wouldn't be
able to do a rollback after the Release-Pending.
On Thu, Oct 12, 2
Hi,
Any other tool, such as a plugin sver, would actually go through the AR Server
eventually before the Request ID is used and a record is created.
There are two settings which you can play around with, and these would revert
back to the old behaviour of locking the table and increasing one st
Randeep, yes, all requests flow THROUGH AR Server, but not all are
generated directly BY it. Outside products would likely use a plug-in
server thread, which creates the competition with direct AR Server calls
for the Next ID calls.
Thomas, Notify already runs in Phase 3 - there is no "later phas
6 matches
Mail list logo
