Kingston Service Catalog form Issues and How to Workaround them

[mohankrishna1]

Starting with Kingston, Service Catalog was introduced with a newer version of “g_form.” Due to this new version of g_form, you may face some unexpected challenges when using catalog forms on an instance running on Kingston.

Here are some known issues caused by new g_form:

1. Checkbox variable in variable editor on sc_task form throws Uncaught TypeError: Cannot read property...
2. Catalog task cannot be saved or closed because mandatory fields checks fails.
3. Mandatory variables are not becoming not mandatory when using UI Policies. This causes issues when t...
4. After upgrading to Kingston, setting a variable to non-mandatory and hidden on forms is not honored
5. List collector variables with a mandatory UI Policy on a catalog item do not load on the submitted R...
6. Kingston Issue: Not able to update the RITM/Task tickets even after providing the value in mandatory...
7. Issue with non-visible mandatory variables
8. Clearing the value of a reference variable via g_form.clearValue does not allow it to pass validatio...

How to workaround g_form issues on Kingston:

If you are experiencing one of the issues above, you can fallback to a previous version g_form to stop seeing the issue.

How to revert g_form to an older version:

• In the Application Navigator type sys_properties.list 

• Click New

• Create a new system property with these values: 
  Name: glide.sc.use_sc_form_v2 
  Type: true|false 
  Value: false
  Click Save

• In the Application Navigator perform cache.do