- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â11-02-2018 10:02 AM
I created an item for my portal and have populated it with the variables I need to collect data from users. However, when I created a UI policy to show/hide variables based on other field values I found that I could not locate the variables in the UI Policy Actions screen. I see the fields for the Catalog Item [sc_cat_item] table but can't seem to locate a node representing the variables or the variables themselves. Do I have to use a script for this instead of a UI Policy Action (as I would if this were an application and not in the portal)?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â11-02-2018 10:27 AM
Shortly after posting this I looked at an existing OOB portal example and realized that I can do this by creating a Catalog UI Policy. This allowed me to tell SN that the "Applies To" is a variable or variable set, rather than a table. From there I was able to proceed with creating the policy as I expected, including using the UI Policy Actions and negating the need for scripting. My mistake was creating the Policy directly from the form.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â11-02-2018 10:05 AM
If you're talking about dealing with variables on the 'sc_req_item' or 'sc_task' form (even if it's being displayed in the service portal), you need to use client scripts to deal with them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â11-02-2018 10:27 AM
Shortly after posting this I looked at an existing OOB portal example and realized that I can do this by creating a Catalog UI Policy. This allowed me to tell SN that the "Applies To" is a variable or variable set, rather than a table. From there I was able to proceed with creating the policy as I expected, including using the UI Policy Actions and negating the need for scripting. My mistake was creating the Policy directly from the form.