Skip to main content
C
Charles25129649qknw
Inspiring
November 29, 2022
Answered

Simplified DTG Validation Script

  • November 29, 2022
  • 2 replies
  • 21565 views

Aaaannndd... I'm back, yet again.  I've been at this months and still feel no better or more intelligent regarding scripting in Acrobat.  At this rate it will be decades before I'm even somewhat proficient -- or possibly longer. 

 

I'm still attempting to write a validation script for just a Military Time field that will error out with any incorrect input. 

This is what I've worked out thus far and now trying to figure out how to have the field reject any input that doesn't follow these guidelines -- to include anyone attempting to use a colon seperator or numbers outside a 23 hour 59 minute clock:

$('#startTimeInput').jqxDateTimeInput({
formatString : "HHMM" + timeCodeLetter .toUpperCase()
});

 

As my posts should make it clear, I have absolutely no idea what I'm doing.  When I get something to work without the expertise here, in the Navy we call this "FM" or "f*ckin' magic". while estatic, it certainly doesn't feel like I've learned anything.  Thankfully, there's no FM involved with the SME's here.  My thanks in advance for any and all assistance.

 

I've been working virtually the same script for a full DTG and plan on applying everything learned in this thread to the following script as well:

 

$('#startTimeInput').jqxDateTimeInput({
formatString : "ddHHMM" + timeCodeLetter + "mmm yyyy"  .toUpperCase()
});

FYSA:  For anyone stumbling upon this, as I've seen it discussed in many different threads, there is no 2400 or 0000 used in Military Time -- it's always a "lost" minute where all official log entries are either 2359 or 0001.

This topic has been closed for replies.
Correct answer bebarth

...and as required, here it is for only the time:

// Custom keystroke script
if (!event.willCommit) {
	var aTester=event.value.split("");
	aTester.splice(event.selStart, event.selEnd-event.selStart, event.change);
	var testeChaine=aTester.join("");
	var RegExTime=/^((((0|1)\d?)|([2][0-3]?))([0-5]\d?)?)?$/;
	event.rc=RegExTime.test(testeChaine) && testeChaine!="24" && Number(testeChaine.substr(2,1))<=5 && testeChaine!="0000";
} else {
	var RegExTime=/^(((0|1)\d)|([2][0-3]))([0-5]\d)$/;
	event.rc=event.value=="" || (RegExTime.test(event.value) && event.value!="0000");
}

// Validate script
event.rc=event.value=="" || (/^((((0|1)\d)|([2][0-3]))([0-5]\d))?$/.test(event.value) && event.value!="0000");

@+

 

2 replies

bebarth
bebarth
Adobe Expert
December 9, 2022

Hi,

You reported a malfunction for my script:

