Opened 8 years ago

Closed 4 years ago

#120 closed Enhancement (Fixed)

Query Selection Page Footer

Reported by: Lois Haggard Owned by: Lois
Priority: -Low Milestone: 2.3 - Testing
Component: View-App Version: 2.3
Severity: Unknown Keywords: query selection
Cc:

Description (last modified by Lois Haggard)

The query selection page should have the same ORG_UNIT page footer as the query builder pages for that query module.

Currently it has the default site-specific footer.

Change History (12)

comment:1 Changed 8 years ago by Lois Haggard

Description: modified (diff)

comment:2 Changed 8 years ago by Garth Braithwaite

Can't do it as currently implemented because the selection page XML:

a) don't have an ORG_UNIT_NAME xml element defined, b) a given builder page can reference many qm.xml's each with a different ORG_UNIT_NAME so which one is the one to use?

Could add that element to the selection page's XML structure then you could have that capability.

comment:3 Changed 8 years ago by Garth Braithwaite

Owner: changed from Garth to Lois Haggard

comment:4 Changed 8 years ago by (none)

Milestone Parking Lot deleted

comment:5 Changed 8 years ago by Lois Haggard

Milestone: Unassigned
Severity: Unknown
Version: 2.0Undetermined - New Item

comment:6 Changed 8 years ago by Garth Braithwaite

Owner: changed from Lois Haggard to Unknown

comment:7 Changed 7 years ago by Eleanor Howell

Keywords: query selection added

comment:8 Changed 7 years ago by Kim Neerings

Priority: Unknown-Low
Version: UnknownParking Lot

comment:9 Changed 4 years ago by Garth Braithwaite

Milestone: Unassigned2.3 - Testing
Owner: set to Lois
Version: Parking Lot2.3

comment:10 Changed 4 years ago by Lois Haggard

I put an <ORG_UNIT_NAME> element with a valid org until name (BVRHS) in my selection file, as a child of the <QUERY_CONFIGURATION_SELECTION> element. It had no effect. I continued to see the default page footer on my selection page. I did not see the BVRHS footer.

comment:11 Changed 4 years ago by Garth Braithwaite

Added <ORG_UNIT_NAME> element processing to the core XSLT and XSD.

Last edited 4 years ago by Garth Braithwaite (previous) (diff)

comment:12 Changed 4 years ago by Lois Haggard

Resolution: Fixed
Status: newclosed

Tested 6/22/2015. Works.

Note: See TracTickets for help on using tickets.