-
Instance wide Senario On/Off Swtich
User Story: As a Dataiku DSS instance Administrator that occasionally has to "turn off" Triggered Scenarios while working on a Dataiku DSS Instance. I would like a Master Triggered Scenario "Off switch". This would inactivate triggered Scenarios across all projects within a Single DSS Instance. This would mean that I can…
-
Document undocumented scenario catch-up fuctionality
I have always assumed Dataiku will not run any missed scenarios when DSS is shutdown. Turns out I was wrong, Dataiku has a built-in scenario catch-up capability. This idea is to document the scenario catch-up fuctionality as it is critical feature that Dataiku Administrators and users should know and Support have confirmed…
-
Display User ID in Last Author of Scenario
A lot of our scenarios are executed with the Run As = "Last Author of Scenario". However it is not easy to see what the actual "Last Author of Scenario" is without having to go to the history tab and checking who last made changes to the scenario. This idea is to display the user ID in the Run As drop down select like this…
-
Automatic update code env with known vulnerabilities
To stay secure I would like code env to be scanned periodically for modules and libraries with known vulnerabilities. If a vulnerability is detected the environment is resolved with patched modules/libraries. For projects running on automation a vulnerable environment is flagged and a bundle with updated env is created and…
-
Native support for Markov models
(VisualML) support for building different types of Markov chain models. Very relevant models in marketing attribution, process analysis and customer journey analysis.
-
Support Partitioned Models for Dataiku MLOps
MLFlow integration is great, eval stores... all the MLOps goodness. Partitioning is also fantastic. However, these two do not play well. We make use of partitioned models quite a bit because we love them. The unfortunate thing is we cannot train partitioned models with MLFlow and starting from 11.2 we cannot use eval…
-
Custom Flows Views
I saw this new Product Idea about an Easier access to Determine Data Set Rebuild Behavior Setting and I thought that sure could be a new Flow View. I then thought well I had similar requirements in the past where some use case would have needed a special flow view that wasn't available. I then thought that the use case…
-
Some way to more easily convert flows to API endpoints
It would be great if there was some way to (more easily) build API endpoints from Flow functionality. Sometimes we'd have a Flow built out using python and visual recipes for stuff like data transformations, feature engineering etc. but then want to deploy the functionality as an API. In that case we'd have to replicate…
-
improving documentation in scenarios
I sometimes find that scenarios lack documentation, particularly when it comes to documenting individual steps within a scenario. Additionally, I am disappointed that (IMO) the new versions of Dataiku have resulted in a less user-friendly documentation experience. The 'summary' tab has disappeared, and the scenario…
-
Easier recipe replacement
Sometimes, I need to change out the recipe I've used in a flow. For example, I may have used a sync before, but now I need a filter or a sort recipe instead. Or I may have used groups, but now need a pivot, etc. Many of the parameters of the recipes will be preserved. For example, computed columns, input and output…