Uploaded image for project: 'Pentaho Reporting and Pentaho Report Designer'
  1. Pentaho Reporting and Pentaho Report Designer
  2. PRD-5871

Location prompting is not working if one opens a report in a new tab

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: High
    • Resolution: Not a Bug
    • Affects Version/s: 7.0.0 GA
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
    • Story Points:
      0
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
    • Sprint Team:
      Tatooine (Maint)
    • Steps to Reproduce:
      Hide

      1) Open an attached report
      2) Click "Run in background"
      3) Select a location
      4) Wait some time. check that the report is stored in a selected location
      5) Open an attached report in a new tab
      6) Click "Run in background"
      Actual result: the location prompt is not shown
      Expected result: the location prompt is shown

      Show
      1) Open an attached report 2) Click "Run in background" 3) Select a location 4) Wait some time. check that the report is stored in a selected location 5) Open an attached report in a new tab 6) Click "Run in background" Actual result: the location prompt is not shown Expected result: the location prompt is shown

      Description

      A technical debt after the Ewok team work.

      (Technical note:

      The location prompt uses the GWT file-browser dialog that is provided by Mantle/PUC in the top-window-frame. When running in a new tab or embedded in a 3rd party application, there is no Mantle/PUC and thus there is no code for the browse-dialog.

      3 options to solve this:

      (1) Try to get the dialog to work: Need to figure out whether we can instantiate PUC 's dialog without the PUC frame itself. It may not be possible at all.
      (2) Hide/disable the functionality. Either users will not be prompted for a location and we store it in a default place, or run in background will not be available. If a OEM embeds the report, there is a good chance that they dont want the run-in-background function at all as they would then need to allow their user to open that report from the saved location.
      (3) Hybrid: Make it an OEM hook, where we check whether the function to call the file-browser is available. If available, we assume that it behaves like PUC. OEMs can provide their own file-browser implementation. If not available, or not accessible, we assume that run-in-background is not possible, and disable/hide the function.

      Tecnhical note ends)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ezhuk Egor Zhuk (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: