e no Filters
>> with names ending in "`!".
>>
>> Arthur
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
>
>
--
Use Merge with the NoWorkflow option (a bit pattern available since ARS 6+)
instead of Modify AND set a real database field so that an escalation fires the
real Modify workflow. Obviously, build that escalation.
You are getting around the basic design of ARS in this way and this must be
done w
Arthur,
"each thread would be relieved as soon as the modify of that one
record is completed in the View form"
You are completely correct about that. However, where you think
"completed" should be reached is actually not where it actually ends.
The transaction (or API call if you prefer) is not
;> that Modify to complete, before going on to the next Modify request to
>>> be
>>> sent to the server.
>>>
>>> Thanks
>>
>> ___
>> UNSUBSCRIBE or access ARSlist Archives
t; without every Modify request having to wait for all the Filters, relevant
>> to
>> that Modify to complete, before going on to the next Modify request to be
>> sent to the server.
>>
>> Thanks
>
> _________
Dear Arthurj (software_architect),
To my knowledge there is no way to alter the atomic nature of the ARS
API. (vai the Java API or the C API.) The "trick" is to realize that
the ARS server is a multi-threaded server. You can control how your
client talks to the ARS server and how many threads are
going on to the next Modify request to be
sent to the server.
Thanks
--
View this message in context:
http://www.nabble.com/Modify-a-View-Form-entry-using-Java-API-tf4308465.html#a12265229
Sent from the ARS (Action Request System) mailing list archive at Nabbl
7 matches
Mail list logo
