nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

forcing save event ?

System

I would like to know if it's possible to force a onSave event.

I am calling a CGI (cgi-callout) but I want it to be executed only if the DCR is saved with valid fields.

So far, we're first doing a IWDatacapture.save() just before calling the CGI but this only invoke the onSaveDone event so validations are not checked.

I don't know how to proceed...

Find more posts tagged with

Comments

Dwayne

Maybe I'm missing something, but why are you trying to "force" the onSave event? If what you're concerned about is invoking your CGI after validation, then why not just put an event handler for onSaveValid or onSaveDone, both of which will happen after all of the fields have been validated.

Unless what you're trying to do is to cause a save to happen without having the user press the "Save" button. On that case, then you might have to walk though each item and check its validity with item.isValid().

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

Yes I'm trying to cause save to happen without clicking the save button...

Because from a usability point of view it's awful to tell the user "you have to click the save button before you can click this one", specially since it's very easy to check if the page has to be saved or not.

The only problem is that so far, the only way I found to save the page is IWDatacapture.save().

Checking the fields one by one is crazy since we have so many different DCT Smiley Sad

Dwayne

In reply to:

Checking the fields one by one is crazy since we have so many different DCT

I understand your frustration. However, the checking logic can be done such that it's independent of the DCT. There's enough functionality in FormAPI to let you walk through each of the items on the form without knowing in advance the exact structure of the DCT. Something like this function (untested - probably lots of syntax errors)


// See if all of the fields identified by the array fieldList are valid.  Recursively checks replicants
function ValidateFields(fieldList) {
    var i;

    for(i=0;i<fieldList.length;i++) {
        // Is this field valid?  Immediately return false if not
        if(!fieldList[ i ].isValid()) {
            return false;
        }

        // Recursively check our children
        return ValidateFields(fieldList[ i ].getChildren());
}

function myCalloutHandler() {
 // some logic

 if(!ValidateFields(IWDatacapture.getRootItems()) {
    alert("Please ensure that the form is valid");
    IWDatacapture.setHighlightMode(true);
    IWDatacapture.redraw();
    return false;
 }

  // Real processing goes here
}

It might be necessary in the for loop to do a call to IWItem.getType() to see if fields are replicants before calling getChildren, and simple data types before calling isValid(). I'm not sure about that

--

Current project: TS 5.5.2/6.1 W2K