I had thought of that.. but does that really work? If I create a display only integer field initiate it at 1 and do a field + 1 until its value is maybe 1000???
If so how exactly would I calculate the time it may take for that counter to reach 1000? I was also thinking of doing a fake count on the largest table on the ARS and returning that to a integer field, hoping that operation would take a brief second or so.. This would sort of having a varying result, as the query would be saved in the recent query buffer in the DB, and subsequent users of that query would experience shorter time to execute it.. Another thought is maybe setting a field with timestamp and adding that value by a constant (say 5) to make it sleep for that much time if a filter loop idea like yours is implemented where I exit the loop as soon as the $TIMESTAMP$ reaches that calculated value.. Joe From: Shellman, David Sent: Wednesday, May 30, 2012 4:10 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: PAUSE or SLEEP a filters in between actions... ** Joe, I've used a simple counter in a filter guide to cause a pause in a filter operation. Basically the old programming loop counter to slow down a process. The filter guide loops until the counter reaches a set value. Dave On May 30, 2012, at 4:05 PM, "Joe Martin D'Souza" <[email protected]> wrote: ** We are updating an identity management system (OIM) using its SPML based WSDL. During the operations to suspend or resume a user the output status of this operation seems to always be ‘pending’ – which in reality is really an intermediate status before ‘success’ or ‘failure’. The lifespan of this intermediate status is just a brief fraction of a second before the update either succeeds or fails.. From the service consumption point of view, this intermediate status of ‘pending’ is not quite meaningful other than the the fact that the WSDL call was successful. Given a choice I would have rather had the option to wait for those few micro seconds, at what point the status of either ‘success’.. They have a operation in the same web service to query the status. Following the update WSDL with a query WSDL is what I thought would be my answer to getting the new status (although I do not like the option of have another WSDL call when there could have been one)... This query however returns the status of the the user pre update. Filters as we know have no ‘SLEEP’ type action, else I could have used that to pause the filter operations in between the update and query operation. Ideally it would have been perfect if there was an ability to introduce a pause between the two WSDL calls. Is there any ‘creative’ way of inserting a pause in a filter operation that maybe I do not know of? Joe _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
