Push a flag to some "Workflow trigger" form.  You can then kick off the
big push server side with an escalation (or some other out of process
method).

 

After the AL push bring up a dialog that does an interval check to see
if the process has completed.  User workflow will stop until the dialog
is closed (by your interval check)

 

Fred

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of LJ Longwing
Sent: Thursday, March 05, 2009 3:12 PM
To: [email protected]
Subject: Re: Client Timeout

 

** 

The problem is that the processing of everything stops till that push is
complete.

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe DeSouza
Sent: Thursday, March 05, 2009 1:33 PM
To: [email protected]
Subject: Re: Client Timeout

** 

Have this AL that does the push in a AL guide. If you have some way to
ID the last record that has to be pushed, you could have a temp field to
identify if that record has been created via the push.

 

Loop the guide until that record has been created, and then move
forward..

 

Joe

 

________________________________

From: LJ Longwing <[email protected]>
To: [email protected]
Sent: Thursday, March 5, 2009 2:44:07 PM
Subject: Client Timeout

** 

Quick question (hopefully)

 

ARS 7.1 Server and Mid-Tier

 

I have a button press that causes a push to happen.  This push can
sometimes take in upwards of 5-8 min's to happen, later actions in the
AL fail to fire because of client timeout.  The timeout window seems to
be about 2 min's give or take a few secs....I'm trying to either extend
the timeout, or find a way to reattach the client to a server side
process once it finishes.  I'm considering moving the entire thing
server side and just sending the user an email when it's done...but
that's not desired.  Any suggestions?...oh...and I've troubleshot the
process...it's not taking too long in any 1 point...it's just an
extensive process...it's all internal to remedy...copying records from
location a to location b when needed...but there can sometimes be 10-20
thousand records that need to be copied...which just takes a bit of
time.





 


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

Reply via email to