Maker checker workflow for creating data flows in waltz

[jain-shreyans-db]

Description

Ability in waltz to govern the creation of data flows.

Currently, the process is generic where in you can either have a involvement or a custom role setup to create data flows (logical / physical). This does not provide any ability to govern creation of such flows from the perspective of that application, actor, or euda and their respective involved users. With this new feature, we expect that a user involved with some permissions for the said app, actor, or euda will be able to approve or reject a 'proposed' data flow.

If approved -> the flow actually gets created. If rejected the proposal gets rejected, and returned to the user.

(further details will be added)

Resourcing

We intend to contribute this feature