...
The following stories are driving much of the architecture for this feature set.
Use Case: A New Datasource
...
“X” has come on the market, and Product Management wants Spoon, Report Designer, Datasource Wizard, and Instaview to all access this datasource
- Current approach – Implement things multiple times for each pillar – A new DataFactory and Datasource Editor dialog in reporting, a new Kettle Plugin including a Step and Step Dialog in Spoon, a new capability within the datasource wizard, a template in Instaview.
- Long term approach – Implement a new Kettle Step and Kettle Step Dialog in XUL, a template for reporting, instaview and datasource wizard.
- The initial experience in report designer should feel native – I should see "X" “X” appear in my available datasources, I should be able to add a new "X"“X”, customize the XUL dialog with connection and query properties, and save that prpt, edit, etc.
Custom Inline ETL Use Case:
- I'm I’m a super IT guy, and the new Datasource "X" doesn't “X” doesn’t meet my needs – I want to do a geo lookup of the IP address and group by country in the report
- I read in the advanced section of Report Designer Guide that certain datasources are powered by Kettle's Kettle’s transformation engine, and I can augment the inline etl by modifying my report's report’s transformation
- I export the KTR from the report designer, open it in Spoon, and then add the geo lookup step in the transformation
- I then point the new KTR in the report and have access to the Country data
- Question – at this point, should I still be able to edit Datasource "X" “X” natively in Report Designer? In Insta, we show warning messages when you go into this mode, but we'd we’d need to speak with Rob and Doug to understand what the experience is when a user has started customizing the transformation and gone off the standard path – in this scenario, as long as that Input Dialog "X" “X” is still labeled "Input" “Input” in the template, should it just stay in Native mode?
Custom Template Use Case:
- I'm I’m a super IT guy and I'm I’m supporting a bunch of business users. They all want access to MongoDB in Report Designer enriched with GEO and other items, but I don't don’t want them to write their own JSON queries.
- I build a custom template that is driven by Parameters vs. the MongoDB Input Dialog - It appears in the datasources as "My “My Company Datasource"Datasource”, and the business users can quickly select from the dropdowns their preferences for the query
...
A - As a Pentaho PM and developer I want...want…
- Any data source that we create can immediately be used anywhere. No more checklists of which data sources can be used from which tools.
- Easier maintenance, a bug gets fixed once and it is fixed everywhere
B - As an end user I want...want…
- Same User Experience everywhere, less learning curve and training.
- A native app experience. UI should match the application look and feel. Swing feel in PRD, SWT feel in PDI and PUC look and feel from the BA Server
C - As a BI Architect I want...want…
- To be able to create, download new and/or modify existing datasources throughout the suite in a consistent, easily understood manner
- Make these new data source available to all my users with one quick and easy step
- Sometimes I want my changes to effect all reports that use the modified datasource
- Sometimes I want my changes to ONLY effect new reports that use the modified datasource
D - As an OEM I want...want…
- Complete control over the datasources that my embedded Pentaho instance can access
- Create, modify and deploy new datasources easily