I’ve been asked to create an email alert which when the Customer Credit Hold is activated by a process such as Invoicing - then the email is sent to notify Accounts.
I’m having trouble finding the right method directive to apply this email alert. I’ve tried Customer Update, CheckCredit Hold, lots of places but cannot seem to get an email to be sent.
All email info is correct - I think my bpm just isn’t been run
Have you run a Trace while entering an invoice that would cause the Customer to go on Credit Hold to see which methods and Business Objects are being called?
I use In-transaction to detect the change and add a widget to call the standard directive if cond is true. In the standard directive, I add the condition that it was called by a in-transaction process, then create the email.
Try sending the email Synchronously. I’ve had issues in the past where asynchronous emails wouldn’t send. This will also display an error to the user if the emails failed to send for some reason, like the SMTP address and port not being set up in Company Maintenance.
I usually use For each Matching…In this case it should not matter has it is one customer …
If an update would be for multiple rows…passing your conditions, “for each matching” would result I think in sending an email for each “matching” row …
Its still not working - I cant believe it - i’m using exactly the same email settings we use on APR which operates fine and also I tested normal Email function from Print and that emails too which I believe uses same company maintenance email settings.
Hi @carlawhite
have you tried to change your BPM from Data to Pre-process Update Method at Customer BO ? you can use the exact same widgets, try it, some times In-Transaction Data BPM for certain tables fail to do what is supposed to do.
Have you tried it with message widgets, before the email to see if it goes through? one for true, one for false… just to make sure if it gets fired or not…
also, sometimes you need to do a recycle IIS, (at least when we were under 10.0.700 we had too often… sometimes a few times… ) but our current version does not need… (10.2.300)