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; } } }

TS6.7.1 SP1 IWDatacapture.save() generate incomplete form

lanpham

Hi,

We just upgraded our dev to TS6.7.1 SP1 and we ran into a problem with FormAPI. The thing is in our DCT, we use a custom button to save the DCR. Basically the button just fire off an event that calls the IWDatacapture.save() function.

The problem is that when we call the IWDatacapture.save(), it causes the dcr to become invalid even though all fields are entered on the form. It has "Incomplete form" appendded to the dcr filename in the GUI and also added an extended attribute "iw_form_valid"=false in to the dcr. This prevents any function to be perform on the dcr:you cannot progress a job with the dcr attached, you can not generate files with that dcr, you can not submit...etc.

Have anyone encounter this problem when upgraded to 6.7.1 SP1?
I was able to easily reproduce the problem with a simple DCT.

We upgraded from TS6.5.0 SP3 to TS 6.7.1 SP1
Run on Windows 2000
Using DCT version 5.0dtd and 6.0dtd

Attached is a simple test DCR. To reproduce the issue, you have to first create a DCR by saving it using the builtin "Finish" button. And then try to edit it then click on the "Save DCR" button. You will notice that the DCR will become invalid. Well at least that how it happens on my server.

Find more posts tagged with

Comments

lanpham

Can someone with TS 6.7.1 SP1 try to reproduce the above issue for me? I need to know if this is my server issue or a bug. Thanks,

JulienLord

We've been running into this too since we switched over to 6.7.1.

After some digging, the problem looks like it stems from using IWDatacapture.save(); Here's a snippet from dcapi_datacapture.js:

[html]
// The save sequence is complex:

// 1. Normally, the user clicks a save button ('Save', 'Save As',
// 'Save & Close'), and we fire the 'onSave' event.
// -> (onSave(button))

// 2. Then we validate, and fire 'onSaveValid' event.
// [VALIDATE] -> (onSaveValid)

// 3. If we don't have a name (because they clicked 'SaveAs' or
// because setDCRName("") was called, we present a browser and
// fire the 'onSaveNameSpecifed' event.
// -> (onSaveNameSpecified)

// 4. Finally, we save, and fire the 'onSaveDone' event.
// [SAVE] -> (onSaveDone)

// When IWDatacapture.save() is called, we jump to step 4 of
// the flow, and only save if we have a name to save to.
[/html]

Skipping validation means the method actually lets you save incomplete forms. I think their might be a bug because even valid forms could come up as incomplete sometimes. I've found a little workaround that seems to be working here, at least for now:

replace
IWDatacapture.save() with parent.datacapture_buttonframe.doSave()

In essence, you replace the object call with the actual call TS makes when you click one of the save buttons. It's not completely tested yet, so you might want to test it out first.

lanpham

Thank you for your response.

I contacted support and they did confirmed that it is indeed a bug in the IWDatacapture.save() FormAPI introduced in SP1. I will try your suggestion out to see if it work.

Thanks,

Resh_Bab

Hi -

I have run into this problem as well. Is there a workaround for this bug? I have formAPI code to setDCRName and when I do IWDatacapture.save(), the form saves as incomplete one. Any help is appreciated.

Thanks,
Resh

lanpham

The workaround i use is from JulienLord's suggestion.

Using parent.datacapture_buttonframe.doSave()

instead of IWDatacapture.save().

Or if you like to save the incomplete form...try this.

var a = new Array() ;
var b = new Array() ;
if(top._dcWin.datacapture.isFormValid( a , b ))
{
parent.datacapture_buttonframe.doSave();
}
else
{
IWDatacapture.save() ;
}

....if the form is valid....parent.datacapture_buttonframe.doSave() will remove the incomplete_form status.

gzevin

Thank you for your response.

I contacted support and they did confirmed that it is indeed a bug in the IWDatacapture.save() FormAPI introduced in SP1. I will try your suggestion out to see if it work.

Thanks,

ah, Ok.. as usual, a new feature comes with a bug. good to know, which one it was Smiley Happy

background image.jpg

aravindmath

i have an "IWDatacapture.save()" in a "OnSave" handler function .
which is creating an incomplete form.

when i replace "IWDatacapture.save()" with "parent.datacapture_buttonframe.doSave()" as suggested in the previous post .
its invoking the same save handler function which is resulting in a recursive loop infinitely.

Can you help me in finding out how "incomplete form" problem can be solved if "iwdatacapture.save()" is inside a save handler function.

bakground image.docx

Adam Stoller

i have an "IWDatacapture.save()" in a "OnSave" handler function .
which is creating an incomplete form.

when i replace "IWDatacapture.save()" with "parent.datacapture_buttonframe.doSave()" as suggested in the previous post .
its invoking the same save handler function which is resulting in a recursive loop infinitely.

Can you help me in finding out how "incomplete form" problem can be solved if "iwdatacapture.save()" is inside a save handler function.

Anyone have any updates on this?
I'm running into it on my current project - and as per the above, when I tried to substitute the standard IWDatacapture.save() with parent.datacapture_buttonframe.doSave() my browser basically when into an endless loop (fortunately I was able to cancel out of it gracefully).

Are there more details / specifics about how to use doSave()?
Does anyone know what triggers the problem in the first place? -- I have to assume that there's something that triggers it or else there would be a lot more threads/posts on this subject.

Adam Stoller

Anyone have any updates on this?
I'm running into it on my current project - and as per the above, when I tried to substitute the standard IWDatacapture.save() with parent.datacapture_buttonframe.doSave() my browser basically when into an endless loop (fortunately I was able to cancel out of it gracefully).

Are there more details / specifics about how to use doSave()?
Does anyone know what triggers the problem in the first place? -- I have to assume that there's something that triggers it or else there would be a lot more threads/posts on this subject.

FYI - my issue is now (I believe) resolved (to be verified on customer's server tomorrow morning) with the assistance of Support.

It was a case of:

untitled.JPG

msrinivas

I ran into the same issue over the weekend. I knew that my code worked fine from a previous project (TS 6.5 sp2) but did not in TS 6.7.1 SP1. After pulling my hair for a few hours and wasting my Sunday morning I found that Patch 73875 for TeamSite 6.7.1 SP1 for Windows fixes this issue.

This was one of the "features" introduced because of the incomplete DCR feature.

HTH