Question
RABO Bank
NL
Last activity: 6 Oct 2016 10:40 EDT
How to Customize FROM email address in Agent Scheduler report
Hi,
We are using PEGA 6.1 SP1 version. Whenever scheduled reports sends an email from PEGA it uses "[email protected]" as FROM address by default. This part is hard coded in PEGA activity "pyActionSendMail".
Now my clients organisation blocked this domain for security reasons hence scheduled reports are not delivered. Is there a way to change this FROm address without customizing this rule? Or should i raise a SR with PEGA to address this issue.
***Updated by Moderator: Marissa. Removed user added #helpme group tag. Apologies for confusion, shouldn't have been an end-user option; added SR details***
Accepted Solution
RABO Bank
NL
Thanks RonLeeGCS for the reply.
That was a Typo. We are using PEGA 6.2SP1 version only.
This pyActionSendMail activity is called from pyTaskOutputProcessor activity where this Param is always sent as Blank by PEGA. Its a BUG. Also They should not hardcode a email address in a activity. I cross checked higher PRPC versions the same rule gets the FROM address from a Email Accoount dynamically.
So this is a BUG in PRPC 6.2 SP1 Which we need to live with or customize this rule until we upgrade the system to 7.x
Note: I raised an SR SR-A99996 with PEGA but it looks like there is no hotfix for this in 6.2SP1. Hence we need to customize this rule to change the email address.
Pegasystems Inc.
US
I don't see this activity in 6.1sp1. It exists in 6.2sp1. There, it checks if the "From" parameter is blank, and if it is, it sets the value to the default value "[email protected]":
So if you set Param.From to the value you want, it should end up as the "From" address.
Accepted Solution
RABO Bank
NL
Thanks RonLeeGCS for the reply.
That was a Typo. We are using PEGA 6.2SP1 version only.
This pyActionSendMail activity is called from pyTaskOutputProcessor activity where this Param is always sent as Blank by PEGA. Its a BUG. Also They should not hardcode a email address in a activity. I cross checked higher PRPC versions the same rule gets the FROM address from a Email Accoount dynamically.
So this is a BUG in PRPC 6.2 SP1 Which we need to live with or customize this rule until we upgrade the system to 7.x
Note: I raised an SR SR-A99996 with PEGA but it looks like there is no hotfix for this in 6.2SP1. Hence we need to customize this rule to change the email address.