Uploaded image for project: 'Community Dashboard Editor'
  1. Community Dashboard Editor
  2. CDE-825

DashboardComponent: parameter propagation should take into account all the mapped parameters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.0 GA, 6.1-16.08.18
    • Component/s: None
    • Labels:
      None
    • 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.

      Description

      Currently a parameter is propagated from the MainDashboard to the SubDashboard when we call a fireChange.
      However, when we change more than 1 parameter, fireChange should also set the values from those mapped parameters.
      Example:
      MainDashboard has a dashboardComponent with 3 parameters mapped:

      //param1 = param2 = param3 ="Default";
      dashboard.setParameter("param1", "Custom");
      dashboard.setParameter("param2", "Custom");
      dashboard.fireChange("param3", "Custom");
      

      Expected Result:
      Sub dashboard to have param1, param2 and param3 set to "Custom"

      Actual result:
      Sub dashboard has param1 and param2 set to "Default", and param3 set to "Custom".

      Suggestion:
      Upon fireChange, dashboardComponent should actually call setParameter for all the mapped parameters, and only then fireChange for the parameter listened parameter.

        Attachments

          Activity

            People

            • Assignee:
              wfaulkner William Faulkner
              Reporter:
              jvelasques Joao Velasques (Inactive)
            • Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: