More Info about the OOTB Activity getEmailSenderInfo
Please explain more about the OOTB activity getEmailSenderInfo . Observed that, in this activity they are setting all parameters which are OUT Parameters. But where those parameters are using.
Have seen the references too, Like CorrCreate activity. But not able to find those parameters exactly.
The name itself is saying that sender info then where are those parameters are using?
Thanks in Advance.
EvonSys India Pvt Ltd
AU
Basically that OOTB activity used to fetch sender email account info which is used as sender email while sending a mail and no need to set those parameters either just enable pass current parameter page and Pega will take care. and If you want to use a particular email account as sender other than default than configure those params and and call the activity.
CPF
SG
Thanks for the reply. But I did not get exactly what I want to know (from reply) . Observed that the output of the getSenderEmailInfo is returning those parameters values only. But where those parameters are used in existing activities?
For example getSenderEmailInfo activity used in CorrNew activity. But I did not find the parameters usage which are output of getSenderEmailInfo. Could you find where those parameters are exactly used in one of the OOTB activity in CorrNew instead of considering the all references.
EvonSys India Pvt Ltd
AU
Please find below attachments where one is output values from getSenderEmailInfo and another is out params usage in sendEmailNotification ootb activity.
Accenture
SG
Hi Renuka,
you already know that getEmailSenderInfo is setting values into parameters, these values are being set from Email accounts configured in the system.
There is a default email account named "Notify" for workpool which is taken as a input to set these parametes.
After above parameters are set, those are being used in Java step defined in SendSimpleEmail and SendEmailNotification activities.
Similarly, in CorrCreate they are used in next successive Java steps defined in the activiy.
Thanks,
Upendhar V.