URL Encoding Inside Email Templates in 6.3 | Community
Skip to main content
bobbym33667819
bobbym33667819
New Participant
September 5, 2018
Solved

URL Encoding Inside Email Templates in 6.3

  • September 5, 2018
  • 3 replies
  • 2191 views

Hi Everyone,

We are using the default templates for workflows and tasks emails located at /etc/workflow/notification/email/default and /etc/workflow/notification/email/tasks. What we are facing issue with is getting the url to our assets being displayed properly so the users can be redirected to them. Our assets have spaces in their names so ${host.prefix}${payload.path.open} returns this for example http://localhost:4502/assetdetails.html/content/dam/msi-dam/admin/LPAVNPRAGRE1224 Single F Product Scan.tif.

Is there a way we can encode the payload path as url and get it as http://localhost:4502/assetdetails.html/content/dam/msi-dam/admin/LPAVNPRAGRE1224%20Single%20F%20Product%20Scan.tif for example?

Thank you very much,

Bobby

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 arunpatidar

Hi,

${payload.path.open} is already encoded for pages but not for assets. Not sure why is it not encoded for assets.

You may try to send email using custom process step, where you can customise urls based on your requirement.

3 replies

arunpatidar
arunpatidarAccepted solution
New Participant
November 16, 2018

Hi,

${payload.path.open} is already encoded for pages but not for assets. Not sure why is it not encoded for assets.

You may try to send email using custom process step, where you can customise urls based on your requirement.

Arun Patidar
kautuk_sahni
kautuk_sahni
Employee
November 16, 2018

Arun Patidar​ any Help here?

Kautuk Sahni
jetate
jetate
New Participant
October 25, 2018

Were you able to find a solution to this? I'm having the same issue.

Terms & ConditionsAccessibility statement

Loading footer...