Imagine that you have a custom Dynamic Schema Processor in your BA Platform that is responsible for changing Mondrian schema every time an Analyzer Report is executed. For example we do it to apply some additional security layer. Now lets say you want to create a report in the Report Designer, publish it to the BA Server, but at the same time you would like to reuse the existing Dynamic Schema Processor to modify the data present in that report. In our case: to apply security restriction by limiting records that the user will see when he/she opens this report in BA Server.
Continue reading Apply Dynamic Schema Processor to a report created in the Report Designer
You have a Mondrian Schema uploaded to the BA Server and you would like to modify it in the run time. For instance in our project we change it for every user authenticated to the platform to apply security restrictions. This modification aims to limit records that users are able to see in reports based on that Mondrian Schema.
Continue reading Dynamic Schema Processor : Modify Mondrian Schema in run time
When creating custom classes for Pentaho BA Server, we can ask Spring to create their instances for us, by simply putting necessary settings in one of the application context configuration files under ../biserver-ee/pentaho-solutions/system. But what if our new class has to be created outside of spring and we still need to inject dependencies from the context created for Pentaho? Particularly this becomes a problem when we would like to inject some dependencies into Dynamic Schema Processor.
Continue reading Inject spring bean into Dynamic Schema Processor in Pentaho