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; } } }

Export Content for Merge Tags instead of Code

Melissa Morrison

RBC is requesting when exporting content from the library to see the values in content merge tag instead of the code.

Find more posts tagged with

Future consideration

Status: Future consideration

Comments

sathish s

@Melissa Morrison Though it is content merge tag value, if we directly export the value then there will be problem in two cases

While viewing the response I will not know which value is from merge tag and which value is from actual response
While importing the response, if the user change the content merge tag value then it is not possible to identify the change as we do not get any merge tag name.

We have to think through this and wait for the request from other customers too.

Right now we will not pick this.

But we will reconsider in future.

Melissa Morrison

@sathish s Understood the logic. I am sharing an image from Qvidian shared by RBC which has their export options to include default content or not.

sathish s

@Melissa Morrison In the image, it looks like they have a configuration to select and export the values. This is fine but when the same file is imported then it cannot be imported with the same file as we will not have the merge tag name.