Question
Virtusa
US
Last activity: 10 Jul 2019 12:09 EDT
Send Email - Link -Attachments
Hi ,
i am running an activity using startFlow metho to run a flow which contains send email smart shape , i see that each time i run the activity there is Link-Attachments instance created , i do not have any work objects created while running startFlow method , How do i skip this Link-Attachments getting created .
Thanks.
Pegasystems Inc.
US
Is the issue you are facing: despite not creating or persisting a case, because you are starting a flow that contains an Email shape, a Link-Attachment instance is created that would never be used?
Instead, you just want to send an email. Is that true?
Pegasystems Inc.
US
You should be able to call CorrNew directly.
f you already have a Data-Corr-Email instance prepared you can use that as the step page and simply call Send.
Check for errors using StepStatusFail.
FYI: if you were at an assignment when sending you would also check for: newAssignPage.pyFlowType=="FixCorrespondence"
Virtusa
US
Pegasystems Inc.
US
The Send Email Smart Shape assumes you want to send an email immediately, plus have a Link-Attachment to reference the Email that you sent.
The "brute force" way to send an email without all the "bells and whistles" is to construct a Data-Corr-Email instance directly then use that class's Send activity.
In the LSA course there is an FSGEmail case that leverages an EmailEditor component. The FSGEMail case copies the most recently linked/attached Data-Corr-Email to an embedded page named ".EditedEmailAttachment". When the "Send" button is clicked in the Rich Text Editor UI, an activity named UpdateAttachmentAndSend is called. The first step in that activity calls Send with the step page being .EditedEmailAttachment.
But here a Data-Corr-Email instance is NOT constructed "from scratch". The Correspondence rule given to Corr-New is configured as "Attach & Hold" so generates a Link-Attachment. FYI: The Send Email shape ignores Attach&Hold.
Again, if you can find a way to construct a Data-Corr-Email instance, you can send the email yourself, but constructing it can be complex since you have recipients and possible email attachments to think about, not just the email body which you could generate using Property-Set-Corr if you wanted.
If the Email your are sending is virtually the same, except for recipients, what you could is Save-As a generated Data-Corr-Email instance in a way that you can easily find it again using a lookup, then use that instance as a template.
The Send Email Smart Shape assumes you want to send an email immediately, plus have a Link-Attachment to reference the Email that you sent.
The "brute force" way to send an email without all the "bells and whistles" is to construct a Data-Corr-Email instance directly then use that class's Send activity.
In the LSA course there is an FSGEmail case that leverages an EmailEditor component. The FSGEMail case copies the most recently linked/attached Data-Corr-Email to an embedded page named ".EditedEmailAttachment". When the "Send" button is clicked in the Rich Text Editor UI, an activity named UpdateAttachmentAndSend is called. The first step in that activity calls Send with the step page being .EditedEmailAttachment.
But here a Data-Corr-Email instance is NOT constructed "from scratch". The Correspondence rule given to Corr-New is configured as "Attach & Hold" so generates a Link-Attachment. FYI: The Send Email shape ignores Attach&Hold.
Again, if you can find a way to construct a Data-Corr-Email instance, you can send the email yourself, but constructing it can be complex since you have recipients and possible email attachments to think about, not just the email body which you could generate using Property-Set-Corr if you wanted.
If the Email your are sending is virtually the same, except for recipients, what you could is Save-As a generated Data-Corr-Email instance in a way that you can easily find it again using a lookup, then use that instance as a template.