If you have that as a pre-processing, it can fire multiple times if the user
is not entering all the required data. For example:
1. User enters a customer, but does not enter two fields that are
required, and clicks save.
2. Preprocessing BPM kicks in, sends out the email.
3. Epicor regular processing kicks in, returns error to user, and the
customer is not saved.
4. User fixes one of the required fields, presses save.
5. Preprocessing BPM kicks in, sends out the email - SECOND email.
6. Epicor regular processing kicks in, returns error to user, and the
customer is not saved.
7. User fixes the second required fields, presses save.
8. Preprocessing BPM kicks in, sends out the email - SECOND email.
9. Epicor regular processing occurs, record is saved.
Note three emails would have gone out in this scenario. If instead, the
pre-processing directive would have simply enabled a post-processing
directive which sends the email, the post would have run only after the save
worked successfully.
Hope that helps,
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
carl.heeder
Sent: Wednesday, April 11, 2012 2:15 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Email troubles
I have a BPM that fires on a new customer (.rowmod="A")
The trouble is that it sometimes fires multiple times I.e., several emails
for one new customer
Support has said that this needs to be a post not pre BPM. This doesn't
sound logical but maybe.
Any advice?
[Non-text portions of this message have been removed]
is not entering all the required data. For example:
1. User enters a customer, but does not enter two fields that are
required, and clicks save.
2. Preprocessing BPM kicks in, sends out the email.
3. Epicor regular processing kicks in, returns error to user, and the
customer is not saved.
4. User fixes one of the required fields, presses save.
5. Preprocessing BPM kicks in, sends out the email - SECOND email.
6. Epicor regular processing kicks in, returns error to user, and the
customer is not saved.
7. User fixes the second required fields, presses save.
8. Preprocessing BPM kicks in, sends out the email - SECOND email.
9. Epicor regular processing occurs, record is saved.
Note three emails would have gone out in this scenario. If instead, the
pre-processing directive would have simply enabled a post-processing
directive which sends the email, the post would have run only after the save
worked successfully.
Hope that helps,
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
carl.heeder
Sent: Wednesday, April 11, 2012 2:15 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Email troubles
I have a BPM that fires on a new customer (.rowmod="A")
The trouble is that it sometimes fires multiple times I.e., several emails
for one new customer
Support has said that this needs to be a post not pre BPM. This doesn't
sound logical but maybe.
Any advice?
[Non-text portions of this message have been removed]