Very often i run into the need to embed a webi report part, such as a table block, in a separate application, outside of InfoView. There are many ways to accomplish this, from leveraging the webi REBean SDK to using the openDocument api. The openDocument api in particular is very handy, since it is so easy and simple to use, and requires no coding. However, in many cases, all that is needed is the report block to be displayed on a screen, rather than the entire webi interface. Using some carefullt placed HTML placed DIVs, you can accomplish that.
While the openDocument api does have the ability to display specific report parts, using the sReportPart argument, it provides only limited functionality. It is officially only supported for Crystal (although it does work with webi as well), but fails to include some of the important controls that come with webi such as pagination, filters, saving and zooming. Leveraging html DIVs, you can “hide” the elements of the webi page that you are not interested in showing, and create a webi presentation, with no coding, that can be included in an external web application.
In the example captured above, you can see an Xcelsius selector with a webi table underneath. The selector uses an EIC to pass a parameter value to the webi report part using the openDocument api and a JS function reloads the webi iFrame when the EIC value changes. DIVs are used to cover up all the webi “extra” unwanted elements, and expose selected menu options as well as the table block.
You can find here the sample files, zipped (xlf, swf, html and .wid, based on e-Fashion).