EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB43749: How to Enable the Page Footer and Display it at the Bottom of the Page (MicroStrategy Web 9.2.x Style) using the MicroStrategy Web SDK 9.3.x - 9.4.x


Community Admin

• Strategy


When the footer section is enabled in the 9.3.x interface, it remains docked on the page as the user scrolls through the content section on the report execution page, as shown below:

When the footer section is enabled in the 9.3.x interface, it remains docked on the page as the user scrolls through the content section on the report execution page, as shown below:
 

ka04W00000147vFQAQ_0EM440000002GbM.png

 
If this behavior is desired, follow KB43685 to enable the page footer with the default layout settings.
 
If it is preferrable to have the footer sectiion situated at the bottom of the report execution page below the report content, follow the steps below:

  1. Open the Web Customization Editor and switch to the Application Settings view.
  2. Create a new plugin and assign it a meaningful name.
  3. Navigate to and double-click to open the report executioon page under Strategy Web Configuration > Pages > report (Report Exeuction).
  4. Switch to the Template Properties tab > Default.
  5. Right-click on the content section > Edit current file (this should open the Report_Contents.jsp file).
  6. Switch to Project Explorer > jsp > open the Copyirght_Footer.jsp file.
  7. Append the contents of the Copyright_Footer.jsp file into the Report_Contents.jsp file.
  8. Save the file and restart the application server.

 

ka04W00000147vFQAQ_0EM440000002GbN.png

 
The example provided in this document is provided “as-is” to the user and assumes that the user:

  • Can program, compile (e.g. javac, jikes, etc.), and execute Java programs
  • Can configure environment variables (e.g. JAR files, property files, etc.)
  • Have all the necessary tools to create Java applications (JDK, IDE, etc.)
  • Has access to the Strategy SDK documentation.
  • Has read the customization warning at the bottom of this document

PREREQUISITES:
 
For the sample to work, the Strategy Web JAR files must be accessible by the Java Runtime
Environment. The Strategy Web JAR files can be found under:

  • Strategy Web Universal (JSP): {web_root}/WEB-INF/lib directory.
  • Strategy Web (.NET): Program Files\Common Files\Strategy directory. 

ADDITIONAL INFORMATION:
 
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://community.strategy.com/topic/0TO44000000FliLGAS/sdk).
 
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at https://www.microstrategy.com/en/support/contact-support.
 
 
CUSTOMIZATION WARNING:
 
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.


Comment

0 comments

Details

Knowledge Article

Published:

June 22, 2017

Last Updated:

June 22, 2017