B Oracle ADF Desktop Integration EL Expressions

B.1 Guidelines for Creating EL Expressions

The following list describes the characteristics that EL expressions for your integrated Excel workbook can have and provides recommendations for writing EL expressions:

• Literal values that evaluate correctly to the type expected for the Oracle ADF component property. The following list describes some examples:

  • Boolean values true and false

  • Integer values such as -1, 0, and 100

  • String values such as hello world

• Strings that contain one or more valid EL expression parts. The following list shows examples of valid syntax:

  • #{row.bindings.ProductId.inputValue}

  • #{components.TAB416222534.errors}

  • #{res['excel.saveButton.label']}

• A valid Excel formula. An Excel formula string must start with the = character. If the literal string includes an #{...} expression, the Oracle ADF Desktop Integration module evaluates this expression first and inserts the resulting value into the Excel formula string. Excel then evaluates the Excel formula.

  Note the following points if you write an EL expression:

  • Excel formula elements must not be used inside an #{...} expression.

  • EL expressions should not contain references to Excel cells because EL expressions are managed within ADF metadata. Excel cannot update the ADF metadata if the referenced cell moves. A workaround is to define a named cell reference or range using the Name box in the Excel Formula Bar. You can reference the named cell reference or named cell range reference from an EL expression. For information about defining named cell references or ranges, see Excel's documentation.

• EL expressions in a page definition file

  For information about the syntax that you use to write EL expressions in a page definition file, see Section 4.3, "Working with Page Definition Files for an Integrated Excel Workbook".

B.2 EL Syntax for Oracle ADF Desktop Integration Components

Table B-1 lists supported expression properties for the Oracle ADF Desktop Integration components that support EL expressions.

The EL expressions use the following syntax to reference these properties:

#{components.componentID.property}

where componentID references the ID of the component and property references the property (for example, rowCount).

Write EL expressions with the following syntax to retrieve:

• Worksheet errors at runtime

  #{worksheet.errors}

  For more information about worksheet errors, see Section 12.4, "Error-Reporting in an Integrated Excel Workbook".

• Workbook initialization parameters

  #{workbook.params.parameterName}

  where parameterName is the name of the workbook initialization parameter. For information about using these parameters, see Section 8.11, "Passing Server Data Context from a Fusion Web Application Page to a Workbook".

• Resource bundle string key values

  #{resourceBundleAlias['resourceBundleKey']}

  where resourceBundleAlias is the alias of the resource bundle and resourceBundleKey is the string key value. For more information about resource bundles, see Section 10.2, "Using Resource Bundles in an Integrated Excel Workbook".

Table B-2 describes the supported syntax and properties for Oracle ADF control bindings. For information about the attribute control hints (controlHint) that the Oracle ADF Desktop Integration module supports, see Table B-3.

You can use the expression builder described in Section 5.6, "Using the Expression Builder" to generate some of the EL expressions described in Table B-2. You have to write some other EL expressions as indicated in Table B-2.

#{bindings.attributeID}
#{bindings.attributeID.label}
#{bindings.attributeID.hints.controlHint}

#{bindings.attributeID.inputValue}

""

#{bindings.ListID}
#{bindings.ListID.label}
#{bindings.ListID.hints.controlHint}

""

#{row.bindings.attributeID.inputValue}

#{bindings.TreeID.[TreeNodeID].AttributeNamePrefix*.inputValue}

""

B.3 Attribute Control Hints in the Oracle ADF Desktop Integration Module

The Oracle ADF Desktop Integration module can read the values of the attribute control hint names described in Table B-3. You write EL expressions that the Oracle ADF Desktop Integration module uses to retrieve the value of an attribute control hint from your Fusion web application. Table B-2 describes the EL expression syntax that retrieves the values of attribute control hints at runtime.

You configure attribute control hints in your Fusion web application. Information about how to add an attribute control hint to an entity object can be found in the "Defining Attribute Control Hints for Entity Objects" section of the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework. Information about how to add an attribute control hint to a view object can be found in the "Defining Attribute Control Hints for View Objects" section of the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

#{bindings.attributeID.hints.readOnly}

=NOT(#{bindings.attributeID.hints.updateable})