Applying UI Policies to Variable Editor

ljschwaberow · ‎02-23-2015

I read the post below regarding adding a Business rule and Client script to filter out empty variables, so they won't show up under Variable Editor. UI policies on record producers should be applied on incident form variable editor. This works great if you have a free form text field. However, most of my UI policies apply to Yes/No Variables showing up under certain conditions. Such as:

If 'My Computer' is selected from a list, a 'Are you having a problem with a specific applications?' shows up with Yes/No choices. Is there any way to keep this field from showing up on the Variable Editor if say 'My Printer' is chosen in the beginning instead of 'My Computer'?

bburdick · ‎03-02-2015

Yes, basically you build an if on the "request_type" you provide.

So in my example, we have a record producer that firsts ask the user what type of issue they are having:

Then based on how they answer this question we ask them some additional questions. Most are not related at all to email. Then in the script section I have created an if for each value if they have answered Desktop, Email, Printer or Phone. And based on how they answer those questions, I populate the correct information into the work notes.

Here is a full snippet of the code that just handles that:

The final line of code basically would be the following:

current.work_notes = descriptionarray;

View solution in original post

geoffcox · ‎02-23-2015

Catalog UI Policies are designed for exactly that. Are you having trouble implementing them?

ljschwaberow · ‎02-23-2015

They work on the initial record producer form but once it's submitted all the fields that were once hidden show up under the Variable Editor on the incident form. Is there a step I'm missing?

geoffcox · ‎02-26-2015

I don't understand the phrase "the Variable Editor on the incident form".

If you mean they show up on the Incident Form itself, then you need to make UI policies for the incident form that are similar to the Catalog UI Policies used on the record producer.

If you mean they show up when trying to customize the Incident Form, then that is normal, you must be an admin and can see all the fields when trying to customize.

ljschwaberow · ‎02-26-2015

Hi Geoff,

Thanks for your assistance on this matter. I am referring to the Incident Variable Editor. I am implementing a self service version of the incident form using Record Producer. I have the Catalog UI policies in place for the Record Producer so that the appropriate fields show up when selection are made. However, once I click submit to generate an incident all those UI policies are applicable any more and all the fields show up no matter what was selected previously - does this make sense?

I thought that maybe I would have to add these UI policies to the incident form, as you mentioned, but these variables are available under UI policies for Incident. I currently have a business rule and client script in place to remove 'empty' variables but that only applies to those with free form text not multiple choice variables that have a default value. Simply put I would like these UI policies to remain in effect on the self service version of the incident form under the 'Incident Variable Editor'.