PMA variable (Class name internal)

Post Reply
Posts: 39
Joined: 02 May 2018, 12:20

05 Dec 2018, 15:00


as you know we are evaluating the suite, we are going through this below xsl which that section renders application name with a hyperlink.


<xsl:call-template name="RenderInstanceLink">
<xsl:with-param name="theSubjectInstance" select="current()"/>
<xsl:with-param name="theXML" select="$reposXML"/>
<xsl:with-param name="viewScopeTerms" select="$viewScopeTerms"/>
<xsl:with-param name="targetMenu" select="$targetMenu"/>
<xsl:with-param name="targetReport" select="$targetReport"/>

We wanted to understand the class internal name how it is formed in the above code so that it carries appropriate PMA variable value to the hyper link.

Your earliest response will save hours of exploration for us.

Thanks in advance.

Posts: 102
Joined: 17 Feb 2009, 20:19

06 Dec 2018, 20:46

The <xsl:call-template name="RenderInstanceLink"> calls a template for putting the pop-up menu box on the link. Note, the menu is assigned to the class of the subject instance in the repository.

The subject instance is the focus of that link, so in the code:
<xsl:with-param name="theSubjectInstance" select="current()"/>

'current()' is calling the instance that is the subject of the node you have just called in the template, in the view you mention, the first <td> is looking at each application that the catalogue template is sent when
<xsl:apply-templates select="/node()/simple_instance[(type = 'Application_Provider') or (type = 'Composite_Application_Provider')]" mode="Catalogue">...</xsl:apply-templates> is applied.

When you click the link, the view(s) that are assigned to the menu use the value that is assigned to theSubjectInstance to identify the value for the PMA in the receiving view.

In the receiving view the PMA variable in the URL then gets assigned to param1, which you can use in your view to get the specific instance from the repository for your view

Hope that helps

Post Reply