How to add User criteria on 'std_change_proposal' table

[Mounika Tungala]

Hi All,

This is an urgent requirement to implement. Can anyone help me to fix this issue, please!!

OOB User criteria is not available on 'std_change_proposal' table and we are not even able to add it from the related list. Is there any way to add User criteria i,e Available for, Not available For on the 'std_change_proposal table'?

[Patrick Laroch1]

What is the end goal?

To limit the users that can use the "Propose a new Standard Change Template" catalog item?

[Mounika Tungala]

Hi @Patrick Laroch1 ,

Thank you for your continued support on this question. My Primary goal is to bring user criteria to the proposal form. if this is not possible then I need to manage the user criteria with scripting.
Ex: Assume I created one field on the proposal table that references to sys_user_group table. So when the user selects a particular group in that custom field, user criteria should be created with the group field mapping. Will something like this work?
So that whoever creates these proposals can put the restrictions even before the proposal goes for change control team approval. 

[Patrick Laroch1 · Accepted solution]

Ok, I think I understand better. To confirm, you wish for the individual proposing a new Standard Change to be able to identify for who the Catalog Item will be available for.

If that is correct, you will need to account for the versioning. So I would probably:

1. add 2 custom List fields to the Proposal referenciong the User Criteria table "Available for" and "Not Available for".

2. Create a Flow (or BR) on the std_change_record_producer table to run on Change to the current_version field to update the related lists.

[Mounika Tungala]

Hi @Patrick Laroch1 ,

I have created two custom relationships on the proposal table which reference to 'Available', 'Not Available for'.

1. It is giving me the list of all the catalog items and respective user criteria. Not able keep any condition to not to show all (attached the screenshot)

2. I am trying to add user criteria to the proposal table before approval. Normally what happens after the approval only the template record gets created in the 'std_change_record_producer' table. So how will I get the sys_id/version of the respective template record to map the user criteria?

[Patrick Laroch1]

you need 2 new fields, not relationships. The fields are reference fields to the user criteria table.

You will need to dotwalk from to std_change_record_producer' table.current_version.std_change_proposal.u_available_for