Why can't I access the ability to suggest or review lookup values to ensure governance of reference data in your organization.

Question

We want to allow the user id ‘user.test@email.com’ to make the suggestion for the lookup value change. 

Answer

There are two roles available when the workflow functionality is enabled on your tenant:

ROLE_RDM_SUGGEST (Suggester) - Users with this role can add, edit, or delete lookup values but the changes are not committed. The changes are committed only when an approver approves the changes.

ROLE_RDM_REVIEW (Approver) - Users with this role receive an email notification when changes are made to lookup values. They then review the changes made to lookup values by multiple users and approve or reject changes as required.

Step 1. Register RDM tenant on Workflow service

POST: {{workflow_service}}/workflow-adapter/workflow/registrations
HEADER:
EnvironmentURL: {{RDM_service}}
BODY:
{
"tenantIds": [
"{{rdm_tenant}}"
]
}

Step 2. Configure user permissions (to be performed by customer admin themselves).

1. Set role ROLE_RDM_SUGGEST for the user who should have permission to suggest changes
2. Set role ROLE_RDM_REVIEW for the user who should have permission to review and approve changes

 "ROLE_RDM_SUGGEST": [
 "awjqDWcFZdjvDeg"
            ],
 "ROLE_RDM_REVIEW": [
 "awjqDWcFZdjvDeg"
            ],

Important note: Workflow service uses a cache to keep auth permissions. New roles aren’t applied immediately (it can take up to 1 hour)

Step 3. Enable the “workflow“ feature for RDM tenant by the config service

1. Get RDM Tenant property from the Config service

   GET: {{config_service}}/service/rdm?environment={{environment}}&tenant={{rdm_tenant}}

    

2. If RDM tenant has property, add "workflow": true into the list of features

   PUT: {{config_service}}/service/rdm?environment={{environment}}&tenant={{rdm_tenant}}
   {
   ...
   "features": {
   ...
   "workflow": true
   }
   }

1. If RDM has no configuration (returns "message": "Configuration for ... not found"), you should create a new one based on the configuration for the environment.

3.1. Get default configuration

GET: {{config_service}}/service/rdm?environment={{environment}}

3.2. Create new RDM tenant configuration

POST: {{config_service}}/service/rdm?environment={{environment}}&tenant={{rdm_tenant}}
{
...
"features": {
...
"workflow": true
...
}
}