Community
Participate
Working Groups
a) Add property on parameter to tell whether this parameter is multi-value. choice type, with choice value: simple, multi-value, ad-hoc. Default value of this property is “simple”. Currently, ROM parameter definition has four display types: text, radio, listing, combobox. After discussion, only the listing parameter could be a multi-value type parameter. So, which means, if the parameter is multi-value type, from parameter requester page, user only can select multiple values from the drop down list, but can not input any value. b) Support for IN operator in the dataset filter definition
Pleae make the Viewer changes ( requester changes ) after hte model changes are done. Viewer support - If the parameter is multi-value type, show allow user to select multiple parameter values.
Model part is fixed. Assign viewer to fix viewer part.
we should also support optional multi-value parameter. To make optional parameter working, BIRT need to be enhanced to support optional filter condition. To support option filter, we need to add a property in filter condition structure. An optional filter condition will not be applied by DtE if the value of the filter condition is NULL. This will be required to support optional parameter in BIRT. Currently BIRT has the concept of optional parameter, however, if the parameter is used in filter condition or data set query, the filter or query condition will also be applied even if the user didn't specify the value for the parameter. This is not what users would expect. To fix that, we need to introduce the concept of optional filter condition. A optional filter condition will be applied only if the value of the condition is not NULL.
Support multi-value parameter and pass object array to engine. Currently, don’t support displayText for multi-value parameter. In the furture, engine should provide new APIs to support it.
Does model also support the optional filter condition?
Yes Model already supported the isOptional for filter condition.
Close it.
