Validating a data field in a Service Portal by using a Catalog Client Script

      Use Case: When submitting a Record Producer, a date field can’t be in the past. How to accomplish this?

      We can create a Catalog Client Script.

      1) What is the trigger?

      The script will run when the date field value changed.

      2) What do we need to confirm?

      We need to check if the date provided is in the future.

      3) What if the date is not in the future?

      If the date is not in the future, then we show an error message to inform that the date cannot be in the past.

      Step by step process

      1) Create a Record Producer (RP) and define the Catalog and Category so it will be visible in a Service Portal

      2) Create a variable in your RP. In this example, the variable will have this configuration:

      Type: Date
      Question: Project Deadline
      Name: project_deadline
      Mandatory: Yes (checked)

      3) Create a Catalog Client Script in your RP to check if the project_deadline value changed. If the date is in the past, show an error message to the user.

      Your Catalog Client Script will look like this:

      Name: Validate Project Deadline
      Applies to: A Catalog Item
      UI Type: Mobile / Service Portal
      Type: onChange
      Variable name: project_deadline

      Script: 


function onChange(control, oldValue, newValue, isLoading) {

    if (isLoading || newValue == '') {
        g_form.hideFieldMsg('project_deadline', true);
        return;
    }

    //If the Project Deadline is in the past, show error message
    var deadlineDate = new Date(getDateFromFormat(newValue, g_user_date_format));
    var nowDate = new Date();

    if (nowDate.getTime() >= deadlineDate.getTime()) {

        g_form.setValue('project_deadline', '');
        g_form.showErrorBox('project_deadline', 'Project deadline should be after today', true);

    } else {

        g_form.hideFieldMsg('project_deadline', true);

    }

}


      Did you manage to test it? Are you able to submit the form if you inform a date in the past? Tell me what you got!


Thank you.

Comments

Post a Comment

Popular posts from this blog

Hacktoberfest

Image
I just completed the #ServiceNowHacktoberfest by having 4 contributions accepted! - Service Portal is a single place for everyone to access information, services and different applications. For my first contribution   (1068)  I shared a use case to get a parameter from the URL and use it into an Ajax call, recovering information from the database to show within the User Interface. - For my second pull request   (1069) I talked about best practices, explaining how to safely update a record. If we're not cautious with this kind of programming we can accidentally insert records instead of updating them. - For my third contribution   (1085)  I explained how to validate a field provided within a Catalog Item/Record Producer so that the date can't be in the past.  - The last one   (1093) was about fixing a direct reference to the Choice table. This is an internal table and it is not best practice to reference that table directly when you are crea...
Read more

VIDEO How to fix a reference to the Choice [sys_choice] table

Image
        The Choice table is used internally by the platform and depending on the payload of an operation, for performance reasons the platform can decide that it is better to drop the table and insert all the values instead of perform updates on specific records.       When we insert a new record in a table, a new sys_id is generated. If we have the Choice table as a reference to provide choices for a particular field in our table, these choices will be lost every time the platform decides to recreate the Choice table.       A simple way to avoid this problem is to create a field of  type Choice  which indirectly uses the Choice table but it is the right way, or we can create our own table to maintain the Application choices.       Recently I received the mission to do exactly this: create a private choice table for an Application.    ...
Read more

How to hide a Related List

Do you know about the Related List that displays people who can approve or reject a document? Recently a scenario came up where the developer needed to prevent the employee who created a record from approving that document. It wasn't common because usually the operational level creates the document while a manager approves it. Leaving this question of personas aside and focusing on the problem, what would be a possible solution? The first workaround that came to my mind was to hide the Approval list if the user who registered was viewing his own record. A workaround is not the ultimate solution. Just a palliative fix while we find time to think about the ideal one. The action plan 1) Every record has a field called sys_created_by; 2) On the front-end (client side) we have access to an API called Glide User that has some information about the logged in user. Among them is the name in the userName property. What if we create a ...
Read more