The BPM Action process is running and it creates the log file
here is the log entries for the time the BPM was fired but no email came tru
05/30/13 13:18:20 BPM Action Process - Processing
05/30/13 13:18:20 BPM Action Process - AblActionType #8 - Starting action
05/30/13 13:18:21 BPM Action Process - AblActionType #8 - Action completed
05/30/13 13:18:21 BPM Action Process - Completed
here is the log entries for the time the BPM was fired but no email came tru
05/30/13 13:18:20 BPM Action Process - Processing
05/30/13 13:18:20 BPM Action Process - AblActionType #8 - Starting action
05/30/13 13:18:21 BPM Action Process - AblActionType #8 - Action completed
05/30/13 13:18:21 BPM Action Process - Completed
On Wed, May 29, 2013 at 3:11 PM, Ephraim Feldman <effgroups@...>wrote:
> 9.05.701
> On 2013-05-29 2:40 PM, "Miguel Santillan" <msantillan@...> wrote:
>
>> **
>>
>>
>> Ephraim, what version you running?
>>
>> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
>> Of upworth
>> Sent: Wednesday, May 29, 2013 11:00 AM
>> To: vantage@yahoogroups.com
>> Subject: [Vantage] Re: Method directive, Post-processing, ABL sending
>> email is slow
>>
>> If the only change you are making is from synch to asynch, then it should
>> work. You may want to verify that the BPM Asynch process is actually
>> running. Open your System Monitor, select 'Actions-->Display All Tasks',
>> then look under the 'Scheduled Tasks' tab. You should see the task there,
>> probably called 'BPM Action Process'. Every time it runs, it reschedules
>> based on the time Delay you specified. If it's not there, then it's not
>> running continuously.
>>
>> Jonathan
>>
>> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
>> Ephraim Feldman <effgroups@...<mailto:effgroups@...>> wrote:
>> >
>> > Thanks Jonathan
>> >
>> > I have tested it and it works when run synchronously but when i set it
>> to
>> > async it doesn't even though the BPM action process is started.
>> >
>> > Could it be possible the reason because I have a pop up message as part
>> of
>> > the BPM?
>> >
>> > Ephraim
>> > On 2013-05-29 8:39 AM, "upworth" <Upworth@...<mailto:Upworth@...>>
>> wrote:
>> >
>> > > **
>> > >
>> > >
>> > > If you haven't dont so, I would suggest that you first run the ABL
>> > > synchronously to verify that it works. I have found troubleshooting
>> to be
>> > > more efficient this way. Once the email is sending like you want it,
>> then
>> > > change it to send asynchronously. (Forgive me, if you've already done
>> this.)
>> > >
>> > > My situation was that the emails worked synchronously but not
>> > > asynchronously. The fix (per a recommendation from Greg in this
>> forum) was
>> > > to run 'System Management-->Business Process Management-->General
>> > > Operations-->Action Process'. My admin took care of this for me and
>> set
>> > > this process to run on startup and "fire" every 5 mins. So, now,
>> every 5
>> > > mins the 'Action Process' runs and sends any emails that were queued
>> via my
>> > > ABL code.
>> > >
>> > > However, if you are having trouble sending email synchronously, let me
>> > > know and I'll post the ABL code I used.
>> > >
>> > > Jonathan
>> > > Business Process Manager
>> > >
>> > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
>> Ephraim Feldman <effgroups@> wrote:
>> > > >
>> > > > Can you please detail me how you did it
>> > > > I did the same but my emails doesn't get send.
>> > > > On 2013-05-28 9:06 AM, "upworth" <Upworth@> wrote:
>> > > >
>> > > > > **
>> > > > >
>> > > > >
>> > > > > PROBLEM SOLVED! My Admin started the 'BPM Action process' and the
>> > > emails
>> > > > > send asynch now. Thanks, Greg!
>> > > > >
>> > > > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
>> "upworth" <Upworth@> wrote:
>> > > > > >
>> > > > > > Thanks, Greg. I'll check with my Admin about that. It sounds
>> like
>> > > this
>> > > > > could be the solution I'm looking for. I'll let you know.
>> > > > > >
>> > > > > > Jonathan
>> > > > > >
>> > > > > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
>> Greg Payne <gpayne@> wrote:
>> > > > > > >
>> > > > > > > For async to work you need the BPM Action process running at
>> > > startup.
>> > > > > In 9.05 is it under Sys management > business Process Management
>> > GO.
>> > > > > > >
>> > > > > > > The time delay is the conversation with the email server, so
>> if you
>> > > > > control the email side you can work on the settings to go faster.
>> > > Another
>> > > > > option is to use IIS or another email server to offload the
>> message and
>> > > > > then relay for Epicor to the primary email server.
>> > > > > > >
>> > > > > > > Greg Payne
>> > > > > > >
>> > > > > > > From: vantage@yahoogroups.com<mailto:
>> vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:
>> vantage%40yahoogroups.com>] On
>> > > > > Behalf Of upworth
>> > > > > > > Sent: Friday, May 24, 2013 10:07 AM
>> > > > > > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
>> > > > > > > Subject: [Vantage] Method directive, Post-processing, ABL
>> sending
>> > > > > email is slow
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > I have created a post-processing method directive that is
>> working
>> > > as
>> > > > > intended except it takes too long. I will be grateful for any
>> help you
>> > > can
>> > > > > provide to speed this up. Below is the situation.
>> > > > > > >
>> > > > > > > The 'Action' is executing ABL code. I have narrowed the
>> performance
>> > > > > problem down to the "run SendEmail" line (see below). I know this
>> > > because I
>> > > > > substituted the "run SendEmail" command with a "display message
>> to the
>> > > > > screen" command and the performance is significantly better.
>> > > > > > >
>> > > > > > > speed test:
>> > > > > > > -No method directive : <2 secs
>> > > > > > > -With 'show message' line : 3-4 secs
>> > > > > > > -With 'send email' line : 11-12 secs
>> > > > > > > (I am not satisfied with costing the users almost 10 secs
>> every
>> > > time
>> > > > > this executes.)
>> > > > > > >
>> > > > > > > Here are the relevant lines in the ABL code:
>> > > > > > > [start]
>> > > > > > > define variable hEmailEx as handle no-undo.
>> > > > > > > run Bpm/BpmEmail.p persistent set hEmailEx.
>> > > > > > > ...
>> > > > > > > run SendEmail in hEmailEx (
>> > > > > > > false,
>> > > > > > > CUR-COMP,
>> > > > > > > vFrom,
>> > > > > > > vTo,
>> > > > > > > vCC,
>> > > > > > > vSubject,
>> > > > > > > vBody,
>> > > > > > > "":U
>> > > > > > > ).
>> > > > > > > [end]
>> > > > > > >
>> > > > > > > I found the code above - and all the other lines not
>> displayed - on
>> > > > > this message board. I am not doing anything out of the ordinary
>> with
>> > > this.
>> > > > > I am simply updating the vSubject and vBody variables and sending
>> an
>> > > email.
>> > > > > I am running this synchronously. It doesn't work at all if I try
>> to
>> > > run it
>> > > > > asynchronously. Using the Action 'send email based on designed
>> > > template'
>> > > > > will not work for me in this case.
>> > > > > > >
>> > > > > > > Is there another method for sending email using ABL code?
>> Should
>> > > this
>> > > > > work asynchronously and should I spend time troubleshooting why
>> it's
>> > > not
>> > > > > working?
>> > > > > > >
>> > > > > > > Thanks in advance for your ideas,
>> > > > > > >
>> > > > > > > Jonathan Tompkins
>> > > > > > > Business Process Manager
>> > > > > > > Alabama Specialty Products, Inc.
>> > > > > > > http://www.alspi.com
>> > > > > > >
>> > > > > > >
>> > > > > > > ________________________________
>> > > > > > > CONFIDENTIALITY NOTICE
>> > > > > > >
>> > > > > > > The information contained in this communication, including
>> > > > > attachments, is privileged and confidential. It is intended only
>> for
>> > > the
>> > > > > exclusive use of the addressee. If the reader of this message is
>> not
>> > > the
>> > > > > intended recipient, or the employee or agent responsible for
>> > > delivering it
>> > > > > to the intended recipient, you are hereby notified that any
>> > > dissemination,
>> > > > > distribution or copying of this communication is strictly
>> prohibited.
>> > > If
>> > > > > you have received this communication in error, please notify us at
>> > > > > 727-578-6280 and immediately delete the communication.
>> > > > > > >
>> > > > > > > "This (document/presentation) may contain technical data as
>> > > defined in
>> > > > > the International Traffic In Arms Regulations (ITAR) 22 CFR
>> 120.10.
>> > > Export
>> > > > > of this material is restricted by the Arms Export Control Act (22
>> > > U.S.C.
>> > > > > 2751 et seq.) and may not be exported to foreign persons without
>> prior
>> > > > > approval form the U.S. Department of State."
>> > > > > > >
>> > > > > > >
>> > > > > > > [Non-text portions of this message have been removed]
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > > [Non-text portions of this message have been removed]
>> > > >
>> > >
>> > >
>> > >
>> >
>> >
>> > [Non-text portions of this message have been removed]
>> >
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>
[Non-text portions of this message have been removed]