Project: talenddataquality
Issue TDQ-6903: Enable contextual Data mart in the report editor
The feature is that we need to be able to use a contextualized connection in the report editor. We need: 0. a new field in the pref page to set the default path of the logo 1. a button in the preference page to export the data mart connection and path information (folder and logo) as a context. 1b. a button in the preference page to revert the context (see the behavior of the database connection revert button). 2. a button in the report editor to attach a context to the report (it will select a context from the repository view). This button is to be added in the context section. 3. run the report with contextual information 4. change the context used by a report 5. export the context information when we export the items The export context action will open the new context wizard. Each variable will start with the report name followed by _. For instance, if the report name is "crm", then the variables will start with "crm_". The variable exported from the preference page only concern the fields available in the preference page: database connection, logo path and folder path. In the report editor, there will be more variables: See attached screen capture "export_context2.png". A "Context" section must be added after the "Database Connection" section in the report editor. In this section, a combo list with the context names will be displayed. The report is executed with the selected context. When there is no context, the combo list is empty. Technically, the EMF context items must be copied into the report item. See how it is done for jobs. {code} {code} (Optional in a first implementation) A. Ideally, if possible, the view Context could be reused to display the context attached to the Report. See with DI team whether it's possible or if the Context view can only be linked to jobs. B. When the repository context is updated, a pop-up should tell whether to propagate the changes. Then the list of impacted reports should be displayed. If the user choose to propagate the changes, a copy of the repository context is done into the report item (same behavior as the DI jobs).
Story points: 20