Hi All,
I am having a requirement on catalog task form. On the form there is two editable field hostname and serial number. Serial Number auto populates when hostname is filled but if the hostname is of a new asset which is not present in pc_hardware table then the user needs to manually enter the serial number.
In manual case, we need to validate if the serial number is already present in pc_hardware table or not. If yes, we need to show the error msg with the name of asset to which the serial number is assigned and prevent saving the form.
As I am new and learning, kindly help me with the script to validate serial number and display error message.
Hi Priya,
This is possible, but will require a couple of components to make it work. Before we begin, we need to design / consider / need the following:
- A Client Callable Script Include to host a function that will perform a check to determine IF the Serial Number entered is already in the pc_hardware table or not.
- An onChange Catalog Client Script that 'does' the check for a Serial Number every time the Serial Number field changes. This Client Script should on be set to run on 'Desktop' since we don't want it on the portal, only after it is logged. We will utilise GlideAjax for this.
- (Optional) A step in a Flow / Workflow that sits behind your item to automatically create the new Serial Number / Hostname in the relevant table. This is optional, you may be happy with the manual process as is.
Some of the concepts here in terms of ServiceNow / Scripting aren't necessarily beginner concepts, so if anything doesn't make a lot of sense, please take the time to research and improve understanding as it will benefit you greatly in the long run.
Client Callable Script Include
Code Snippet:
var CMDBClientUtils = Class.create();
CMDBClientUtils.prototype = Object.extendsObject(AbstractAjaxProcessor, {
checkForSerialNumber: function () {
try {
var isError = false;
var serialNumber = this.getParameter('sysparm_serialnumber');
var grHardware = new GlideRecord('cmdb_ci_pc_hardware');
grHardware.addQuery('serial_number', serialNumber);
grHardware.setLimit(1);
grHardware.query();
// We are just going to return a simple error message if we do / dont find the
if (grHardware.next()) {
// Setting isError to TRUE to indicate that WE HAVE found a matching Serial Number.
isError = true;
return isError;
} else {
// we didn't find the serial number. You can decide what to do here, maybe you create the new pc_hardware record here instead of in the workflow / flow.
// Is error will be false here, indicating we havent found any matching serial number.
return isError;
}
} catch (ex) {
gs.error(ex);
}
},
type: 'CMDBClientUtils'
});Catalogue Client Script
Code Snippet:
function onChange(control, oldValue, newValue, isLoading) {
if (isLoading || newValue == '') {
return;
}
// GlideAjax, if you're not familiar with the concepts I suggest spending some time looking it up, its super useful.
var ga = new GlideAjax('global.CMDBClientUtils');
ga.addParam('sysparm_name', 'checkForSerialNumber');
ga.addParam('sysparm_serialnumber', g_form.getValue("serial_number"));
ga.getXML(checkSerialNumber);
}
function checkSerialNumber(response) {
var answer = response.responseXML.documentElement.getAttribute("answer");
// Remember we are returning a boolean. If TRUE then we found the Serial Number, if FALSE we didnt.
if (answer) {
// Add your own error behaviours, this just an example.
g_form.addErrorMessage('We found the Serial Number, please enter another.');
g_form.clearValue('serial_number');
} else {
// Add your own success behaviours, this is just an example.
g_form.addInfoMessage('We didnt find the Serial Number, we are all good to go.');
}
}
This should be enough to get you started and to get some validation working. There are some caveats to consider though:
- You may want to modify the GlideRecord query in the Script Include, it is just there as an example. You may have some more specific search criteria for matching with a record.
- This will not STOP someone from submitting if they have entered a Serial Number that already exists. New behaviour / client scripts are required for that.
- Carefully consider the client behaviour you want once we determine if the Serial Number exists or not, the ones in the client script I have written are just examples.
Hope this helps, let us know how you get on.
Ethan
Please mark the answer as correct if this has solved your issue, or upvote the answer if it was helpful.
