Question

Workflow Name token issue in email

Workflow Version 10

Updated June 7, 2019

asked on March 12, 2019

Hello,

I have recently noticed an issue when using the Workflow Name token in an email. I use this token all the time in email and have never had an issue until this process. I have not changed anything. We have not upgraded recently. I am using designer 10.2.0.216.

What I am seeing is that the token no longer recognizes the spaces but rather tries to encode the workflow name. I now have 202D20 in the name every places there should be a space.

Did I miss something? I do not have the encoding function on.

Thanks.

WorkflowNameToken.png (51.14 KB)

| Download

0 0

Answer

SELECTED ANSWER

replied on March 12, 2019

This seems to be a bug that was introduced between 10.0 and 10.2. It is also present in 10.4. I'll log it and we'll look into it for 10.4.1. Reference ID 160191.

0 0

Replies

replied on March 12, 2019

Did you recently upgrade from 10.0 to 10.2?

0 0

View 1 previous reply

replied on March 12, 2019

No. Our upgrade was more than 4 months ago. And I have used the token since then just fine.

Only thing that changed recently on our side is in our Outlook where it inserts a small "alert" line in all emails that come from outside sources. But our default email for workflow is from our own domain.

0 0

SELECTED ANSWER

replied on March 12, 2019

This seems to be a bug that was introduced between 10.0 and 10.2. It is also present in 10.4. I'll log it and we'll look into it for 10.4.1. Reference ID 160191.

0 0

replied on March 12, 2019

Great. Thanks.

0 0

replied on June 7, 2019

On second look, it seems this works as intended. The workflow name is the safe name (with spaces and other characters sanitized). Use the display name token instead.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow Name token issue in email

Answer

Replies

Sign in to reply to this post.