Merge word funcitonality leaves HTML tags in final document
We are using the OOB word merge functionality to include sections in a word document, the document generation is done sucessfully but for some reason the document shows up with HTML tags in it. Pega version used is 7.1.7
Is there a way to remove them or an extra step is required in the OOB activity to allow this.?
Oscar--Sorry to answer your question with a couple more questions, but we need some more information to appropriately answer your question. No extra steps should be required to successfully generate a document.
When you say 'section' are you talking about UI screenshots? If not, what do you mean by 'section'?
Can you post a sample of the HTML tags you're seeing OR maybe even post the document?
So right now what we are doing is that on the correspondence rule we are setting up to include a section this section holds the case information in read only mode.
We have grids inside the section so when it generates it at the end it leaves like blank spaces in each of the column cells and also it shows blank spaces with values of true or false where there are some hidden sections based on when conditions
Oscar--Thanks for claifying that it's a correspondence rule including a section with grids. We have some theories, but too many to easily discuss without seeing an example. Is there any way you can share the HTML tags you're seeing OR maybe even the generated document? If you're not comfortable posting that information here, please check the PM I'm about to send you with my email address.
Oscar--I haven't heard back from you, but here's some information that may be helpful to your or others following this thread...
The sections we include in our application documentation are custom HTML, designed to be rendered by Word. I suspect the section that you are using is auto-generated, which is a process that creates HTML that is designed to be rendered by a browser within Pega’s UI. While any section can be included in a corr rule and merged into a Word document, not all HTML in every section will be designed for Word viewing, and when Word doesn’t know how to render the section content, it will show the HTML markup.