onSaveDone event - save not done?

TeamSite 6.7.1
Windows 2003

After a DCR is saved I want to go into the DCR and change a value based on the auto generated filename for the DCR.

I believe I can fix this problem using the onSaveNameSpecified, but want to post this info anyways as it cause Many problems.

Is it possible that the onSaveDone event is getting called before the DCR is actually done saving?

My onSaveValid event does a sever callout to a cgi script that reads the values in the DCR and changes 2 under certain circumstances. This works about 9 out of 10 times. The other time the DCR seems to get overwritten after my server callout is done.

I believe that sometimes my code runs so fast that TeamSite is finishing saving the original value back to the DCR after the server callout is done.

My other evidence for this is from this post:

http://devnet.interwoven.com/forums_vb/showthread.php?t=15006&forumid=13

The user in the above post claims that onSaveDone they would change values in the DCR using FormAPI and 9 out of 10 times these changes would be included in the save.

Can you use FormAPI to change values in a DCR in the onSaveDone event and expect them to be included in the save? Isn't it too late then unless you specifically tell FormAPI to resave the doc after the changes?

Has anyone else had experiences with this? Am I completely off base here?

Griff

Find more posts tagged with

Comments

Sailesh

OnSaveDone is called after the dcr gets its name and dcr gets saved in the data folder.

So changes to dcr after that would not be saved.

kaalraa

Is it possible that the onSaveDone event is getting called before the DCR is actually done saving?

The system has all the information necessary to save the form, and the data has passed validation by FormsPublisher and by any custom user script function. When the save completes, one final event, onSaveDone, is triggered.

Can you use FormAPI to change values in a DCR in the onSaveDone event and expect them to be included in the save? Isn't it too late then unless you specifically tell FormAPI to resave the doc after the changes? Has anyone else had experiences with this? Am I completely off base here?
Griff

Using FormAPI, one can change the values within the DCR using any external script or so. However, you are changing the DCR values not the values being put in the DCT. Once you change the values you can just submit your DCR.. again. I hope you got what you are looking for.

ISCBorisB

Griff, you seem to get confusing replies because of the ambiguous question.

"After a DCR is saved I want to go into the DCR and change a value based on the auto generated filename for the DCR"

What does it mean? Do you want to modify DCR Form, saved DCR File or both? Those are all different scenarios, some of them imply that the Form
and the File are out of synch right after successful "Save" which may or may not be a good idea

GriffTheDog

Thanks Kaalraa!

You solved the problem.

On certain pages where the callout is ran, if the user previewed and then clicked save the save would over write the callout that ran on the preview click.