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.
In Strategy there is a search field within the attribute element prompt. The standard search may not be sufficent for users. Users can remove elements from the collection based upon a custom logic.
Below is a sample executing of this customization. To insert custom logic into the filter, users must first remove the searchPattern which was entered by the user. Once this is removed the collection will contain all available attribute elements, users can then filter down this list based on a custom logic.
Below is an image of the initial run, notice that there are 7 elements
Below is an excerpt from the collectData method inside of the customization, notice how the element with id 4 is being removed.
Sample Code/Error
//how to remove an element from the collection
we.removeItemByID(
"8D679D3811D3E4981000E787EC6DE8A4:4");
Below is an image of the result of a search being entered(note the default searchPattern was removed.
Users will need to perform the following to create this customization.
Sample Code/Error
public class browseCust extends ElementsBrowseTask{
@Override
protected void collectData(BeanTaskRequestContext btrContext)
throws TaskException {
// TODO Auto-generated method stub
AttributeBean ab = (AttributeBean) btrContext.getWebBean();
//call super prior to removing, to the origonal list is populated
super.collectData(btrContext);
WebElements we;
try {
we = ab.getAttributeElements();
//hoe to add an element
// we.add("8D679D3811D3E4981000E787EC6DE8A4:3", "darren");
//how to remove an element from the collection
we.removeItemByID("8D679D3811D3E4981000E787EC6DE8A4:4");
System.out.println("size: "+we.size());
//loop through existing list
for(int i = 0; i<we.size(); i++){
System.out.println(we.get(i).getID());
//comparison can be made based on we.displayname
System.out.println(i + ": " + we.get(i).getDisplayName());
}
} catch (WebBeanException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
//super.collectData(btrContext);
}
@Override
public void processRequest(TaskRequestContext context, TaskOutput taskOutput)
throws TaskException {
String removePtn = null;
RequestKeys rk = context.getRequestKeys();
removePtn = rk.getValue("searchPattern");
//removing the search pattern
rk.remove("searchPattern");
}
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.
