First page Back Continue Last page Graphics

Saving for Later


Saving for Later

In some applications, an end user may need to stop without completing a task, for example, when additional information is needed to answer questions. As the developer of the application, you may want to retain the current state of the task if a user leaves a page without finalizing it. You can also enable the user to complete the rest of the task at a future point, with former unsaved values restored to the page. The ability to save current application state is called save for later.

There are two general categories of saving for later:

Explicit: For example, a page contains a button that the user can click to save all the data entered so far on the page. Explicit save for later is available for both ADF unbounded and bounded task flows. For example, a user may click a button to save, but not submit, a partial expense report, and then may cancel out of the application. Later the user can invoke a list of saved expense reports and select the one to continue working on.

Implicit: For example, a user accidentally closes a browser window without saving data entered on a page, a user logs out without saving the data, or the session times out. Implicit save for later can originate only from a bounded task flow.

Save for later saves the data without enforcing validation rules or submitting it. The end user can resume working on the application later with the same data that was saved at the point when the save for later was performed.