Reference qualifier behavior in RITM form

[SouvickA]

Hello All,

I need to clarify a configuration on Service catalog.

Variable (A) is showing drop down options from reference qualifier and based on selection another variable (B) shows choices. The configuration works good while the catalog is on portal. After submitting, we have kept the variables editable on the respective RITM. But the issue on this RITM level for the submitted item, the variable A is not showing all the correct options and same for variable B.

Please share any knowledge on this configuration.

Regards,

Souvick

[Nawal Singh]

Hi @SouvickA ,

Could you please share the reference qualifier logic? That might help us identify the issue more effectively.

Thank you!

[SouvickA]

The reference qualifier logic is like javascript:"u_catalog_item="Sys_id"^u_type=variable A ^u_parent=" + current.variables.variable B ;

[Nawal Singh]

Hi @SouvickA ,

In order to validate the root cause can you please do one thing- instead of RQ set some default value and submit and check like- variable is still picking wrong value or correct one.

If the value is correct then RQ is causing the issue and if still facing the same issue then other need to validate.

Hope that will help!!

If you found my response helpful, please mark it as helpful and accept it as the solution.

Thank you
Nawal Singh

[Ankur Bawiskar]

@SouvickA 

it worked for me in RITM

Ref qualifier on Portal

After submitting I selected another Location and it showed Users from that location so it correctly applied filter

Variable config

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

[Nilesh Pol]

@SouvickA 

Here's a breakdown of potential causes and solutions:

1. Reference Qualifier Configuration: Ensure that the reference qualifier for Variable A is correctly configured to display the appropriate options. Sometimes, the reference qualifier might be context-sensitive, meaning it works differently on the portal versus the RITM form. Verify that the qualifier logic is applicable in both contexts.

2. Catalog Client Scripts: If you have any client scripts that manipulate the options for Variable A or B, ensure that they are designed to run on both the catalog form and the RITM form. Catalog client scripts may not automatically apply to the RITM form unless explicitly configured to do so.

3. UI Policies: Check if there are any UI policies affecting the visibility or options of these variables on the RITM form. UI policies can behave differently in the catalog versus the RITM, so ensure they are correctly set up to apply in both scenarios.

4. Variable Attributes: Review the attributes of the variables to ensure they are set to be editable and visible on the RITM form. Sometimes, attributes might restrict visibility or editability after submission.

Please share the snaps so that will find core.