Bugzilla – Full Text Bug Listing
| Summary: | Cannot send report parameters when defininig interactive drilldown on the legend | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Sheldon Lee-Loy <sleeloy> | ||||||
| Component: | BIRT | Assignee: | Yulin Wang <Lionel.wyl> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Xiaodan Wang <xwang> | ||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | hchristensen | ||||||
| Version: | unspecified | Keywords: | plan | ||||||
| Target Milestone: | 2.5.0 M4 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | Non-Auto | ||||||||
| Attachments: |
|
||||||||
|
Description
Sheldon Lee-Loy
Created attachment 116091 [details]
screen shot that shows the ability to submit report parameters
Created attachment 116092 [details]
workspace that shows the problem.
Please let me which release this feature will be targeted as this is a must have for a product. Currently Legend in chart doesn’t support interactivity for each item, i.e. the interactivity hot spot is treated as a whole in Legend. Only value series supports interactivity to each data point, so it’s expected behavior. There are some reasons we can’t support it in Legend. The typical case is when you could have a chart with multiple value series definitions (your case has only one: sales), Legend can’t be separated to multiple parts. Another case is, you optional grouping is by productLine as a group key, if you set another parameter value which is not this group key, so the parameter values may be various in each group. As a workaround, you have to add interactivity to value series. Legend only supports interactivity (such as hyperlink and scripts) as a whole, except built-in highlight and toogleVisibility. For the enhancement, we could create a javascript variable for current legend item’s value, so user could use js variable instead of evaluate expression to pass the parameter value. Moreover, we should disable the data binding in expression builder, since it’s not supported in Legend case. (In reply to comment #4) > As a workaround, you have to add interactivity to value series. Legend only > supports interactivity (such as hyperlink and scripts) as a whole, except > built-in highlight and toogleVisibility. > For the enhancement, we could create a javascript variable for current legend > item’s value, so user could use js variable instead of evaluate expression to > pass the parameter value. Moreover, we should disable the data binding in > expression builder, since it’s not supported in Legend case. Could you explain the work around in more detail? What is the target date of BIRT 2.5.0? I couldn't find a release plan on the website. (In reply to comment #5) > (In reply to comment #4) > > > As a workaround, you have to add interactivity to value series. Legend only > > supports interactivity (such as hyperlink and scripts) as a whole, except > > built-in highlight and toogleVisibility. > > For the enhancement, we could create a javascript variable for current legend > > item’s value, so user could use js variable instead of evaluate expression to > > pass the parameter value. Moreover, we should disable the data binding in > > expression builder, since it’s not supported in Legend case. > > Could you explain the work around in more detail? > > What is the target date of BIRT 2.5.0? I couldn't find a release plan on the > website. > I mean you should add interactivity to value series so that the interactivity could work when you click/mouseOver/... to the Bar/Line/Pie... I don't know the date yet. Added two variables: legendItemText and legendItemValue in expression builder for Legend's hyperlink drillthrough/bookmark/URI. Variable legendItemText is the value of current Legend item's text, and variable legendItemValue is the value of current legend item's showValue when color is by series and showValue is enabled. Also remove column binding expressions from expression builder since it doesn't fit legend type. In this case, please use legendItemText instead of column binding expression. Both variable legendItemText and legendItemValue can be passed to the target report. Verified in build (2.5.0.v20081223-0630). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. This enhancement/defect was mistaken closed as part of the TPTP 4.6 Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes) since the originator of this enhancement/defect has an inactive Bugzilla account. If this enhancement/defect is still unresolved and reproducible, please re-open. |