Form Checks and Balances With ServiceDesk Plus – Part 2

Last time out we were adding some data verification checks to a template form in ManageEngine ServiceDesk Plus to check on the length, and hence value, of a numerical data input field for employee ID numbers. As mentioned this client also had a requirement to check on a date entry field for the delivery of a service and advise the user if the requested delivery date was realistic.   Using Field and Form Rules on a Service Request template this is quite easy to achieve. In this example the client had created a custom field on their service template, represented by the internal field name of ServiceReq_601_UDF_DATE1 (see note below). Now all we needed to create was a logic rule to test for date validity when a user entered any data into this date field. An example of the script code used is given below and is was designed to present the user with a pop-up alert message in the event that the requested date for delivery was less than 7 days from today’s date:

var req_start_date=$CS.getValue("ServiceReq_601_UDF_DATE1");
var min_del_date = new Date();


/* Calculate minimum delivery date (Today plus 7 days) */
min_del_date.setDate(min_del_date.getDate() + 7);


if(req_start_date < min_del_date)
{
    alert("Please note that New User Requests can take up to 7 days to complete. Please contact support directly to facilitate this request or select an alternative start date greater than 7 days from today.");
    $CS.stopFormSubmission();   /*stop form submission*/
} 

These articles have only scratched the surface of what is potentially possible using Field & Form Rules. We suggest you start experimenting and please feel free to share your ideas.

Enjoy!

Note: If you’re unsure of the internal field name of a custom field simply go to the ‘Field & Form’ tab of the relevant template and create a logic rule. If you select an ‘Action’ of ‘Execute Script’ in the pop-up editor you can look for the Template Field label name you used to create the field. The editor will then indicate the internal label it is using for this custom field and the default operations you can perform on this field. Check out Part 1 for a screenshot .. ;0)