Restoring transactions with ADF Taskflow

A great option of ADF taskflow in JDeveloper 11g is restoring savepoints, with this you can continu with your crashed or saved transaction. This can be handy if the user have filled in a lot of forms and he or she don't want to commit yet. The user can decide to store this session, this is called explicit save. The next time the user opens the application. He or she can restore this savepoint and returns to the right page with the right data. An another is option is to enable it for all the bounded taskflow in your application, this is called implicit save. Now the user can continu with its session after a timeout or when the user closes the browser and leaves a transaction open.
You can configure this in the adf-config. the adf-config is located in the .adf\META-INF folder of your application workfolder.

<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config" 
  xmlns:sec="http://xmlns.oracle.com/adf/security/config">
  <sec:adf-config-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
       credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
  </sec:adf-config-child>
  <adfc-controller-config xmlns="http://xmlns.oracle.com/adf/controller/config">
    <savepoint-datasource>jdbc/scottDS</savepoint-datasource>
    <savepoint-manager>DATABASE</savepoint-manager>
    <savepoint-expiration>86400</savepoint-expiration>
    <enable-implicit-savepoints>false</enable-implicit-savepoints>
  </adfc-controller-config>
</adf-config>

The open transactions can be saved on the the application server or default in a table. In my case I store these savepoints in the database see the element savepoint-manager, now I have to provide the datasource jndi name. If you make a connection in jdeveloper for example scott and then you can fill in jdbc/scottDS. JDeveloper automatically creates datasources for all your project connections.
ADF Taskflow creates now a new table called oradfcsavpt . The records looks like this.

If you use adf security then ADF Taskflow storew the transaction with the logged in username. So you can make a custom restore page where the user can see and restore his own transactions.
If you want to enable savepoint restore for the whole application then you have to use true by the enable-implicit-savepoints element. In my case is this false so I need a method to save the transaction. I will do this with a method call in ADF Taskflow.
In this example I used two taskflows, the first is an unbounded taskflow with a main view, this is a page with a department and employee overview, this taskflow also has a restore page with a simple inputtext where the user can put in the session id. This value is stored in #{pageFlowScope.savepoint} This value is used by the Save Point Restore component.

This is a picture of the main page

The main view call the second bounded taskflow where I can create a new department with a employee.

The first page is a page to create a new department, the second page is to create employees with this new department. On this page I have a commit and a save button.

The save button calls the following method #{controllerContext.currentViewPort.createSavePoint}. This creates a savepoint. The result of this method is the stored session id.

The return value is stored in the #{pageFlowScope.saveId} variable and displayed in the next page.
Now we can close the browser and open the application again. Now go the restore page, put in the session id and restore. You are now redirected to the employee page and continu the transaction.

Here you can download the example project.