The following sample would be useful in scenarios where users would like to modify the event for a link of a report using Strategy web SDK version 9.x and 10.x. In the example below the edit link has been modified to return the execute event instead of the edit event so that clicking on the link would execute the report instead of opening it in design mode.
Note: The list of events that can be called for a report can be found here .
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.
Steps:
Extend the FolderViewTransform and override the getEditEvent() method which is used for generating the event for the edit link on the Folder page for reports as shown below,
Sample Code/Error
public WebEvent getEditEvent(WebObjectInfo object) {
WebEvent result;
//Retrieve the object type
int iObjectType = object.getType();
switch (iObjectType) {
//If the selected link is for a report then instead of returning the edit event return the execute event
case EnumDSSXMLObjectTypes.DssXmlTypeReportDefinition:
result = EnumReportBeanEvents.REPORT_EVENT_EXECUTE;
break;
//Otherwise, return the event defined on the parent class
default:
result = super.getEvent(object);
}
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 the
MicroStrategy Developer Hub.
To access the Strategy Developer Hub, 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 Hub, 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
http://www.microstrategy.com/Support/ContactUs.asp.
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.
421489
