
In bpm’online, you might have noticed, that often you’ll create some child record and upon saving, you’re returned to the parent page. For example, you’re looking at an account page, you click the “+” button on the case detail to add a case for the account, the case page opens to fill out the case details, and when you save you are returned to the account. This behavior makes sense, but there might be certain sections when you don’t want it to work this way. You might want the user to stay, and not return to the parent page when you save.
This behavior can be changed. To do this, we’ll override the save method on our page code. We can intercept and change the page’s config before passing it off to the base page’s save method. The setting in the config we need to change is called “isSilent” and we simply need to set this to true to not use this out of the box behavior for our page.
// override save on page save: function(config) { //modify isSilent config = Ext.apply(config || {}, { isSilent: true }); //now call the parent save method and provide config this.callParent([config]); }
That is it, now the user will no longer navigate back to the parent when the page is saved.
Hi Ryan
In relation to above. I have a process which adds an Order based on an Opportunity. The final element is that it Opens the new Order (Open Edit Page) and the user has to Save it. Currently it takes you back to the Opportunity but I want it to just save and stay on edit page (completing the process). I added your code but when clicking save it does not do anything and process remains on the Open Edit Page. Does it behave differently in a business process?