Emailing work items - time delays with batch processing

[Workflow99@aol.com]

Margaret,
 
If you are on WAS 6.10 or higher, you can develop a method to send a mail  
using BCS intreface without having to depend on RSCONN... Use the URL below  to 
see Thomas Jung's SDN weblog on using BCS.
 
_https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/789_ 
(https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/789) 
 
 
Regards,
Ramki Maley
Workflow Developer,  USCBP.
248-613-1287 (C)

 
In a message dated 9/23/2005 11:47:30 AM Eastern Standard Time,  
wug.replies at workflowconnections.com writes:

Hi  Margaret,
I've always treated RSWUWFML as a 'reminder' job. Why not send an  email
from your WF instead?
You will still have delays between  SapConnect and Notes, but that's under
the control of your Basis and Notes  people. You could of course also have
a sendmail step followed by one that  runs the RSCONN... job for the
fastest turnaround :-)

By the way,  RSWUWFML is also a fairly intensive job since it trawls
through a lot of  agent evaluations and stuff and shouldn't be run quite
that  often.

Cheers
Mike

Hilsbos, Margaret A wrote:
> Hello  all,
>
> This is a kind of general question where I am fishing for  the best
> approach/answer to an anticipated problem.
>
>  Currently we are implementing a workflow on a WAS 620 CRM box that is
>  replacing a homegrown, Lotus-Notes based application.  I have set up  the
> RSWUWFML2 job to email work items to the users, but I see this as  a
> looming headache because:
>
> - the LN app sent the  corresponding emails immediately (at least that is
> the perception),  with no significant delay
> - even if I set up the RSWUWFML2 and  SAPConnect jobs each to run every
> minute (which I think Basis doesn't  want to do anyway), there is still
> potentially up to a 2 minute delay  from when a step is completed and the
> next item is sent from SAP to an  Outlook recipient.
> - In testing, with the jobs set to 1-minute  intervals, we were seeing even
> greater delays than expected (like 15  minutes or more).  I have asked
> Basis to look at it but I'm  guessing the jobs are going into a queue that
> is holding them up,  and  I suspect we won't be able to fix it easily, if
> that's the  case.
>
> Here's my questions:
> - is there a better way to  do this in our current environment? Are we just
> doing it wrong  altogether?
> - Would integrating the solution in the Portal  (EP6-point-whatever) buy us
> anything?
> - has SAP introduced, or  is it planning to introduce, newer components
> that make the email  integration more seamless? If so what are they, and
> how can I find out  more about implementing them?
>
> A 2-minute delay in the  processing may seem like nothing to us, but I'm
> expecting it to be a  user-acceptance hurdle for this process. And I'm a
> bit cranky about  the 2 minute (plus!) thing myself, considering this is an
> internal  process with all the users on the same floor of the same
>  building.  Sneaker-net would almost be faster.
>
> Your  thoughts, ideas?
>
> Thanks,
>
> Margaret  Hilsbos
> Day & Zimmermann
>
>
>  _______________________________________________
> SAP-WUG mailing  list
> SAP-WUG at mit.edu
>  http://mailman.mit.edu/mailman/listinfo/sap-wug
>


Mike  Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44  (0)7786 910 855
_______________________________________________
SAP-WUG  mailing  list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050923/541ff005/attachment.htm