Send emails after MRP is completed

We have a need to send an e-mail after a process is complete, like MRP.

Is this BPM e-mail setup applicable to that scenario also?

Is anyone doing this process completion e-mail send?

Thanks.

Brad Boes
Metalworks

--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> Adele continues:
>
> > Thanks for the suggestions. However, I am trying to come up with a solution that doesn't require us to edit the email addresses before deploying. We are currently using distribution lists, but that still doesn't solve our problem as we can't use the distribution list while testing since we don't want everyone on the list to get a bunch of test emails.
> >
>
> Oh, what I didn't mention is that we have a distribution list for each
> BPM. So my distribution list looks like EPICOR-BPM-<Directive>@...
>
> I then can put in individuals or another distribution list into that
> distribution list. This way I always know where the email comes from
> and I can test my putting the managers list in or out as I am testing.
>
> Have a great weekend,
>
> Mark W.
>
Hello,

We have created some BPMs that send out emails to a management group when certain conditions are met. As we are creating these BPMs, we need to be able to test them without sending a bunch of test emails to management. Our current process is to just have the email address of the person testing it enetered as a placeholder. The problem with this is that we need to make sure and remember to change the email address when we deploy the BPM.

We would like to come up with a solution that guarantees that emails don't get sent to the real recipients unless the email is issued from our Live database, but this solution also needs to allow us to test and deploy the BPMs without having to modify them.

Has anyone run into this problem and come up with a solution? I would like to not have to reinvent the wheel if possible :)

Thanks!
Adele
Adele wrote:
> We would like to come up with a solution that guarantees that emails don't get sent to the real recipients unless the email is issued from our Live database, but this solution also needs to allow us to test and deploy the BPMs without having to modify them.
>
> Has anyone run into this problem and come up with a solution? I would like to not have to reinvent the wheel if possible :)

Personally, we never put real names in our BPM mail-to fields. We use
(serverside) distribution lists. That way, as people come and go, all
you have to do is change the distribution list and not go back into
the code. Works for testing purposes too. You just add yourself as
your testing and when you're ready, add the managers.

Mark W.
Thanks for the suggestions. However, I am trying to come up with a solution that doesn't require us to edit the email addresses before deploying. We are currently using distribution lists, but that still doesn't solve our problem as we can't use the distribution list while testing since we don't want everyone on the list to get a bunch of test emails.

--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Maybe overkill for you but..
> I finally started keeping a test server around for stuff like this.
> I use the built in pop3 - p3server.msc
> Addresses like - user@...
> I use the outlook express email client.
> This way I never worry about the production Vantage/Exchange servers.
> I do have to edit email addresses before I deploy to the production server.
>
> --- In vantage@yahoogroups.com, "Adele" <arbjorklund@> wrote:
> >
> > Hello,
> >
> > We have created some BPMs that send out emails to a management group when certain conditions are met. As we are creating these BPMs, we need to be able to test them without sending a bunch of test emails to management. Our current process is to just have the email address of the person testing it enetered as a placeholder. The problem with this is that we need to make sure and remember to change the email address when we deploy the BPM.
> >
> > We would like to come up with a solution that guarantees that emails don't get sent to the real recipients unless the email is issued from our Live database, but this solution also needs to allow us to test and deploy the BPMs without having to modify them.
> >
> > Has anyone run into this problem and come up with a solution? I would like to not have to reinvent the wheel if possible :)
> >
> > Thanks!
> > Adele
> >
>
The only way I could see this working would be to setup a different email
system somewhere and have that DB or secondary server point to there for
SMTP and then not let the emails leave that server to get anywhere.

But that seems like a lot of work to bother with for this sort of thing.

What is the problem with changing the email prior to deployment that would
make you want to potentially put in more time to set something up than you
would save in the long run?

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Adele
Sent: Friday, March 11, 2011 2:40 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Testing BPMs that send emails

Thanks for the suggestions. However, I am trying to come up with a solution
that doesn't require us to edit the email addresses before deploying. We are
currently using distribution lists, but that still doesn't solve our problem
as we can't use the distribution list while testing since we don't want
everyone on the list to get a bunch of test emails.

--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Maybe overkill for you but..
> I finally started keeping a test server around for stuff like this.
> I use the built in pop3 - p3server.msc Addresses like - user@...
> I use the outlook express email client.
> This way I never worry about the production Vantage/Exchange servers.
> I do have to edit email addresses before I deploy to the production
server.
>
> --- In vantage@yahoogroups.com, "Adele" <arbjorklund@> wrote:
> >
> > Hello,
> >
> > We have created some BPMs that send out emails to a management group
when certain conditions are met. As we are creating these BPMs, we need to
be able to test them without sending a bunch of test emails to management.
Our current process is to just have the email address of the person testing
it enetered as a placeholder. The problem with this is that we need to make
sure and remember to change the email address when we deploy the BPM.
> >
> > We would like to come up with a solution that guarantees that emails
don't get sent to the real recipients unless the email is issued from our
Live database, but this solution also needs to allow us to test and deploy
the BPMs without having to modify them.
> >
> > Has anyone run into this problem and come up with a solution? I
> > would like to not have to reinvent the wheel if possible :)
> >
> > Thanks!
> > Adele
> >
>




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Adele continues:

> Thanks for the suggestions. However, I am trying to come up with a solution that doesn't require us to edit the email addresses before deploying. We are currently using distribution lists, but that still doesn't solve our problem as we can't use the distribution list while testing since we don't want everyone on the list to get a bunch of test emails.
>

Oh, what I didn't mention is that we have a distribution list for each
BPM. So my distribution list looks like EPICOR-BPM-<Directive>@...

I then can put in individuals or another distribution list into that
distribution list. This way I always know where the email comes from
and I can test my putting the managers list in or out as I am testing.

Have a great weekend,

Mark W.