Date validation if date is 7 days from today

[shaik23]

Hello mates,

Below is my requirement.

Create a catalog client script that runs when the ‘Is this due to be returned at a specific date?’ field is updated.

Generate an error if the Date is not 7 days from today

for this i have created a catalog client script script given below but its not working as expected, i am missing logic can anyone please help me.

var today = new Date();
    today.setHours(0, 0, 0, 0);

    // Calculate the valid date (7 days from today)
    var validDate = new Date(today);
    validDate.setDate(today.getDate() + 7);

    // Get selected date
    var selectedDate = new Date(newValue);
    selectedDate.setHours(0, 0, 0, 0);

    // Compare the dates directly (Date vs Date)
    if (selectedDate.getTime() !== validDate.getTime()) {
        g_form.showFieldMsg('is_this_due_to_be_returned_at_a_specific_date',
            'Date must be exactly 7 days from today', 'error');
    } else {
        g_form.hideFieldMsg('is_this_due_to_be_returned_at_a_specific_date', true);
    }



}

Date format is month/date/year in our instance

[Ankur Bawiskar]

@shaik23 

why not use catalog UI policy and no scripting required.

this will handle the different date formats as well

No Code date validations through (Catalog) UI Policies 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Hi @shaik23 

You can try with a UI policy, and it is easy to do."

https://www.servicenow.com/community/developer-articles/no-code-date-validations-through-catalog-ui-...

[shaik23]

@Ankur Bawiskar @Dr Atul G- LNG  thanks will try but my client said to use client script, ui policy is best fit than client script i am not sure why they asked for client script !

[Dr Atul G- LNG]

Hi @shaik23 

If you check this link, you’ll notice that a UI Policy is 100% low-code/no-code, which means it’s easy to maintain and introduces no technical debt. So, suggest to the client that using a UI Policy would be the better approach in this case.