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 ?

[Mark Manders]

What did you already try and where are you stuck? This sounds like pretty straightforward record producers, both with user criteria for visibility to the respective teams and the new one will have a default reason type (just set it from the script, don't ask for it), while the other one has a reference qualifier/client script to not show the 'vulnerable' option. 

[Ankur Bawiskar]

@Priya Singh 2 2 

you can handle the visibility using User Criteria

Create 2 user criterias and add respective ones in "Available For" related list

User criteria for Service Portal 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[yashkamde]

Hello @Priya Singh 2 2 ,

Create two read ACL's on the table and add data condition as you mentioned on the basis of Reason Type :

In the same way for other Reasonable type use another role so records will be seperated !!!
Result : USER 1 ->

USER 2 ->

If my response helped mark as helpful and accept the solution.

[Ankur Bawiskar]

@Priya Singh 2 2 

To handle the visibility of Records based on Type, you can use Table.None READ ACLs for each type and handle the visibility.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