Subject: This way understand it, this should be treated like Formula…
In Formula, on a button, one must save, then close, in two separate operations. XPages are the same way. By telling it to save you’ve only done half of what’s needed.
I personally put code in the data source postSaveDocument event to load a page after save, but then I wanted to run an Agent, and that appears to be the place to do that.
If you aren’t running an Agent should should be able to simply put a page load after the saveDocument and all will be well. I believe page load is a Simple Action, and if you use the Design tab for your work it should stick an actionGroup in for you.
The page it goes to after save is defined on the XPage tab of the XPage properties. By default it says Same Page, but it can be changed. That’s probably the best practice place to define which page to go to.However, XPages offers much greater flexibility that that. See my blog post on navigation in XPages -