Working with ADF Desktop Integration Table-Type Components 7-17
For more information about ADF Table component properties, see Section A.9,
ADF Table Component Properties and Actions.
4. Click OK.
5.
Open the integrated Excel workbook.
6.
Open the Action Collection Editor to configure an action set for the Oracle ADF component, ribbon control, or worksheet event that the end user uses to invoke
the action set at runtime.
7.
Add the ADF Table component’s DeleteFlaggedRows action to the list of actions that the action set invokes at runtime.
For more information about invoking action sets, see Section 8.2, Using Action
Sets.
8. Click OK.
7.9.2 What Happens at Runtime When an ADF Table Component Deletes Rows in a Fusion Web Application
The end user flags rows to delete, as described in Section 7.10.2, Row Flagging in an
ADF Table Component. The end user then invokes the action set. The following
sequence of events occurs:
1.
If specified, the action binding referenced by the BatchOptions.StartBatchActionID property is invoked.
Failures from this step are treated as errors. An error stops the action set invoking. It also returns the error condition to the action set. If an action binding is specified
for the ActionSet.FailureActionID property, the action set invokes the specified action binding.
For more information about configuring batch options, see Section 7.10, Batch
Processing in an ADF Table Component.
2.
The action set invokes the Delete action binding specified by RowActions.DeleteRowActionID.
3.
If no errors occur during the invocation of the Delete action binding, a success message entry appears in the _ADF_StatusColumn column. If a failure occurs,
the ADF Table component stops invocation of the Delete action binding and continues to Step 4.
4.
If an action binding is specified for the BatchOptions.CommitBatchActionID property, the action set invokes it. If this step fails, the action set stops processing
batches. If no failures occur, the action set processes the next batch by invoking the DeleteRowEnabled
True to enable the ADF Table component to delete rows in the Fusion web application.
False is the default value.
Note: Rows inserted since the last invocation of the ADF Table
component’s Download action but not uploaded to the Fusion web application are ignored even if flagged for deletion.
Table 7–7 Cont. RowActions properties of ADF Table component
Set this property... To...
7-18 Desktop Integration Developers Guide for Oracle Application Development Framework
action binding specified by the BatchOptions.StartBatchActionID property, and so on until the action set processes all batches.
5.
If the action set processes all batches successfully, it invokes the action binding specified by its ActionOptions.SuccessActionID property if an action
binding is specified for this property. It then removes the rows deleted in the Fusion web application by invocation of the Delete action binding specified by
RowActions.DeleteRowActionID from the worksheet and returns a success code to the action set.
If failures occur while the action set processes the batches, the action set invokes the action binding specified by its ActionOptions.FailureActionID
property if an action binding is specified for this property. This action binding returns a failure code to the action set.
6.
If an unexpected exception occurs while the action set invokes its actions, an error code is returned to the action set. All row level errors are displayed in the Status
column, and all batch level errors can be tracked through Table.errors. For more information about error handling, see
Section 12.4, Error Reporting in an Integrated Excel Workbook.
7.10 Batch Processing in an ADF Table Component
The ADF Table component uploads modified rows from the Excel workbook in batches rather than row-by-row. You can configure batch option properties that
determine the size of batches and what actions the ADF Table component invokes when it uploads a batch.
Note that end users might encounter unexpected reports of errors under certain circumstances while uploading data from ADF Table components. After posting
changes from a batch, ADF Desktop Integration runs the action specified by the CommitBatchActionID. Errors that occur during the commit action might continue
to be reported on subsequent batch commit actions, even though those batches of records do not contain the error. This happens when any pending model updates that
exist when the CommitBatchActionID gets called are not automatically reverted when commit fails.
To avoid any such error, you must create a custom action for the CommitBatchActionID that first attempts to commit the pending model changes.
However, if an exception occurs during commit, the custom method should first rollback the pending model changes, so that any subsequent batch commit attempts
can succeed.
7.10.1 Configuring Batch Options for an ADF Table Component
The ADF Table component has a group of properties BatchOptions that allow you to configure how the ADF Table component manages batches of rows. Information
about these properties can be found in Section A.9, ADF Table Component Properties
and Actions.
To configure batch options for an ADF Table component: 1.
Open the integrated Excel workbook.
Note: It is important that the commit exception gets thrown again
after rollback so that the commit errors are reported, as expected on the client.
