What Happens at Runtime When You Configure a Workbook to Handle Data Conflicts

Adding Validation to an Integrated Excel Workbook 12-7

12.7 Handling Data Conflicts When Uploading Data from a Workbook

If one of your end users John makes changes to a row of data that he downloaded from a Fusion web application to an Excel workbook and another end user Jane in a different session modifies the same row in the Fusion web application after John downloads the row, John may encounter an error when he attempts to upload the modified row, as his changes conflict with those that Jane made. Depending on the configuration of your Fusion web application, John may receive RowInconsistentException type error messages. For information about how to configure your Fusion web application to protect your data, see the How to Protect Against Losing Simultaneously Updated Data section in the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. To resolve this conflict in the integrated Excel workbook, John needs to download the most recent version of data from the Fusion web application. However, invoking the ADF Table component’s Download action causes the component to refresh all data that the component hosts in the Excel workbook. This may overwrite other changes that John made that do not generate conflict error messages. To resolve this scenario, you can expose the ADF Table component’s DownloadFlaggedRows action. When invoked, this action downloads data only for the rows that the end user flags for download. Using this action, John can resolve the conflict issues and upload his modified data. Chapter 15, Using an Integrated Excel Workbook Across Multiple Web Sessions and in Disconnected Mode provides information about using an integrated Excel workbook across multiple sessions. For information about flagging rows, see Section 7.10.2, Row Flagging in an ADF Table Component. For information about invoking component actions, see Section 8.2.2, How to Invoke Component Actions in an Action Set. For more information about the components that the ADF Table component supports, see Section A.9, ADF Table Component Properties and Actions.

12.7.1 How to Configure a Workbook to Handle Data Conflicts When Uploading Data

You specify a row-specific attribute of the tree binding for the RowData.ChangeIndicatorAttribute property to determine whether a row has been modified by another user since the row was last downloaded by the ADF Table component. To configure a workbook to handle data conflicts: 1. Open the integrated Excel workbook. 2. Select the cell in the Excel worksheet that references the ADF Table component and click Edit Properties in the Oracle ADF tab to display the Edit Component: ADF Table dialog. 3. For the RowData.ChangeIndicatorAttribute property, specify the row-specific attribute of the tree binding that you use to determine whether a row has been modified by another user since the row was last downloaded by the ADF Table component in your integrated Excel workbook.

4. Click OK.

12.7.2 What Happens at Runtime When You Configure a Workbook to Handle Data Conflicts

The ADF Table component caches the original value of the row-specific attribute of the tree binding that you specified as a value for 12-8 Desktop Integration Developers Guide for Oracle Application Development Framework RowData.ChangeIndicatorAttribute when it invokes the RowDownSync action. When the ADF Table component invokes the RowUpSync action, it checks if the value of the binding hosted by the Fusion web application and the original value cached by the ADF Table component differ. If they differ, it indicates data conflict, as changes have been made to the value of the binding hosted by the Fusion web application since the ADF Table component downloaded the value of the binding. 13 Testing Your Integrated Excel Workbook 13-1 13 Testing Your Integrated Excel Workbook This chapter describes features in ADF Desktop Integration that help you test your integrated Excel workbook as you configure it. It includes the following sections: ■ Section 13.1, Introduction to Testing Your Integrated Excel Workbook ■ Section 13.2, Testing Your Fusion Web Application ■ Section 13.3, Testing Your Integrated Excel Workbook

13.1 Introduction to Testing Your Integrated Excel Workbook

Testing an integrated Excel workbook before you publish and deploy it to your end users enables you to verify that the functionality you configure behaves as you intend. Before you test your integrated Excel workbook, test the Fusion web application with which you integrate the Excel workbook. Once your Fusion web application functions as you intend, use the test mode provided by ADF Desktop Integration to test the functionality in your integrated Excel workbook.

13.2 Testing Your Fusion Web Application

Test the Fusion web application that you integrate your Excel workbook with before you start testing the integrated Excel workbook. For information about testing a Fusion web application, see the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. Verify that the Fusion web application you want to integrate an Excel workbook with, supports ADF Desktop Integration by carrying out the procedure described in Section C.1, Verifying That Your Fusion Web Application Supports ADF Desktop Integration. There are some differences between the test mode and the runtime mode when you run the integrated Excel workbook. Table 13–1 lists these differences. Table 13–1 Differences between Test mode and Runtime mode Test mode Runtime mode Does not perform tamper check Performs tamper check Does not display the connection confirmation dialog Displays the connection confirmation dialog Displays the Oracle ADF ribbon tab Does not display Oracle ADF tab Allows you to switch back to design mode Does not allow you to switch back to design mode