nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Get rid of Goofy merge field names!

Andrew_Smith

I just returned from Disneyland, saw Goofy. He was fun.

These goofy merge field names. Not so fun. They need to go.

Why?

They make reading a doc with merge fields more difficult during development. You have to process all the extra characters. Makes you think you have typos all over the place. Yuck.
With the prior merge fields you could guess the merge field name most of the time. Now... no way!
We used to be able to make changes to a DEMO workflow doc, download the doc and re-upload to a similar workflow in PRODUCTION so long as the fields were the same. The doc is no longer portable.

I understand this change was made to support some future feature. If you need super secret unique field names, at least let us specify it vs the random generation.

Find more posts tagged with

Status: None

Comments

David_Wieseneck

Yeah. Super confusing. Would love to know the reason for the change. There is a lack of documentation in the release notes.

Charlie_Choules

Yes, please remove these! I used to be able to draft a template document in MS Word and include the field tags and conditional logic before even uploading the document to Workflow Designer. (Then I'd simply just create the fields and conditions that I had pre-written into the template - can't help it, apparently my brain in is backwards)!

Joe_Nguyen

Hi @Andrew_Smith, Thank you for taking the time to share your feedback with us!