Hello, I am testing AEM forms with workflows. I found some documentation that I used to configure the workflow https://experienceleague.adobe.com/docs/experience-manager-65/forms/workflows/aem-forms-workflow-step-reference.html?lang=en#send-email-stephttps://experienceleague.adobe.com/docs/experience-manager-learn/forms/handling-af-form-submissions/configuring-adaptive-form-to-trigger-workflow.html?lang=enhttps://experienceleague.adobe.com/docs/experience-manager-learn/forms/handling-af-form-submissions/configure-af-to-trigger-aem-workflow.html?lang=en My workflow:1. Assings form data do variable and sets some additional variables to include in the email2. Generates DOR3. Sends email that should include DOR as attachment Send email attachment config: Payload: When I test this I can see that DOR is send as the attachment but it has incorrect name (without any extension) - is this a bug in the workflow step or am I doing something wrong ?

B

bartek_887

New Participant

Solved

Send email attachments name invalid

Forum|Forum|3 years ago
May 10, 2022
2 replies
1022 views

Hello, I am testing AEM forms with workflows. I found some documentation that I used to configure the workflow

My workflow:

1. Assings form data do variable and sets some additional variables to include in the email

2. Generates DOR

3. Sends email that should include DOR as attachment

Send email attachment config:

Payload:

When I test this I can see that DOR is send as the attachment but it has incorrect name (without any extension) - is this a bug in the workflow step or am I doing something wrong ?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by abhishs

This is a regression and has been fixed with the 6.5.13.0 release which will be out in the first week of June 2022. If you are on 6.5.12.0, please open a support ticket to get the hotfix.

A

abhishsAccepted solution

Employee

This is a regression and has been fixed with the 6.5.13.0 release which will be out in the first week of June 2022. If you are on 6.5.12.0, please open a support ticket to get the hotfix.