Applies on target record option in catalog ui policies not working

kalyani23
Tera Contributor

‎05-18-2022 02:00 AM

Hi,

i have create a record producer with more number of fields, and i want to hide some fields based on previous selection .I have created ui policy and since i want the same hidden fields in target record in table , i have checked the option applies on target record .in service portal ui policy working but after submission in target record it is not reflecting.

Can someone help to achieve this.

Regards, 

Kalyani

0 Helpfuls
  • 1,181 Views
3 REPLIES 3

Jaspal Singh
Mega Patron
Mega Patron

‎05-18-2022 02:04 AM

Applies on Target will be applicable for Record producers (incidents, etc.)

If it is for RITM or Catalog Tasks you need Applies to Requested Items & Applies To Catalog Tasks

0 Helpfuls

kalyani23
Tera Contributor
In response to Jaspal Singh

‎05-18-2022 02:15 AM

Hi Jaspal, i have created the record producer on a table which is extended from task table. so in that case will it not be applicable?

0 Helpfuls

Jon G1
Kilo Sage

‎12-18-2023 10:49 AM - edited ‎12-18-2023 02:50 PM

Hi Kalyani,  Did you ever find a resolution to this?  I'm having a very similar problem.

 

Edit: I've found two KB articles that may be relevant to this issue:

KB0965252 indicates that Catalog UI Policies can only interact with variables and not the parent record.  I'm not sure which fields you're trying to show/hide, but this might be related.  The KB suggests creating a UI Policy directly on the table instead of using a Catalog UI Policy.

 

The KB article that solved my problem is this: KB0863000 

I have a certain type of change request that requires the use of variables, and instead of forcing people through a record producer, I wrote a business rule that creates the variable fields on the question_answer table directly.  The problem is that the scripts on the variable set that I use for that were not applying. 

 

Based on the info in that KB article, I created a dummy record producer that links to the variable set that I'm using and I insert a record on sc_item_produced_record as that article suggests. Once I updated my script to create that record, the Catalog UI Policy and Catalog Client Script started applying as expected with the caveat mentioned above that the policies only seem to apply on the variables.