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: AddingNewPlaintextExportDelimiter. (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 Settings > Creating a New Plug-in in the MSDZ).
- Enable the Property Files settings from the Show Advanced Options in Strategy Preferences.
- Click on 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 Property Files -> WEB-INF -> classes -> resources and double-click MessagesBundle_en_US.properties to launch the Web Properties Editor.
- Enter a new property-value pair in the text field at the bottom confirming to the syntax nameOfProperty=value. For example: delimiter.1=Pipe.
- Click Add.
- Save the file.
- Exit the Web Customization Editor.
- Navigate to the customization plug-in folder inside the plugins folder of the Strategy Web installation.
- Create a config folder structure in \WEB-INF\xml inside the plug-in. For example: plugins\AddingNewPlaintextExportDelimiter\WEB-INF\xml\config.
- Copy the out of the box exportPlaintextDelimiters.xml into it. This file is found in Strategy\WEB-INF\xml\config.
- Copy one of the entries, and adjust it to have the chosen delimiter and custom message bundle entry for the description. For example:
<export-plaintext-delimiter desc="Pipe" desc-id="delimiter.1" key="6">|</export-plaintext-delimiter>
- Save the changes.
- Restart the Web Server.
- Launch Strategy Web to view the customization.
Note: If Internationalization is used, the following extra steps need to be taken:
- In the plugins\AddingNewPlaintextExportDelimiter\WEB-INF\xml folder, create a new file named pageConfig.xml. The contents should look like this:
<framework>
<export-plaintext-delimiters config-src="@AddingNewPlaintextExportDelimiter:/WEB-INF/xml/config/exportPlaintextDelimiters.xml"/>
</framework>
- Restart your web server.
Note: If No Delimiter (blank delimiter) is needed, the following would be used for step 13:
<export-plaintext-delimiters version="1.0">
<export-plaintext-delimiter desc="NoDelimiter" desc-id=delimiter.1 key="6"> </export-plaintext-delimiter>
</export-plaintext-delimiters>
As for
step 6, the value for
delimiter.1 should be
"No Delimiter" instead of
"Pipe". 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.