Variable editor on the Standard Ticket 'Additional Details' tab won't adhere to catalog UI policies

[Dave_H]

For reviewing requests and approvals, our customers require a view that replicates the catalog item form layout. To achieve this, I have configured the Standard Ticket tab configuration to use the Variable Editor(Read-only) on the 'Additional Details' tab instead of the Variable Summarizer.

This is good for showing the form in the correct layout however the problem I'm facing is that it does not conform to the Catalog Item UI Policies or Variable availability, it will simply show all variables unless the variable is hidden.

Is there any way to make the 'Variable Editor' (sp-variable-editor) widget conform to the same UI Policies that run when completing the catalog item form?

For instance, if I have variables A, B & C, and I have a UI policy that sets visible = false on variable B on the form (using 'Applies on a Catalog Item view' checkbox) it won't appear on the form frontend however after submission, the policy is ignored and it will appear in the summary/My Requests.

[Ankur Bawiskar]

@Dave_H 

that's correct. catalog UI policy or client script won't apply on the variable editor on ticket page.

it's OOTB behavior and you can't do much here.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Dave_H]

I guess my question is whether there is another method to allow me to achieve this? We have several catalog items where variable visibility is dependent on other variable values. UI policies allow us to present a clean form where the options are clear based on selections however all this is abandoned on the ticket page. This makes it hard to decipher for the requestor and approvers down the line.

I'd like to adopt Employee Center, however this is a major drawback in our attempt to migrate from our legacy portals.

[Ankur Bawiskar]

@Dave_H 

not possible with the variable editor on portal as it's OOTB behavior.

If my response helped please mark it correct and close the thread so that it benefits future readers.