Changes between Version 1 and Version 2 of Ticket #120, comment 11


Ignore:
Timestamp:
05/18/15 16:42:58 (4 years ago)
Author:
Garth Braithwaite
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #120, comment 11

    v1 v2  
    1 Please review the title of this ticket and the comments (Query Selection Page Footer).  I'm just guessing as there's not any details on the issue but I think what you're asking for is a QUERY BUILDER/RESULT page footer which is different from the SELECTION page.  The QM builder and result page do support ORG_UNIT_NAME but only at the module level.  That is not a valid element for a CONFIG structure.  If you're still having an issue then you should check the core code - maybe you've overwrittin the value.  Core code xslt/html/query/module.Page.xslt has:
    2 
    3         <xsl:param name="Page.orgUnitName" select="/QUERY_MODULE/ORG_UNIT_NAME"
    4                 ibis:doc="Provides the associated module organization unit contact
    5                         info text which is typically used in the content footer.  The actual
    6                         org unit text is pulled from the 'org_unit.xml' file and is keyed
    7                         off of via the '/QUERY_MODULE/ORG_UNIT_NAME' element."
    8         />
    9 
    10 Which should be the correct value (if one exists).
    11 
    12 Also the org unit has been part of IBIS for a long time see system docs: http://ibis.health.utah.gov/docs/view/model/QueryModule.html#element_ORG_UNIT_NAME_Link02490EA0
    13 
    14 or the xsd/query_module.xsd for valid QM elements/structure.
     1Added <ORG_UNIT_NAME> element processing to the core XSLT and XSD.