Data Product Workflows
Overview
To streamline the creation and management of data products within Collibra, we offer a suite of workflows designed to facilitate and accelerate your data product development process.
This package provides the following customizable workflow templates, intended as a framework:
-
Request Data Product: Initiates a request to the domain owner for a new data product, simplifying the onboarding process.
-
Data Product Request Management: Automatically activates upon user acceptance of data product ownership and guides each stakeholder through a structured, collaborative process to build and finalize the data product.
-
Request Asset Access: An adapted version of the standard Request Asset Access workflow. Enables users to add data products to their data basket for review and checkout.
-
Add port and output: Eases the creation or versioning of an outgoing Data Product Port and link it automatically to the Data Product.
-
Promote to Data Product: Allows the creation and definition of a Data Product from an existing Data Set.
Additionally, it provides a detailed configuration and deployment guide to facilitate seamless integration and operation of these workflows within your Collibra environment. This guide offers a step-by-step setup process to ensure a successful implementation.
More details
Release Notes
Fixed an NPE crash in the Data Product Request Management workflow when reviewers expanded Output Port Details panels during the Validate Build stage, which blocked Data Products from transitioning to Implemented status. Also resolved a related issue in the Build Team Instructions form where all port information (headers, asset links, and draft relations) was incorrectly rendered blank.
Compatibility
- Collibra Data Intelligence Cloud
Dependency
- Collibra API v2
License and Usage Requirements
Release History
Release Notes
New version of the Data Product workflows fixing some issues.
Compatibility
- Collibra Data Intelligence Cloud
Dependency
- Collibra API v2
License and Usage Requirements
Release Notes
Updated for 2025.10 with extra workflows and updates to existing workflows
Compatibility
- Collibra Data Intelligence Cloud
Dependency
- Collibra API v2
License and Usage Requirements
Release Notes
Includes:
- Request Data Product Workflow (v3.0)
- Data Product Request Management Workflow (V3.0)
- Request Asset Access Workflow (v2.0)
- Data Product Workflows Guide (v1.1)
Includes:
- Fixes to support Groups of users on the “Request Data Product Workflow” which was in v1.0
- Fixes to support Groups of users on the “Data Product Request Management Workflow” which was in v2.0
- Fixes the issue with the Contract to align with Asset Model of 2024.11 – Only one contract can be created per Output Port
- Fixes to the issue where Request Asset Access Output Port Access is now refined to go to Technical Steward
Compatibility
- Collibra Data Intelligence Cloud
- 2024.10
- 2024.11
Dependency
- Collibra API v2
License and Usage Requirements
Release Notes
Includes:
- Request Data Product Workflow (v1.0)
- Data Product Request Management Workflow (V2.0)
- Request Asset Access Workflow (v1.0)
- Data Product Workflows Guide
Includes:
- Fixes to support Groups of users on the “Data Product Request Management Workflow” which was in v1.0
Compatibility
- Collibra Data Intelligence Cloud
- 2024.10
- 2024.11
Dependency
- Collibra API v2
Catherine Ruef
I’ve come across multiple errors in the workflow. One being a generic “Unexpected error
Error when completing workflow task ‘Data Product Requirements’.” Upon further inspection in the log files it looks like it could be due to the inputPortId variable not being defined properly.
Additionally, in the newest release the documentation mentions that “In advanced governance use cases, you can use the child asset types Data Product Output Port and Data Product Input Port, and their relations.” which leads me to believe that using the parent asset type “Data Product Port” is the general guidance – is it even a best practice to create the input port and output port asset types automatically in these workflows?
Björn Barrefors
The first instruction in the document
“Asset Model Change – Delete the Data Contract Characteristic of “governs functioning of Data Product Output Port” max Cardinality 1. This will ensure Contracts could be connected to multiple Output Ports”
is not possible to do. Get an error saying:
“Not authorized
It is not allowed to update system resources.”
Roshan Medatwal
Thanks Bjorn, Yes we have identified that change as part of 2024.11. Also we will be releasing the workflow version shortly. The current version of workflow will only be impacted if you have a common contract across different output ports, if you do not have this scenario, the workflow will work.
If you think, it makes sense to have Common contracts across multiple output ports please raise an ideation and provide feedback for Product team.
We will shortly align the workflow to the asset model as per 2024.11 release