quote
.. any time the DTG (full format ddHHMM(z) mmm yyyy) has a day (dd) entry of "10", "20", or "30", the script will not allow a time entry to exceed two (2) zeroes. So only the HH can contain 00 and then it will not allow a third zero as would be required within the first nine (9) minutes after midnight to 0009 (technically 0001 through 0009 as we've previously discussed there is no 0000 or 2400 used).

And effectively, it's a case I didn't think about!

Here is a new script which will solve this mistake:

if (!event.willCommit) {
	event.change=event.change.toUpperCase();
	if ((event.value.length==6 && event.selStart==6) || (event.selStart==6 && event.selEnd>7)) event.change+=" ";
	else if ((event.value.length==10 && event.selStart==10) || (event.selStart==10 && event.selEnd>11)) event.change+=" 20";
	var aTester=event.value.split("");
	aTester.splice(event.selStart, event.selEnd-event.selStart, event.change);
	var testeChaine=aTester.join("");
	var RegExFullMiltaryDTG=/^(((0[1-9]?)|((1|2)\d?)|(3[01]?))((((0|1)\d?)|(2[0-3]?))([0-5]\d?)?([A-Z]([ ]((((J(AN?)?)|(F(EB?)?)|(M(AR?)?)|(A(PR?)?)|(M(AY?)?)|(J(UN?)?)|(J(UL?)?)|(A(UG?)?)|(S(EP?)?)|(O(CT?)?)|(N(OV?)?)|(D(EC?)?)))([ ](2(0\d{0,2})?)?)?)?)?)?)?)?$/;
	var theFullTest=RegExFullMiltaryDTG.test(testeChaine) && testeChaine.indexOf("00")!=0 && Number(testeChaine.substr(0,2))<32 && testeChaine.indexOf("24")!=2 && (testeChaine.indexOf("0000")==-1 || (testeChaine.indexOf("0000")==1 && testeChaine.indexOf("00000")==-1)) && !isNaN(Number(testeChaine.substr(0,6)));
	var dayOK=1;
	if (testeChaine.length>11) dayChecking(testeChaine);
	event.rc=theFullTest && dayOK;
} else {
	var RegExFullMiltaryDTG=/^(((0[1-9])|((1|2)\d)|(3[01]))(((0|1)\d)|(2[0-3]))([0-5]\d)[A-Z][ ]((JAN)|(FEB)|(MAR)|(APR)|(MAY)|(JUN)|(JUL)|(AUG)|(SEP)|(OCT)|(NOV)|(DEC))( 20)\d{2})?$/;
	var dayOK=1;
	if (RegExFullMiltaryDTG.test(event.value)) dayChecking(event.value);
	event.rc=dayOK;
}

You should be able to write that case correctly now.

Don't hesitate to tell me if you catch an other malfunction.

@+

    bebarth
    bebarthCorrect answer
    Adobe Expert
    December 12, 2022

    ...and as required, here it is for only the time:

    // Custom keystroke script
if (!event.willCommit) {
	var aTester=event.value.split("");
	aTester.splice(event.selStart, event.selEnd-event.selStart, event.change);
	var testeChaine=aTester.join("");
	var RegExTime=/^((((0|1)\d?)|([2][0-3]?))([0-5]\d?)?)?$/;
	event.rc=RegExTime.test(testeChaine) && testeChaine!="24" && Number(testeChaine.substr(2,1))<=5 && testeChaine!="0000";
} else {
	var RegExTime=/^(((0|1)\d)|([2][0-3]))([0-5]\d)$/;
	event.rc=event.value=="" || (RegExTime.test(event.value) && event.value!="0000");
}

// Validate script
event.rc=event.value=="" || (/^((((0|1)\d)|([2][0-3]))([0-5]\d))?$/.test(event.value) && event.value!="0000");

    @+

     

      BarlaeDC
      BarlaeDC
      Adobe Expert
      November 29, 2022

      Hi,

       

      I am not sure if this will help or not, but if I was looking to limit a field to a specific range of numbers, I would use a RegEx to achieve this, placing this in a custom script on the validation would mean that a user could not enter any value that does not pass the validation check.

       

      The code I would use is

      // I am not a regex expert and I am sure someone could simplify this down, but this is the basic of it
// ([0]{3}[1-9]) - makes sure 0000 is not allowed 
// ([0][12][0-5][0-9]) - if it does start with a 0 then it can only be a 1 or a 2 after it, followed by 0-5 and then by 0-9
//([1][0-9][0-5][0-9]) - if it starts with a 1, then it can be followed by 0-9, then 0-5, then 0-9 again.
// ([2][0-3][0-5][0-9]) - if it starts with a 2, it can only be followed by a 0,1,2,3 and then 0-5 and 0-9
var myRegExp = new RegExp("([0]{3}[1-9])|([0][12][0-5][0-9])|([1][0-9][0-5][0-9])|([2][0-3][0-5][0-9])");
event.rc = myRegExp.test ( event.value);

       I hope this helps

        C
        Charles25129649qknwAuthor
        Inspiring
        November 29, 2022

        THANK YOU!!  YOU ARE A ROCKSTAR! 🙂  It's working quite well and I will now attempt to use it as a baseline for adding the full DTG (ddHHMM(z) mmm yyyy).  I truly appreciate the assist.

        C
        Charles25129649qknwAuthor
        Inspiring
        November 29, 2022

        ...could you give me a few examples for "the full DTG (ddHHMM(z) mmm yyyy)"?

        @+


        A full Miltary DTG consists of the Day, Time, Time Zone, Month, and Year in the following format:

        ddHHMM (Time Zone) mmm yyyy and would  look like the following example (for the moment I'm typind this):

        291124Q NOV 2022 or

        291624Z NOV 2022

         

        In a DTG, the day of the month is limited to 0-31, the time is limited to 0001-2359, the time zone is limited to A-I and K-Z (J was excluded to prevent confusion with I and as some alphabets do not have one), the month is always limited to the first three (3) characters spelling the name (i.e. JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, & DEC) and always capitalized, and the year in a full DTG is always four (4) digits but can be truncated to two (2) digits for informal message traffic, memos, letters, forms, and some data collection. The two (2) digit format is less common since the Y2K issues are still in the memory of the senior Brass but as the newbies fleet up, they will forget and I'm certain it will show up more frequently outside msg traffic and log entries as time progresses. 

         

        I used the Quebec "Q" time zone as it's local EST but it would be "R" Romeo during the summer months of EDT.  The vast majority of message traffic and log entries will utilize Zulu "Z" -- second example -- with the use of a local time zone dependent on a number of unimportant factors.. 

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices