Depending on if you do standard or ‘in transaction’ I can’t remember from the top of my head, but there is a template/wizard based email option that requires no coding..
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Bill Jackson
Sent: Wednesday, April 17, 2013 12:40 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: BPM Or Data Directive : send email
Thanks. I ask because all of my 'alert' experience has been with 'BAM's, but this particular Table is not available in a BAM.
We will be using a 'data directive', I'm not sure if the 'BpmEmail.p' can be used there, but I will find out.
________________________________
From: b_ordway <cooner_55421@...<mailto:cooner_55421%40yahoo.com>>
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Sent: Wednesday, April 17, 2013 1:30 PM
Subject: [Vantage] Re: BPM Or Data Directive : send email
I'm not sure I understand your question exactly but here are my two cents anyway...
Any new alerts I would set up as a BPM.
I liked BAM alerts but I've experienced unexplained, inconsistent behavior.
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Bill Jackson
Sent: Wednesday, April 17, 2013 12:40 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: BPM Or Data Directive : send email
Thanks. I ask because all of my 'alert' experience has been with 'BAM's, but this particular Table is not available in a BAM.
We will be using a 'data directive', I'm not sure if the 'BpmEmail.p' can be used there, but I will find out.
________________________________
From: b_ordway <cooner_55421@...<mailto:cooner_55421%40yahoo.com>>
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Sent: Wednesday, April 17, 2013 1:30 PM
Subject: [Vantage] Re: BPM Or Data Directive : send email
I'm not sure I understand your question exactly but here are my two cents anyway...
Any new alerts I would set up as a BPM.
I liked BAM alerts but I've experienced unexplained, inconsistent behavior.
--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Bill Jackson <fujijapman@...> wrote:
>
> We are looking to alert based on the 'PartAlloc' table, probably within a Data Directive. My question is, without having done much as of yet:
>
> Â Can we use the 'BAM' style ( Including {ud/GlbAlert.i &TableName = "PartAlloc"} ?
>
> Â Or should we pursue using the 'BpmEmail.p' code, similar to this posting.
>
> Bill J.
>
> Â
>
>
> ________________________________
> From: Steven Gotschall <sgotschall@...>
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Sent: Tuesday, August 17, 2010 3:09 PM
> Subject: Re: [Vantage] Re: BPM send email
>
>
>
> Â
> I found the same thing with the weird email TO address. It doesn't appear to
> affect delivery of the email. When we first started on 8.03 we didn't have this
> problem. Somewhere between updating Vantage and Exchange the problem emerged.Â
> I called it into Epicor, and they were clueless, basically they said they
> couldn't support Exchange. None of my other SMTP mailers (like my copiers) have
> this problem so it has to be something Vantage is doing. One of these days I'm
> going to trace the SMTP communication between Vantage and Exchange and see where
> the problem lies.
>
> ________________________________
> From: k99ja04 <jallmond@...>
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Sent: Tue, August 17, 2010 1:46:57 PM
> Subject: [Vantage] Re: BPM send email
>
> Â
> Trying to do it with a BPM. I later found BpmEmail.p. Below is the code I ended
> up with.
>
> It's weird the email address looks funky when it shows up in Outlook. I the main
> window, the To: field shows only "engineering@", and when I examine the MIME
> headers the To: fields shows (spaced for clarity)
>
> To: "engineering@" <wrightcoating.com engineering@...>
>
> They seem to flow so I'll take it for now. Any pointers? Something funny with
> the way you should quote or use any special characters with an email address?
> Thanks,
> Jared
>
> repeat:
> define variable vFrom as character no-undo initial '':U.
> define variable vTo as character no-undo initial '':U.
> define variable vCC as character no-undo initial '':U.
> define variable vSubject as character no-undo initial '':U.
> define variable vBody as character no-undo initial '':U.
> define variable hEmailEx as handle no-undo.
>
> run Bpm/BpmEmail.p persistent set hEmailEx.
> define variable from_cnt as integer no-undo.
> assign vFrom = 'Administrator@...'.
>
> define variable to_cnt as integer no-undo.
> assign vTo = 'engineering@...'.
>
> define variable cc_cnt as integer no-undo.
> assign vCC = ''.
>
> define variable subject_cnt as integer no-undo.
> assign vSubject = 'Bad Part Number'.
>
> define variable body_cnt as integer no-undo.
> assign vBody = "PartNum is not barcode friendly." + CHR(10) + "Quote:" +
> STRING(ttOrderDtl.QuoteNum) + " Line:" + STRING(ttOrderDtl.QuoteLine).
>
> run SendEmail in hEmailEx (
> false,
> CUR-COMP,
> vFrom,
> vTo,
> vCC,
> vSubject,
> vBody,
> "":U
> ).
> /* async as logical
> company as character
> emailFrom as character
> emailTo as character
> emailCC as character
> emailSubject as character
> emailText as character
> emailMimeHeader as character */
> IF valid-handle(hEmailEx) THEN delete procedure hEmailEx.
> leave.
> END.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "bw2868bond" <bwalker@> wrote:
> >
> > I am confused -
> > are you writing a BAM Alert .p procedure which uses ud/GlbAlert.i to send
> >emails or a BPM which uses Bpm/BpmEmail.p ?
>
> [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]