-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into fix-glossary-term-listing
- Loading branch information
Showing
69 changed files
with
1,186 additions
and
299 deletions.
There are no files selected for viewing
Empty file.
5 changes: 5 additions & 0 deletions
5
bootstrap/sql/migrations/native/1.5.15/mysql/schemaChanges.sql
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| -- Make domain policy and role non-system | ||
| UPDATE policy_entity SET json = JSON_SET(json, '$.provider', 'user') where name = 'DomainOnlyAccessPolicy'; | ||
| UPDATE policy_entity SET json = JSON_SET(json, '$.allowDelete', true) where name = 'DomainOnlyAccessPolicy'; | ||
| UPDATE role_entity SET json = JSON_SET(json, '$.provider', 'user') where name = 'DomainOnlyAccessRole'; | ||
| UPDATE role_entity SET json = JSON_SET(json, '$.allowDelete', true) where name = 'DomainOnlyAccessRole'; |
Empty file.
5 changes: 5 additions & 0 deletions
5
bootstrap/sql/migrations/native/1.5.15/postgres/schemaChanges.sql
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| -- Make domain policy and role non-system | ||
| UPDATE policy_entity SET json = JSONB_SET(json::jsonb, '{provider}', '"user"', true) where name = 'DomainOnlyAccessPolicy'; | ||
| UPDATE policy_entity SET json = JSONB_SET(json::jsonb, '{allowDelete}', 'true', true) WHERE name = 'DomainOnlyAccessPolicy'; | ||
| UPDATE role_entity SET json = JSONB_SET(json::jsonb, '{provider}', '"user"', true) where name = 'DomainOnlyAccessRole'; | ||
| UPDATE role_entity SET json = JSONB_SET(json::jsonb, '{allowDelete}', 'true', true) WHERE name = 'DomainOnlyAccessRole'; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...etadata-docs/content/v1.6.x/connectors/dashboard/powerbi-report-server/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
44 changes: 44 additions & 0 deletions
44
...o-guides/data-governance/workflows/default-workflows/dashboard-certification.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| title: Governance Workflows - Dashboard Certification Workflow (Default) | ||
| slug: /how-to-guides/data-governance/workflows/default-workflows/dashbaord-certification | ||
| collate: true | ||
| --- | ||
|
|
||
| # Governance Workflows - Dashboard Certification Workflow (Default) | ||
|
|
||
| The **Dashboard Certification Workflow** is a periodic batch workflow designed to automatically manage the certification process for dashboards within Collate. | ||
| It is triggered periodically based on the configured scheduled, it fetches the assets based on the filters and it certifies dashbaords based on their attributes. | ||
|
|
||
| {% image src="/images/v1.6/how-to-guides/governance/workflows-table-certification" alt="dashbaord-certification" /%} | ||
|
|
||
| ## Workflow Elements | ||
|
|
||
| - **Owners and Description are not Null nor Empty** | ||
| This task checks where the dashbaord has an owner and a description | ||
|
|
||
| If either attribute is missing or empty, the workflow moves to **Don't set certification**. | ||
| Otherwise, the workflow moves to **Entity is Tier 1 or Tier 2**. | ||
|
|
||
| - **Entity is Tier 1 or Tier 2** | ||
| This task checks if the dashbaord is categorized under *Tier 1* or *Tier 2*. | ||
|
|
||
| If the dashbaord is either *Tier 1* or *Tier 2*, the workflow moves to **Entity is Tier 1**. | ||
| Otherwise, the workflow moves to **Set Bronze Certification**. | ||
|
|
||
| - **Entity is Tier 1** | ||
| This task checks if the dashbaord is specifically *Tier 1*. | ||
|
|
||
| If the dashbaord is *Tier 1*, the workflow moves to **Set Gold Certification**. | ||
| Otherwise, the workflow moves to **Set Silver Certification**. | ||
|
|
||
| - **Set No Certification** | ||
| Sets the dashbaord certification to *None*. | ||
|
|
||
| - **Set Bronze Certification** | ||
| Sets the dashbaord certification to *Bronze*. | ||
|
|
||
| - **Set Silver Certification** | ||
| Sets the dashbaord certification to *Silver*. | ||
|
|
||
| - **Set Gold Certification** | ||
| Sets the dashbaord certification to *Gold*. |
44 changes: 44 additions & 0 deletions
44
.../how-to-guides/data-governance/workflows/default-workflows/glossary-approval.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| title: Governance Workflows - Glossary Approval Workflow (Default) | ||
| slug: /how-to-guides/data-governance/workflows/default-workflows/glossary-approval | ||
| collate: true | ||
| --- | ||
|
|
||
| # Governance Workflows - Glossary Approval Workflow (Default) | ||
|
|
||
| The **Glossary Approval Workflow** is designed to define the process of updating the status of Glossary Terms within Collate. | ||
| It is triggered when a Glossary Term is created or updated and it ensures it undergoes a review process until it reaches the desired status. | ||
|
|
||
| {% image src="/images/v1.6/how-to-guides/governance/workflows-glossary-approval" alt="glossary-approval" /%} | ||
|
|
||
| ## Workflow Elements | ||
|
|
||
| - **Check if Glossary Term has Reviewers** | ||
| This task checks whether the glossary term has any reviewers assigned. | ||
|
|
||
| If no reviewers are found, the glossary term is directly marked as approved. | ||
| If reviewers are found, the workflow moves to **Check if Glossary Term is Ready to be Reviewed**. | ||
|
|
||
| - **Check if Glossary Term is Ready to be Reviewed** | ||
| This task verifies if the glossary term is ready for review based on the presence of a description. | ||
|
|
||
| If the glossary term is ready for review, the workflow moves to **Set Status to 'In Review'**. | ||
| If the glossary term is not ready, the workflow moves to **Set Status to 'Draft'**. | ||
|
|
||
| - **Set Status to 'In Review'** | ||
| If the glossary term is ready, its status is set to "In Review". | ||
|
|
||
| - **Set Status to 'Draft'** | ||
| If the glossary term is not ready for review, its status is set to "Draft". | ||
|
|
||
| - **Approval** | ||
| A user approval task where reviewers approve or reject the glossary term. | ||
|
|
||
| If the glossary term is *approved* by the reviewers, the workflow moves to **Set Status to 'Approved'**. | ||
| If the glossary term is *rejected* by the reviewers, the workflow moves to **Set Status to 'Rejected'**. | ||
|
|
||
| - **Set Status to 'Approved'** | ||
| If the glossary term is approved, its status is updated to "Approved". | ||
|
|
||
| - **Set Status to 'Rejected'** | ||
| If the glossary term is rejected, its status is updated to "Rejected". |
33 changes: 33 additions & 0 deletions
33
...ntent/v1.6.x/how-to-guides/data-governance/workflows/default-workflows/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| --- | ||
| title: Governance Workflows - Default Workflows | ||
| slug: /how-to-guides/data-governance/workflows/default-workflows | ||
| collate: true | ||
| --- | ||
|
|
||
| # Governance Workflows - Default Workflows | ||
|
|
||
| These workflows are a good starting point for different governance tasks. They should be used as they are or modified to suit your needs. | ||
|
|
||
| {%inlineCalloutContainer%} | ||
| {%inlineCallout | ||
| color="violet-70" | ||
| bold="Glossary Approval Workflow" | ||
| icon="MdMenuBook" | ||
| href="/how-to-guides/data-governance/workflows/default-workflows/glossary-approval"%} | ||
| Define how the Glossary Approval Workflow should work. | ||
| {%/inlineCallout%} | ||
| {%inlineCallout | ||
| color="violet-70" | ||
| bold="Table Certification Workflow" | ||
| icon="MdMenuBook" | ||
| href="/how-to-guides/data-governance/workflows/default-workflows/table-certification"%} | ||
| Define how to classify your Table Asset with different Certification Levels to indicate data trustworthiness and quality. | ||
| {%/inlineCallout%} | ||
| {%inlineCallout | ||
| color="violet-70" | ||
| bold="Dashboard Certification Workflow" | ||
| icon="MdMenuBook" | ||
| href="/how-to-guides/data-governance/workflows/default-workflows/dashboard-certification"%} | ||
| Define how to classify your Dashboard Asset with different Certification Levels to indicate data trustworthiness and quality. | ||
| {%/inlineCallout%} | ||
| {%/inlineCalloutContainer%} |
44 changes: 44 additions & 0 deletions
44
...ow-to-guides/data-governance/workflows/default-workflows/table-certification.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| title: Governance Workflows - Table Certification Workflow (Default) | ||
| slug: /how-to-guides/data-governance/workflows/default-workflows/table-certification | ||
| collate: true | ||
| --- | ||
|
|
||
| # Governance Workflows - Table Certification Workflow (Default) | ||
|
|
||
| The **Table Certification Workflow** is a periodic batch workflow designed to automatically manage the certification process for tables within Collate. | ||
| It is triggered periodically based on the configured scheduled, it fetches the assets based on the filters and it certifies tables based on their attributes. | ||
|
|
||
| {% image src="/images/v1.6/how-to-guides/governance/workflows-table-certification" alt="table-certification" /%} | ||
|
|
||
| ## Workflow Elements | ||
|
|
||
| - **Owners and Description are not Null nor Empty** | ||
| This task checks where the table has an owner and a description | ||
|
|
||
| If either attribute is missing or empty, the workflow moves to **Don't set certification**. | ||
| Otherwise, the workflow moves to **Entity is Tier 1 or Tier 2**. | ||
|
|
||
| - **Entity is Tier 1 or Tier 2** | ||
| This task checks if the table is categorized under *Tier 1* or *Tier 2*. | ||
|
|
||
| If the table is either *Tier 1* or *Tier 2*, the workflow moves to **Entity is Tier 1**. | ||
| Otherwise, the workflow moves to **Set Bronze Certification**. | ||
|
|
||
| - **Entity is Tier 1** | ||
| This task checks if the table is specifically *Tier 1*. | ||
|
|
||
| If the table is *Tier 1*, the workflow moves to **Set Gold Certification**. | ||
| Otherwise, the workflow moves to **Set Silver Certification**. | ||
|
|
||
| - **Set No Certification** | ||
| Sets the table certification to *None*. | ||
|
|
||
| - **Set Bronze Certification** | ||
| Sets the table certification to *Bronze*. | ||
|
|
||
| - **Set Silver Certification** | ||
| Sets the table certification to *Silver*. | ||
|
|
||
| - **Set Gold Certification** | ||
| Sets the table certification to *Gold*. |
24 changes: 24 additions & 0 deletions
24
...a-docs/content/v1.6.x/how-to-guides/data-governance/workflows/elements/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| --- | ||
| title: Governance Workflows - Elements | ||
| slug: /how-to-guides/data-governance/workflows/elements | ||
| collate: true | ||
| --- | ||
|
|
||
| # Governance Workflows - Elements | ||
|
|
||
| {%inlineCalloutContainer%} | ||
| {%inlineCallout | ||
| color="violet-70" | ||
| bold="Trigger" | ||
| icon="MdMenuBook" | ||
| href="/how-to-guides/data-governance/workflows/elements/triggers"%} | ||
| Defines what initiates a workflow (e.g., an event or a scheduled action) | ||
| {%/inlineCallout%} | ||
| {%inlineCallout | ||
| color="violet-70" | ||
| bold="Nodes" | ||
| icon="MdMenuBook" | ||
| href="/how-to-guides/data-governance/workflows/elements/nodes"%} | ||
| Represent the building blocks of a workflow. You can configure each node to specify conditions, actions or tasks. | ||
| {%/inlineCallout%} | ||
| {%/inlineCalloutContainer%} |
Oops, something went wrong.