Hi,
I want the "work notes" - field to be the default view when viewing a ticket (instead of the "Additional Comments"- field showing), so it will look like this:
I found a record in the dictionary called "Work notes" on the task table, and tried setting this to default value "true". Then I get the desired result when viewing a ticket, but not when creating a new one. It then shows both the "Additional Comments" and the "Work notes"-field, and it says "true" in the "Work Notes"-field. I belive the original behavior is both of the fields showing like this, but of course not showing the "true" statement in the "Work notes"-field.
Anyone got an idea as to how I can default show the "work notes" (work notes = ticked) instead of the additional comments? It would be OK for both fields showing on a new ticket as well, but I would not want to see "true" in the work notes - field.
Thanks in advance!
Hi Ina,
Look what I found... Two user preferences that do what you want... you can make these a single field or expand them to show both. You can default to work notes too!
I just changed mine on incident and noted the changes in sys_user_preferences. If you want make those the default for people, just remove the user name and change the System field to true (checked) and insert&save the new record. It doesn't prevent people from changing it to the way they want (collapsed and comments first), but it gives you a default for noobs.
Let me know if you need more help or if that answers your question.
Sorry for the confusion Mike. Even though the user cannot set a preference, you may still be getting the value from the system's programatic value or a non-user specific value in sys_user_preference. In this image, System Administrator has his own preference saved for the annotations (off). Anyone else will get them on by default (system=true and user is empty). If neither were there they would get a value from the underlying platform code (likely true.)
What you can check is for any/all entries with the name of the preference you are looking for and see who the user is for that. You may need to remove some legacy entries to make your system entry take precedence.
Hi Mike,
When I finally got the BR to work I ran into the same problem you have.
"Any insight as to why there seems to still be a preference even though there is no record written on the sys_user_preference table? I did fix the code as you suggested..."
It's seems like the ui user preference is also set on the client-side. This means that records stored in sys_user_preference will only be used when initalizing a new user session.
I have found a solution for this. It's an ugly one.
This is what I did to the incident table:
I created a glide.ui.incident.stream_input user preference without a user and removed the others.
Then I created a client-script on the incident table with type 'onLoad':
function onLoad() {
setPreference('glide.ui.incident.stream_input', 'work_notes');
}
This will force the client-side to keep the value 'work_notes' and when ever you open a new incident form it will always have work_notes checked as default.
//Andreas
