7-14 Desktop Integration Developers Guide for Oracle Application Development Framework
d.
For each uploaded row, displays a status message in the Status column. For more information, see
Section 8.2.5, How to Display a Status Message While an Action Set Executes.
e.
For any row failure, it verifies the value of AbortOnFail. If AbortOnFail is set to False, it continues upload process, otherwise it stops uploading data
and invokes the commit action.
5.
While uploading data, the ADF Table component returns a success or failure code to the executing action set based on the following:
■
If the ADF Table component uploads all batches successfully, it returns the success status to the executing action set. If the end user has selected the
Download all rows after successful upload
option in Step 3, the ADF Table component then downloads all rows from the Fusion web application.
■
If the ADF Table component did not upload all batches successfully, the action set invokes the action specified by the RowActions.FailureActionID
property, if an action is specified for this property. ADF Desktop Integration returns a failure code to the action set.
If you selected On failure, continue to upload subsequent rows in the Upload Options dialog of Step 3, the Upload action returns a success code to the action set
even if some individual rows encountered validation failures.
7.8.3 What Happens at Runtime When a ReadOnly EL Expression is Evaluated During Upload
At runtime, if an ADF Table component column’s ReadOnly property evaluates to True, the ADF Table component’s Upload action ignores all changes in the column’s
cells.
It is recommended that you avoid ReadOnly EL Expressions that specifies row value binding expressions as part of the expression. If a row value binding must be used,
you must understand how the EL expression is evaluated during Upload.
Currently, all EL expression evaluation is performed on the client. Therefore, an extra round trip to the server would be needed to first evaluate a ReadOnly EL expression
containing a row value binding before the row value can be updated. In order to avoid the high cost of making an extra call to the server, ReadOnly EL expression evaluation
during upload is performed the same as during table change tracking as if the user were offline.
For more information about change tracking, see Section 7.19, Tracking Changes in an
ADF Table Component.
7.8.4 What Happens at Runtime When an Upload Fails
When the ADF Table component starts uploading data, ADF Desktop Integration creates a savepoint before initiating the upload process. In case of any failure, ADF
Desktop Integration reverts back to the same savepoint, ensuring the integrity of the server-side state of the Fusion web application.
Note: If an ADF Table component column’s ReadOnly property
evaluates to True, the ADF Table component’s Upload action ignores changes in the column’s cells.
For more information about an ADF Table component column’s properties, see
Table A–10 .
Working with ADF Desktop Integration Table-Type Components 7-15
For each row that is uploaded, ADF Desktop Integration does the following:
1.
Creates a DataControlFrame savepoint on the server.
2.
Applies row attribute value changes, and performs data validation.
3.
In case of any error, reverts back to the savepoint state. For more information about savepoints, see the Using Trees to Display Master-Detail
Objects section in the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework.
7.8.5 How to Create a Custom Upload Dialog
