How to make all fields on the SP profile Page read only?

[Derek10]

Hi all

I've been working on the widget profile in the SP, and I have noticed some fields are read only and some are not. I would like to make them all read only but cannot tell what is driving the read only vs not? It looks like my custom fields are the ones that are being editable

I did try using UI policies set to read only but no luck.

Any suggestions?

[Aanchal Mehndi1]

Hi Derek,

Below links might be useful to you.

https://www.servicenowguru.com/scripting/business-rules-scripting/variables-form-readonly/

Re: How to build ACLs for variables in service catalog?

[Andrew Wortham · Accepted solution]

Hey Derek,

Unfortunately, I do not believe that there are any instance options that you can change here to edit the profile without taking ownership of the widget.  

However, if you do take ownership of the widget it is easy to edit the fields on the profile and whether they are editable.

You can do a search in the HTML for "editable"

Then notice that there is a property of the field that is "editable-by-user" if you set that property to false the field will always be read only for everyone.   Or you can put some logic in there.

You can also control what fields exist on the profile in the Server Script.

Hope that helps!

Best,

Andrew

[maryvanatta]

How does one make it so the user can update their profile? Under the "About" section I have   business phone, mobile phone, street, city, state and zip.     I can click on them, enter information and then save. But it doesn't ahve.

  I have a requirement that the user that is logged in can update the fields.   This is a temporary solution until they have their AD cleaned up and integration with LDAP complete.

[Andrew Wortham]

Hey Mary,

That sounds like a reasonable temporary solution.  

"How does one make it so the user can update their profile? Under the "About" section I have   business phone, mobile phone, street, city, state and zip.     I can click on them, enter information and then save. But it doesn't save."

OOB this functionality works, what exactly happens when you try to save?   Does the new information entered stay or revert back to the former info?

One possible cause for the save not going through would be an abort action business rule.

This section is based on the Service Portal view of the user table.  

If the user has read / write access to those fields they will be able to click into them and save, check business rules, ACLs, and post the exact behavior and we can see if we debug!

Best,

Andrew