Release 3.19.0 (53) - Cassandra Clean-Up (46.37.0 // 1.179.0)
Modified on: Thu, 30 Jul, 2020 at 9:59 AM
- From now we don't support legacy Data Tables based on connections to relational databases anymore.
- Existing Data Tables will be automatically migrated.
- Writing into database tables with the "Dataset Save" processor is also not possible anymore.
- The workflow can be migrated or the processor can be manually replaced by the "Data Table Save" processor.
- A new key-type is now available to add a connection which makes it possible to retrieve data from the respective Outlook account.
In the following all features are listed which are (partly) included in the release. If no other open parts (stories) are left, the feature is finished and otherwise it is clarified as ongoing.
|MVP of Outlook Authentication|
|Goal||A MVP for adding another key-type that can be added regularly to ONE DATA that allows you to retrieve data from the respective Outlook account.|
|Finished parts in the release||Add a new key type for O365 ROPC Authentication||After investigating multiple OAuth authentication mechanisms available with Microsoft Identity Platform we have decided to implement OAuth 2.0 Resource Owner Password Credentials grant Authentication (More details here: v2-oauth-ropc), which allows an application to sign in the user by directly handling their password. |
|Goal||Clean-up open point in the Cassandra connection topic and improve the feature.|
|Finished parts in the release||Fix visitor madness around DataSource and DatabaseTable|
- Support for legacy Data Tables based on connections to relational databases will be removed. Existing Data Tables will be automatically migrated.
- Writing into database tables with the "Dataset Save" processor is also not possible anymore. The workflow can be migrated or the processor can be manually replaced by the "Data Table Save" processor.
Did you find it helpful?
Sorry we couldn't be helpful. Help us improve this article with your feedback.