This example will show how developers can create a toolbar button that will export a specific Strategy document. This would be useful for those who want to make a particular document accessible to their users at all times.
STEPS TO REPRODUCE:
public boolean processRequest(RequestKeys keys) throws WebException {
WebEvent event = getWebEvent(keys);
if(event == null) {
return super.handleDefaultRequest(keys);
}
System.out.println(event.getID());
switch(event.getID()) {
case Enumexportdocumentfromreport2Events.BEAN_EVENT_EXPORTDOCUMENTFROMREPORT2 :
System.out.println("custom event was hit");
WebEvent webEvent = getWebComponent().getRoot().getWebEvent(3069);
//WebEvent webEvent = null;
if (webEvent != null) {
webEvent.setArgumentValue(EnumServletEvents.WebEventArgumentObjectID
, "FD19021F4E19112821C9C18145F118B7");
ParameterBuilder pb = new DefaultURIBuilderImpl();
pb.addEventInfo(
webEvent,
EnumEventElement.EventElementTypicalURLLink,
EnumWebPersistableState.MINIMAL_STATE_INFO
);
getWebComponent().getRoot().handleRequest(new StringRequestKeys(pb.toString() , true));
}
return true;
default :
return super.handleDefaultRequest(keys);
}
}The example provided in this document is provided “as-is” to the user and assumes that the user:
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:
Note:
More elaborate programs will require additional library files and are out of the scope of this document.
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://resource.microstrategy.com/msdz/).
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 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.