Hi Debabrata,
It is possible to give the suggesting permission to one entity type and not other entities. You will need to use metadata security to achieve this.
Here is one example for your reference.
Organization
Contact
As you can see from above snapshots, in my sandbox, the user I have logged in with have Suggesting permission on Organization profile, But in Contact profile the user have EDIT permission only.
If this is the use case that you are trying to implement, then it can be done in the following way using metadata security. I have followed the below approach:
- Created a custom role from the user management console.
- Assigned READ, CREATE,UPDATE permission to the custom role for the CONTACT entity type in metadata security.
- Assigned READ, INITIATE_CHANGE_REQUEST permission to the custom role for the Organization entity type in metadata security.
- Assigned the custom role to the user from user management console along with other relevant roles like ROLE_API, ROLE_USER etc.
Here is a screenshot of the metadata security which I have used
Let me know if this solves your first use case.
------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal
------------------------------
Original Message:
Sent: 01-12-2024 05:26
From: Debabrata Sarkar
Subject: Workflow Suggesting Option visibility
Hi Team,
As per my understanding in Reltio we are showing 'Suggesting' option in the gobal dropdown list to invoke the DCR workflow. And it is directly depends on the role.
Now I have two questions regarding this-
- If I have multiple entities(tables), and I want to invoke the DCR WF for only one entity (not all), then how can it be done?
- What is the way to invoke a DCR for bulk update? (I dont see any 'Suggesting' option on entity level)
Appreciate if anyone can help.
Thanks,
Debabrata
------------------------------
Debabrata Sarkar
EPAM Systems
------------------------------