This is the apparently less wrong alternative to Changing the Task description into an HTML field. You create a new “u_html_description” field. You hide the out of the box “description” and you live happily ever after. Right? Not so fast! There will still be issues: Many customizations will still be required: Find and evaluate if […]

This is the last in a series of articles where I explore the possibility of adding any record to a Visual Task Board from a form, from a list context menu, and a list choice. This last one will also involve a list choice, but in this case, we will add a single card for

In previous articles, I explored the possibility of adding any record to a Visual Task Board from a form and from a list. Where do we go from here? What about selecting multiple records from a list and adding a card for each one of them? The idea We can use Personal tasks [vtb_task] as

In a previous article, I explored the possibility of adding any record to a Visual Task Board from a form. So the next obvious step is to try to do the same in the list view. Will it be possible to do that? (Spoiler alert: Yes!) The idea We can use Personal tasks [vtb_task] as

I really like Kanban-style dashboards. In ServiceNow, we have Visual Task Boards. I really love them, but I don’t like the second word in their name: Task. Why only tasks? I want to be able to add any record in the system to a freeform board. For example, I might have a list of Scripts,

In order to debug a GlideAjax Script Include, we have to trigger the code from the server side. We can run it the same way as we do with any other Script Include: using the background script. We can simply override the getParameter function defined in AbstractAjaxProcessor, so that it uses some static values instead

How many times do you write “ServiceNow” each day? Probably more than you think. 10 keystrokes every time you have to write it. Are you the kind of person who writes SN, Snow, SNow, or any weird combination that only you understand? I’m guilty of certain inconsistencies. I tend to write the full word, but

The XML import process directly inserts records into the target table. During the import the system: – Ignores any business rules that normally apply to the table. – Does not provide any opportunity to transform incoming data. – Automatically matches a reference field’s display value to the local Sys ID for some tables. If you need to validate or transform

Annotation preferences for each user are stored as user preferences with the name “glide.ui.show_annotations”. You can override that configuration and change the visibility with the following code on the client side: The user preference works at the platform level, and you might want to alter this behaviour in a particular form. This is an undocumented