With Citrus, we added static parameters. Although this already brought us closer to our goal to total world domination for our reporting tool (Ya know, you have to have some small goals to make a life worthwhile) it is not enough to solve the more complex problems. Therefore, the Lemonade release pushes the frontier a bit further and allows a whole range of new features.
By selecting a tiny little check-box, parameters can now be excluded from the UI-generation. The parameter itself still behaves like any other parameter and thus takes part in the formula-calculations and is part of the validation.
Parameter Validation can be loosened
When this flag is set to false, the validator will accept other values than the ones that have been specified in a list-parameter. With relaxed validation, you can easily write WHERE conditions, that accept partial matches or contain “LIKE” clauses. For the sake of security, we none-the-less default this feature to strict-checks.
Every List-Parameter can now have computed display-texts. This way, you are no longer limited by what your datasource can produce, and even a simple data-source like an XML file or a static table-datasource can produce better looking prompts.
A post-processing formula processes the parameter-input before it gets validated or passed into the report. The post-processing can either be defined on the parameter itself or can be defined as an extra field by using a hidden parameter. The computed value will still be validated by the engine and thus using formula’s does not necessarily mean you have to fear that illegal input comes through. Formulas allow you to access runtime information, like the current user’s roles or the user’s name via the ENV(..) function.
All these features are available in the CI-build. To make use of them in the platform, you will have to upgrade the reporting-engine and the reporting-plugin of the 3.5-GA BI-server.
Next stop: Dynamic mondrian roles and dynamic security information for JDBC datasources.