The formal study of semantics intersects with many other fields of inquiry, including lexicology, syntax, pragmatics, etymology and others. Independently, semantics is also a well-defined field in its own right, often with synthetic properties. In the philosophy of language, semantics and reference are closely connected. Further related fields include philology, communication, and semiotics. The formal study of semantics can therefore be manifold and complex.
Semantics contrasts with syntax, the study of the combinatorics of units of a language (without reference to their meaning), and pragmatics, the study of the relationships between the symbols of a language, their meaning, and the users of the language. Semantics as a field of study also has significant ties to various representational theories of meaning including truth theories of meaning, coherence theories of meaning, and correspondence theories of meaning. Each of these is related to the general philosophical study of reality and the representation of meaning.
Here’s a quick one: I was asked to replace the “Legacy CI Relations” form element with the new “CI Relations” element on all CI forms. I didn’t want to have to order a new mouse afterwards, so I came up with a quicker way.
First, navigate to sys_ui_element. To identify all occurences of Legacy CI Relations, I used this query:
Note: The display value of the sys_ui_formatter field is “Legacy CI Relations”.
Next and last step: Change the values of element and sys_ui_formatter as follows:
element = "ui_ng_relation_formatter.xml";
sys_ui_formatter = "b62309137f32310009fedf92bdfa912b"; // "CI Relations"
You might not see the change on forms immediately, as there is some caching involved. However, if you’ve not tampered with any other values on the UI element records, the Legacy Element should be replaced with the New UI on all forms. Good luck.
Field styles are a complicated mechanism. The system has to check if a value in a column equals the value defined in the style record. So many things can go wrong here, right? Well…actually, yes. It’s so complicated that ServiceNow has given up fixing it, as per some Knowledge Base articles.
Here’s one example I recently encountered when trying to apply styles to a Boolean field. The requirements were to apply the style to a List and a report, specifically a Calendar report.
