-
I run LotusScript code in postSaveDocument via an Agent. The only way to reliably do that is to have concurrencyMode=save (or both) on the XPage proper, or any attempt to do anything in the LS Agent results in a save conflict. What I see, however, is some of the time the LS save operation returns false, meaning failure, but I have no clue what that means. I think it’s failing attempting to save a document that has no change, but I can’t for the life of me figure out why it would be doing that.
-
And sadly the NotesDocument.save() method has never said jack about why it might fail. It is possible that could be useful information.
-
I surmise this is some wonkiness with the XSP command processor, since this code never, ever, ever did this before I wrapped it in an Agent and started calling it from a XPage, and it’s been working for years and years. It also looks like it’s only doing this when the document it’s saving has NOT been updated, which makes it all the funkier.
Any ideas? Thanks for your time…