javascript function - “pega.u.d.asyncRequest(…)”
The crux of the issue is a javascript function - “pega.u.d.asyncRequest(…)” is expected to do asynchronous processing. But that doesn’t seem to be the case.
Since there is very limited documentation around this the question is “why” is this the case ? Is it a defect or as per design and rationale for this design.
The urgency is due to fact client is in middle of time- sensitive POC and are unable to use this OOTB function to accomplish async behavior.
Pegasystems Inc.
US
check if this helps: Re: httpRequestAsynch(strUrl) doesnt work in the Confirm dialog on firefox
Pegasystems Inc.
US
Hi Sushant,
What Kevin has provided you is a link that discusses using pega.util.Connect.asyncRequest. The pega.util.Connect JavaScript class is used for the core AJAX communication. The pega.u.d.asyncRequest is a helper function for the pega.u.d space used for OTB harness level actions like reloadSection and other processing. This ends up calling pega.util.Connect.asyncRequest.
What is making you think that pega.u.d.asyncRequest is not doing asynchronous processing? Do you have a custom AJAX call in your configuration that is using pega.u.d.asyncRequest or just normal OTB functionality? What version of PRPC are you using?
At a the lower level the pega.util.Connect.asyncRequest can't even be made to be synchronous, there is no parameters or options etc. The connection is always set to a asynchronous (true):
o.conn.open(method, url, true);
What you might be seeing is how the server is handling the requests but I need more information to discuss that further.
--Chris
Water NSW
AU
Hi Chris,
As asynchronous calls, we expect the activity to run in a background without the need for the invoked activity to wait. That is working fine.
However, we are unable to invoke any other server calls while the asynchrnous activity is running.
For example:
On a button click I am calling an activity. This activity calls an asynchronous activity. The Asynchronous activity has a wait method with a value of 30 seconds for testing purpose.
After the button is clicked, any other components that require a server side call (example: auto complete) is not working for 30 secs.