Skip to content

Commit 205b57d

Browse files
jjoyce0510John JoyceJohn JoyceJohn Joyce
authored
docs(): Adding docs for approval workflows (datahub-project#14259)
Co-authored-by: John Joyce <john@Mac-4333.lan> Co-authored-by: John Joyce <john@Mac-4560.lan> Co-authored-by: John Joyce <john@Mac-4605.lan>
1 parent 6b64c25 commit 205b57d

File tree

8 files changed

+551
-9
lines changed

8 files changed

+551
-9
lines changed

docs-website/sidebars.js

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,9 +105,14 @@ module.exports = {
105105
],
106106
},
107107
{
108-
label: "Access Management",
108+
label: "Data Access Workflows",
109109
type: "doc",
110-
id: "docs/features/feature-guides/access-management",
110+
id: "docs/managed-datahub/workflows/access-workflows",
111+
},
112+
{
113+
label: "Data Access Roles",
114+
type: "doc",
115+
id: "docs/features/feature-guides/access-roles",
111116
},
112117
{
113118
label: "Automations",
@@ -415,7 +420,7 @@ module.exports = {
415420
},
416421
{
417422
type: "doc",
418-
id: "docs/managed-datahub/approval-workflows",
423+
id: "docs/managed-datahub/change-proposals",
419424
className: "saasOnly",
420425
},
421426
{

docs/actions/events/entity-change-event.md

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -603,3 +603,109 @@ This event is emitted when a structured property association is proposed for an
603603
}
604604
}
605605
```
606+
607+
### Approval Workflow Request Create Event
608+
609+
This event is emitted when a new approval workflow form request is submitted on DataHub.
610+
611+
Note that `parameters.fields` contains all of the form fields provided when the user originally
612+
submitted the approval request form. It contains a serialized JSON object that must be deserialized from string before accessing!
613+
614+
#### Sample Event
615+
616+
```json
617+
{
618+
"event_type": "EntityChangeEvent_v1",
619+
"event": {
620+
"entityType": "actionRequest",
621+
"entityUrn": "urn:li:actionRequest:88170f40-b4f5-4b05-a997-f5f680248b59",
622+
"category": "LIFECYCLE",
623+
"operation": "CREATE",
624+
"auditStamp": {
625+
"time": 1753829419490,
626+
"actor": "urn:li:corpuser:admin"
627+
},
628+
"version": 0,
629+
"parameters": {
630+
"actorUrn": "urn:li:corpuser:admin",
631+
"actionRequestType": "WORKFLOW_FORM_REQUEST",
632+
"workflowUrn": "urn:li:actionWorkflow:7a6e7a24-7525-4f1e-8d9b-08ba562399d0",
633+
"expiresAtMs": 1756680611743,
634+
"fields": "{\"reason\":[\"Building Tableau Dashboard Q2\"],\"privileges\":[\"SELECT\"],\"projects\":[\"Orders Dashboard Q2\"],\"tags\":[\"urn:li:tag:__default_gold\"]}",
635+
"workflowId": "7a6e7a24-7525-4f1e-8d9b-08ba562399d0"
636+
}
637+
}
638+
}
639+
```
640+
641+
### Approval Workflow Request Step Complete Event
642+
643+
This event is emitted when an approval step within a workflow request has been completed (approved, rejected, or requires more information).
644+
645+
Note that `parameters.fields` contains all of the form fields provided when the user originally
646+
submitted the approval request form. It contains a serialized JSON object that must be deserialized from string before accessing!
647+
648+
#### Sample Event
649+
650+
```json
651+
{
652+
"event_type": "EntityChangeEvent_v1",
653+
"event": {
654+
"entityType": "actionRequest",
655+
"entityUrn": "urn:li:actionRequest:ce424fff-7fab-4731-b106-fab9d69238da",
656+
"category": "LIFECYCLE",
657+
"operation": "MODIFY",
658+
"auditStamp": {
659+
"time": 1753829625133,
660+
"actor": "urn:li:corpuser:admin"
661+
},
662+
"version": 0,
663+
"parameters": {
664+
"actorUrn": "urn:li:corpuser:admin",
665+
"actionRequestType": "WORKFLOW_FORM_REQUEST",
666+
"stepId": "approval-step-2",
667+
"workflowUrn": "urn:li:actionWorkflow:7a6e7a24-7525-4f1e-8d9b-08ba562399d0",
668+
"expiresAtMs": 1754002407730,
669+
"stepResult": "ACCEPTED",
670+
"fields": "{\"reason\":[\"Test\"],\"privileges\":[\"SELECT\"],\"tags\":[\"urn:li:tag:NeedsDocumentation\"]}",
671+
"workflowId": "7a6e7a24-7525-4f1e-8d9b-08ba562399d0"
672+
}
673+
}
674+
}
675+
```
676+
677+
### Approval Workflow Request Complete Event
678+
679+
This event is emitted when an approval workflow request has been fully completed - either approved through all steps or rejected at any step.
680+
681+
Note that `parameters.fields` contains all of the form fields provided when the user originally
682+
submitted the approval request form. It contains a serialized JSON object that must be deserialized from string before accessing!
683+
684+
#### Sample Event
685+
686+
```json
687+
{
688+
"event_type": "EntityChangeEvent_v1",
689+
"event": {
690+
"entityType": "actionRequest",
691+
"entityUrn": "urn:li:actionRequest:553595ec-2295-4970-89a4-bb7d02e691c0",
692+
"category": "LIFECYCLE",
693+
"operation": "COMPLETED",
694+
"auditStamp": {
695+
"time": 1753829954539,
696+
"actor": "urn:li:corpuser:admin"
697+
},
698+
"version": 0,
699+
"parameters": {
700+
"result": "ACCEPTED",
701+
"actorUrn": "urn:li:corpuser:admin",
702+
"actionRequestType": "WORKFLOW_FORM_REQUEST",
703+
"workflowUrn": "urn:li:actionWorkflow:7a6e7a24-7525-4f1e-8d9b-08ba562399d0",
704+
"expiresAtMs": 1756335474418,
705+
"fields": "{\"reason\":[\"test\"],\"privileges\":[\"SELECT\"],\"projects\":[\"test\"],\"tags\":[\"urn:li:tag:NeedsDocumentation\"]}",
706+
"operation": "COMPLETE",
707+
"workflowId": "7a6e7a24-7525-4f1e-8d9b-08ba562399d0"
708+
}
709+
}
710+
}
711+
```

docs/automations/ai-term-suggestion.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This automation can:
1818

1919
- Automatically suggests glossary terms for tables and columns.
2020
- Goes beyond a predefined set of terms and works with your business glossary.
21-
- Generates [proposals](../managed-datahub/approval-workflows.md) for owners to review, or can automatically add terms to tables/columns.
21+
- Generates [proposals](../managed-datahub/change-proposals.md) for owners to review, or can automatically add terms to tables/columns.
2222
- Automatically adjusts to human-provided feedback and curation (coming soon).
2323

2424
## Prerequisites

docs/deploy/environment-vars.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -465,7 +465,7 @@ Reference Links:
465465

466466
Reference Links:
467467

468-
- **Access Management**: [Access Management Feature](../features/feature-guides/access-management.md)
468+
- **Access Management**: [Access Management Feature](../features/feature-guides/access-roles.md)
469469
- **Structured Properties**: [Structured Properties Overview](../features/feature-guides/properties/overview.md)
470470
- **Lineage Features**: [Data Lineage](../features/feature-guides/lineage.md), [UI Lineage Management](../features/feature-guides/ui-lineage.md)
471471
- **Compliance Forms**: [Compliance Forms Overview](../features/feature-guides/compliance-forms/overview.md)

docs/features/feature-guides/access-management.md renamed to docs/features/feature-guides/access-roles.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,20 @@ import FeatureAvailability from '@site/src/components/FeatureAvailability';
22
import Tabs from '@theme/Tabs';
33
import TabItem from '@theme/TabItem';
44

5-
# Access Management
5+
# Data Access Roles
66

77
<FeatureAvailability/>
88

9+
> **Note**: This feature is under active development and subject to significant change.
10+
911
## Introduction
1012

11-
DataHub's Access Management feature allows you to associate external roles from your source systems with your data assets in DataHub. This creates a unified view of access control across your data ecosystem, helping data consumers:
13+
DataHub's Access Roles feature allows you to ingest external roles from your source systems with your data assets in DataHub so that users can understand which roles they need in order to access a given asset.
14+
15+
Whereas [Data Access Workflows](../../managed-datahub/workflows/access-workflows.md) enable you to create workflows for requesting and reviewing access for tables, dashboards, etc, this feature enables users to understand the roles
16+
that already have access for a given asset, and redirect to an external platform to request access to the role.
17+
18+
This creates a unified view of access control across your data ecosystem, helping data consumers:
1219

1320
1. **Discover available access** - Find what roles are already provisioned for them across different data platforms
1421
2. **Request appropriate access** - Easily identify and request to join the appropriate role for the access they need

docs/managed-datahub/approval-workflows.md renamed to docs/managed-datahub/change-proposals.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
import FeatureAvailability from '@site/src/components/FeatureAvailability';
22

3-
# Change Proposals & Approval Workflows
3+
# Change Proposals
44

55
<FeatureAvailability saasOnly />
66

docs/managed-datahub/managed-datahub-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,5 +161,5 @@ Fill out
161161
162162
## More Ways to Act on Metadata
163163
164-
- [Approval Workflows](docs/managed-datahub/approval-workflows.md)
164+
- [Approval Workflows](docs/managed-datahub/change-proposals.md)
165165
- [Metadata Tests](docs/tests/metadata-tests.md) -->

0 commit comments

Comments
 (0)