View: Application Impact Analysis - Description cannot be displayed in HTML

[xiaoqi]

Hello,

I'd like to get your help on the "Description" column's display issue.

The view I'm populating is "Application Impact Analysis", the data contents are loaded and shown correctly, but the Description column - both in "Business Impact" and "Application Impact" table - are not displayed in proper HTML format.

Instead, the NewLine is displayed as

Code: Select all

<br/><br/>

. (I have one empty line between paragraphs hence I have two <br/> here).

While checking the source "application/core_al_app_impact_analysis.xsl", I see the description column is coding as below:

Code: Select all

<xsl:variable name="aDescription">
	<xsl:call-template name="RenderMultiLangInstanceDescription">
		<xsl:with-param name="theSubjectInstance" select="current()"/>
	</xsl:call-template>
</xsl:variable>

As benchmarking, I have view: "Project Catalogue by Name" which have the correct HTML format displayed in the column, while in the source file: enterprise/core_el_project_catalogue_by_name.xsl, I found the related codes as below:

Code: Select all

<xsl:call-template name="RenderMultiLangInstanceDescription">
	<xsl:with-param name="theSubjectInstance" select="current()"/>
</xsl:call-template>

The actual templated called by the two views are same. The only difference is the ones used in "Application Impact Analysis" are wrapped inside one variable definition statement.

I've tried to bypass the variable definition, and directly use the inside template call like "Project Catalogue" view, then the description shows text in HTML format correctly. Looks like this is the reason.

Before I proceed the change, may I know from you whether you can have the descriptions displayed OK in HTML, or is there any other reason here we need to wrap the "RenderMultiLangInstanceDescription" inside one variable definition? (I see it's used in later for deciding display business proc description and physical proc description.

Thanks, Xiaoqi

[jasonp]

Hi Xiaoqi,

we are happy for you to go ahead and make your change and we will add it to our list of fixes in our next release.

Thanks for letting us know.