Record Producr on Policy Exception Table

[Priya Singh 2 2]

Hello Team,

We have a requirement to create a new Record Producer that will generate records in the Policy Exception table. This new Record Producer will be managed by a different team. Although a Record Producer already exists for the same table and is maintained by another team, we need both producers to operate independently without any functional conflict.

The key differentiator between the two Record Producers will be the Reason Type (choice field).

• The new Record Producer will set the Reason Type to “Vulnerable”.
• The existing Record Producer will continue using the other available Reason Types.

This approach ensures that each team can manage its respective requests separately, while both producers continue to create records in the same table without overlapping responsibilities.                                                           

How we can make visibility/access for this requirement for these 2 teams ?

[Priya Singh 2 2]

Problem is not visibility of Record Producer on Portal, problem is this when record gets created : For ex if it gets created  through "x" it will create Policy Exception Record though x Producer and "a" team will handle or having required access to this which is already setup like this but I created "y" Record Producer and it will also create a record under Policy Exception table but another team "b" will handle it they should have required role to work on it without interrupting team  a record, how I can handle these things that I want to know, I am trying to modify ACLs by putting data condition Reason is this or for my new I am trying to put data condition reason is Vulnerable but it's not working 

[Priya Singh 2 2]

I see this acl is controlling read access, I added condition here to identify data (Existing ACL)

And I created this one and added newly created role to this acl, but it is not allowing read access to the users who are part of this role