KB40484: How to prevent all reports or a single (or subset) of reports from going to History List using the MicroStrategy Web SDK 2021 and above when the preference “Add reports and documents to History List” is set to automatic

SUMMARY

When the following Web Preference is set to Automatic, all reports and documents in Web will be sent to History List:

 
The following technote describes the steps to be taken to prevent all reports or a single (or subset) of reports from going to history list when this preference is set to automatic.
 
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.

Note: More elaborate programs will require additional library files and are out of the scope of this document.
 
Using the Web Customization Editor to create a plug-in
 
Strategy SDK provides a Web Customization Editor that can be used to create a customization plug-in. The following steps show how to create the plug-in and deploy.

• Launch the Web Customization Editor.
• Create a new plug-in and give it a meaningful name. For example: DoNotSendToHistory. (For step by step instructions on creating a new plug-in, please navigate to Home > Web SDK > Customizing Strategy Web > Web Customization Editor > Features and Customizable)
• Click in Strategy Web Configuration inside the Application Settings view to expand the hierarchical tree. The expanded list comprises the different settings that can be modified to perform customizations.
• Navigate to Pages.  Right-mouse click report(Report Execution) and select Create New Add-On to launch the New Add-On Class Wizard.
• Click Browse... next to the Source folder’s text field to select the src folder and click OK.
  Enter the following information for the rest of the text fields:
  Package: ##Any package the client wants to use##
  Name: ReportSetFlagsAddon
  Add-on description: This add-on will prevent reports from going to history list. 
  
• Click Next. Click Finish. For additional information on Add-On creation, reference the MSDZ (Home > Web SDK > Customizing Strategy Web > Part II: Advanced Customization Topics > Customizing Add-ons> Add-on Creation)
• Change the class extension from
       public class ReportSetFlagsAddon extends AbstractAppAddOn to
       public class ReportSetFlagsAddon extends ReportSetFlagsAddOn
  
• Add the following method public void setReportExecutionFlags(ReportBean rb, RequestKeys keys)
  Reference: https://resource.microstrategy.com/MSDZ/MSDL/921m/docs/ReferenceFiles/com/microstrategy/web/app/addons/ReportSetFlagsAddOn.html#setReportExecutionFlags(com.microstrategy.web.beans.ReportBean, com.microstrategy.web.beans.RequestKeys)
  
• Add the following code to the setReportExecutionFlags method:
  
  Java
  

    try {	      ReportBean _rb = rb;	      if (_rb == null)	        return;		      //Information needed to prevent a single report from going to history list	      String id = _rb.getObjectID();	      System.out.println("Object ID is: " + id);		      if(!report_id.equals(id)) {	        return;  // exit if condition fails, else resume.	      }	      int executionFlags;	      executionFlags = _rb.getExecutionFlags();	      _rb.setExecutionFlags(executionFlags & ~EnumDSSXMLExecutionFlags.DssXmlExecutionSaveToInbox);	    }	    catch (Exception ex) {	      ex.printStackTrace();	    }

  
  
   
  
• Save the changes.
• Double-click report(Report Execution) to open the editor.
• Click on the Add-on Properties tab.
   
  

• On the Add-On Properties tab, the custom add-on class should be listed under the Class Name:
  

• Set the new addon in the first place in the list of addons using the arrow button at the right:
  
  

• Add to the new add on, the same properties with the same values as in the original OOTB addon:

1. Save the new changes.
2. Restart the Web Server to see the changes applied in Web.

 
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.