Project: talenddataquality
Issue TDQ-9141: Profiler : Allow variables, like context variables - Part I 
Allow variables, like context variables, to be valid fields in analysis and report input fields, like date range on where clauses. Today to run a profile over a date start/stop and then change the range requires hard coding and then changing that hardcoded value. Concerned analysis fields: - data filter - number of connections per analysis Concerned report fields: - output folder - output filename - execution date range (start / end) - logo file path Enable context usage of contexts in TOS DQ (only use built-in contexts => no need to display the context node in dq repository view)? is Context view reusable? Adapt the analysis editor to display the context and allow the user to switch between contexts just as in the report editor. Add a separate section "Context group" in the analysis editor AND move the current context of the report editor into a new section too.
Story points: 20