hide catalog variables from reports

[tbisca]

We have numerous catalog items where potentially personal identification information could be entered. We want to hide these fields not only from the request item (sc_item_req) and task (sc_task) in the variables section but we also want to prevent them from being reported on or read except for people with a specific role.

Initially, we want the field visible so that data can be entered in. I know that within the workflow you can designate which fields are visible in the variables section but we are trying to prevent people from scanning the variable sections and finding the personal information.

For example, I have a field call PIN that is entered by the individual on the catalog item. Once the request item/catalog task is created, only people with the PINAccess role should see it. If someone without PINAccess role looks at a request Item/catalog task, they would not see it while those who have the role can. We also want to prevent a person without the PINAccess role from getting access to it via reporting.

I tried using an ACL with mixed results but maybe I'm doing it wrong. I tried limiting the sc_item_option_mtom, dependent item where dependent item.question contains PIN. The script

is answer = false;, but this seemed to lock out the entire table not just for PIN. This did not hide it on the variables section of any of the items.

Appreciate any help/thoughts/suggestions.

Thanks, Tim Bisca

[Chris M_]

I don't have a complete answer to this, but I may be able to get you far enough along to make your ACL qork as expected...

When you dot-walked to dependent item.question, what you were actually looking at is the question field on the options table (sc_item_option.item_option_new).   While this field's display value is the text of the question on your form, the field is a reference field pointing to the variable table (item_option_new).   The actual text of the question is variable.question (item_option_new.question_text).

In my case, when I have to filter in certain values in a database view, I got the sys_id's of the questions I needed and used the schema sc_item_option.item_option_new = [item_option_new.sys_id] for each question I wanted to include.

[rohitservicenow]

Hi Tim, 

Have you had a luck hiding the variables from reports?

[lana5]

Hello, same question to you, have you had any luck hiding variables from reports?