Way to eliminate "all attachments" from being sent using OOTB corr rules?
Did you ever find a solution for this? I have a similar question but not using the LS base ... can't find an easy way to eliminate "all attachments" from being sent using OOTB corro rules
Content from original question: SCENARIO: when "GeneratePDFandAttach" method is called in an activity (for second time), only one attachment is to be attached, but all attachments which are attached to current case ((say) previously generated pdf in the same case(when "GeneratePDFandAttach" is called for first time in flow action, signature.png) are also being sent to email as attachments.
Thanks Paul. While useful, selecting "By Category" doesn't quite get me the fine grained level of control I wanted. If I have several "PDF"'s for example all in the same category (say, File), I still get all the PDF's sent. I guess I could get fancy and write a process that loops over them ... but that's what I'm trying to avoid. Appreciate the input.
I had a conversation with an SC this week and we were talking about this problem. In passing he mentioned "Wanna know the short cut - change the categories". If I created new attachments with a Category of "NewAttachment" and summarily updated the Category of other attachments I could isolate the new or more recent stuff based on some business rule. then I could have the email widget call only for the NewAttachments. Obviously this requires a process to update existing attachments, but that's fairly light work. In context, it is a perfectly viable solution/workaround to the issue. Thanks again for weighing in, Paul.
I found this on Mesh the other day. It seems to be a "way" to get what I'm trying to do - a methodology to allow for more fine grained control of attachment distribution via email. I haven't dug completely through it as this particular ask has gone way down on the want list, but thought I'd share. It seems to be the closest thing to an answer I've come across.
In the future, it would be great to have more control over attachments or a way to make such an action more easily extendable without heavy activity creation. (I'm looking at you, Product Team).
***Updated by moderator: Lochan to remove personal information (twitter handle)***
The status of this enhancements has been updated to 'Answered' as the Pega Product team believes that choosing the Send email smart shape > configuring the attachment categories > choosing the specific category to send the attachments is the right way of achieving this requirement.