Make a field readonly in a business rule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2013 09:01 AM
Is there a way to make a field readonly based on roles in a business rule. I cannot locate anyting on this site or the SN wiki site.
Thank you,
Linda
- Labels:
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2013 01:20 PM
Linda, I had a quick look at your Incident from October. I think the issue there is that the page where the script wasn't firing is not an Incident form, but rather a catalog item that creates an Incident. So Incident client scripts don't apply.
Then, when the Incident is subsequently opened, the client script works because you're actually on the Incident form.
Perhaps you could use a Catalog Client Script for the catalog item? You could have it do the same thing as the one for the Incident table, but it would work on that specific catalog item:
http://wiki.servicenow.com/index.php?title=Creating_a_Catalog_Client_Script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2013 02:03 PM
That made so much sense and make the changes you suggested, but it still did not work. It is totally ignored. Just to be clear, the user does not have the opportunity to set or change the severity from the Report an Incident form (catalog item). After the incident is created, when the user accesses the self-service view they have access to the field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2013 02:41 PM
You have a client script named "Maximo - Load" that is generating a JavaScript error on the ESS view of the Incident form. It is trying to do the following:
$('incident.u_computer_name').insert(blah blah blah)
But the u_computer_name field isn't on that view of the form, so it's blowing up. Try the following instead:
var e = $('incident.u_computer_name');
if (e)
e.insert(blah blah blah)
That will check whether $('incident.u_computer_name') exists before trying to do something with it.
Caveat: there may well be other things wrong with that and other scripts on the ESS view, that was just the first one I blew up on when I had a look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2013 10:08 AM
Looks like you solved the issue. Instead of modifying the client script, we decided to add the field to the self-service form and the client scripts are working again.
I plan to reach out to the developer of the Maximo - Load client script to inform him of the issue we had.
Thank you so much for your assistance.
Linda