JQuery not working in Service Operational workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Team,
We are using jQuery in a client script to add choices to a string-type field. However, this script is not working in Workspace.
Our setup is designed to support multiple customers. One customer requires a string field, while another needs predefined choices for the same field. To handle this, we created the following client script using jQuery to dynamically add choices. Unfortunately, it does not work as expected in Workspace.
Could you please advise on how to make this work in Workspace, or suggest an alternative approach?
Please once check the below client script and help me on this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Shaik Khasim ,
I think it will be a better idea just use:
- UI policy for the clients and configure on the SOW view workspace to hide/show the field, you can define an advanced script options
- A simple client script on change from the type field to hide/show the others field based on condition.
You really dont need a Jquery options, that is actually deprecated on the SN environment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Shaik Khasim ,
There is a check box in client script called "Isolate Script", can you please turn on.
Check below link
Please mark my answer correct and hehlpful if this works for you
Thanks,
Sarthak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Sarthak Kashyap , Thank for the response. I enabled it, but it's still not working in the workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Shaik Khasim Thats the reason SN do not recommend DOM.
DOM may work on native but it fails in many portal/workspace cases.
Workspace is quite different from native UI so it may not work.
What can be done here:
Try switching to OOB choice type field getting values from sys_choice table, I understand you might have a business requirement but this has high chances of failing.
Please mark the answer correct/helpful accordingly.
