Today to have a parameter at the dashboard level, we use the global flag for parameters.

New suggested flow:

• Deprecate the global flag.
• When adding a new widget to the dashboard, if the query has parameters we will show them to the user and let him pick what to do with them:
  1. Add the parameter to the dashboard (default option), creating a dashboard parameter.
  2. Map it to existing dashboard parameter (default option, if parameter with the same name exists).
  3. Give the parameter a static value.
  4. (Not sure we need this:) Keep it a standalone parameter at the widget level.

Things to think about:

• How to show if a widget is affected by a parameter? Maybe color code them, and show this color on the widget?