We are trying to implement a requirement to send various automated emails based on configurations stored on a Page List, for that we wanted to use the Split for each shape. However, when executing a send email smart shape inside of the Split for each, the correspondence rules are not getting attached to the work object. Is this a bug or not a supported configuration? I assume here the problem is with the child requestors inside the split for each. We have tested using versions 8.5.6 and 8.8.2 having the same behavior on both.
Here the current configuration we have for our POC (v 8.8.2)
Here the result once the case is executed, as you can see the history says that the correspondance was attached, however there is nothing on the case attachments.
@RobertoB6828 Can you please try enabling the include attachments checkbox to see whether any changes happening? Also can you refer the below link to check whether required informations are there in Data-corr-email page before it calls CorrAttach.
Yes, we try that too. But that check box only tells the smart shape to include attachments while sending the email. Some more interesting findings after tracing the activities:
All the correspondence rules are persisted in the Data Base.
Link Attachment instances are there as well but they are referencing the Work Pool and not the Work object.
Case is having a pzInsKey when the attachment / linking is taking place.
@RobertoB6828 not sure why this is happening. Can you once try keeping the send email smart shape outside the split for each, that is main flow. Also can you check the context/class of each pages in pagelist the flow is getting executed. The context could be the reason I guess. Can you also once try keeping your case type work class as the class for the pagelist?
The Smart Shape works as expected outside the split for each, the problem only happens inside of it.
The class of the Page List we have set it to be the same as the Work Class. as you cannot execute smart shapes on Flows derived from Data Classes.
So, we are suspecting that since the split for each will execute the flows using child requestors, these might not have the correct context maybe; or somehow their changes are getting lost at Link-Attachment level.
We have not open any service request yet, because we are not 100% sure if it is working as design or actually a bug/issue with the platform.
