I am using tabs (i.e. tab navigational list) when updating a row. When I update an item, and then click on a tab to go to another section of data, the item does not save the updated value when I go back to the item via tab. (I checked the session)
2. click on only available choice (Creative Services Design) in menu
3. Modal page of outstanding requisitions
4. Click the edit icon to the left of zazaza
5. Change project title
6. Click on another tab such as Delivery or Purpose and click back to Project
7. value is back to orginal value.
So, I'm think the "user design" may need to change. Instead of navigating by tabs, the user needs to update/save the data first and then navigate elsewhere. To my way of thinking, navigation implies the user is done on a page. But that's problematic. What if the user (he/she) changed his/her mind and just wants to cancel and go to a new page? So I think the user needs to commit to an action on the first page before tabbing away to another. You'd need to program it a little bit differently.
provide an additional button to submit the page and save the changes.
If you still think, you need to save on clicking the tab, you can do it.
For that, you need to create a template and submit to same page and from that page you need to redirect or branch to selected tab
Thanks for the answer. I thought it was redirecting but was not sure since I did not see it explicitly stated when you select Page instead of URL and doSubmit (or apex.submit in 4.20. I changed all the tabs to doSubmit('tab name') and it works now.
Thanks for trying to help but I don't like the idea of them pressing a button for each tab they are updating. I want it to be more intuitive, so when they are finished updating everything they then click on the save button.