Configuring a Data Request
You can configure a data request to:
Query and return data from an EnterpriseOne table or business view.
Perform an aggregation of data from a table or business view and return aggregate amounts.
In a standard data request that returns data directly from a table or business view, you can use variables to define the return fields. In a data request that performs an aggregation, you can use variables to define the "group by" fields and the returned aggregate amounts. You define a variable by typing a name next to the field or item that represents the returned value.
When you add a data request to an orchestration, any variables that you define are automatically added to the orchestration as inputs. This enables you to map the returned data to subsequent steps in an orchestration.
After creating a data request as described in Creating a Service Request, perform these tasks:
Load the Fields from a Table or Business View
You need to know the name of the table or business view that contains the data you want returned. If you do not know the table or business view name, but you know the application that uses the table or business view, you can use the JD Edwards EnterpriseOne Cross Reference Facility (P980011) to identify the table or business view associated with the application. From the Cross Reference form, click the "Interactive Applications" tab, then click the "Business Views Used by an Interactive Application" or "Tables Used by an Interactive Application." If you do not have access to the Cross Reference Facility, ask an administrator to look up this information for you.
In the Available Actions area, enter the name of the table or business view in the Table/View Name field.
Click the Load button.
The Orchestrator Studio loads all fields from the table or business view into the grid.
Configure a Data Request to Return Field Data
After loading fields from a table or business view, set up filtering criteria and specify the fields that contain data that you want returned.
For example, a business analyst wants to add a data request to an orchestration that returns a customer's credit limit amount. The orchestration has "Customer Number" defined for one of its inputs. To configure the data request, the business analyst:
Sets up filter criteria with a condition that filters on Address Number.
Selects the Credit Limit and Alpha Name fields for the return data.
Adds the data request to the orchestration, mapping the Customer Number input in the orchestration to the Address Number in the data request.
When the data request is added to the orchestration, the Credit Limit and Alpha Name fields automatically become additional inputs to the orchestration, which the business analyst can then map to subsequent orchestration steps.
To configure a data request to return field data:
Define the filtering criteria for the data request:
In the Fields grid on the left, click the "Filter" icon next to the field or fields that contain data that you want to filter on.
The Orchestrator Studio displays each field in the Filter Criteria area on the right.
For each field in the Conditions box, select the appropriate operand and in the adjacent field, enter a hard coded value or a variable.
A variable appears in the field by default. If you modify the variable name, make sure the syntax includes the $ sign and brackets, for example:
${Address Number 1}Select the Match All or Match Any option to determine how the conditions are applied.
You can also click the Options button, and from the Query drop-down list, select a predefined q uery to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.
Specify the data you want returned:
In the Fields grid, click the "Return" icon next to each field for which you want data returned.
Each field appears in the "Return Fields and Variable Names" on the right.
(Optional) You can use a variable for the return by entering a name for the variable in the adjacent blank field.
Note: Return variables do not need the${}notation. This notation is only necessary for input variables to distinguish between a variable and a hard coded value.When you add a data request to an orchestration, these variables are automatically added to the orchestration as inputs, which you can use to map return data to subsequent orchestration steps.
(Optional) For the return data, determine the order by which you want the data returned:
In the grid on the left, select the Order By icon next to any field that was selected for the return data.
The Orchestrator Studio adds the field name to the Order By area on the right.
In the drop-down list next to the field name, select Ascending or Descending.
(Optional) Click the Options button to configure settings that control how the AIS Server processes a data request at runtime. See Configuring Form Request and Data Request Processing.
Configure a Data Request to Perform an Aggregation
To configure a data request to return aggregate amounts:
After loading the fields from a table or business view, slide the Aggregation toggle to the right.
This enables the aggregation features in the Fields grid.
Click the "Filter" icon next to the fields that contain the data that you want to filter on.
The Orchestrator Studio displays each field in the Conditions area on the right.
Set up conditions for filtering data:
For each field in the Conditions box, select the appropriate operand and in the adjacent field, enter a hard coded value or a variable.
A variable appears in the field by default. You can modify the variable name, but you must use the $ sign and brackets in the syntax, for example:
${Address Number 1}Select the Match All or Match Any option to determine how the conditions are applied.
You can also select the Options button, and from the Query drop-down list, select a predefined q uery to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.
Click the "Aggregate" icon next to the fields that contain the data for the aggregation.
In the pop-up window, select the type of aggregate that you want to perform.
The aggregate options displayed depend on whether the field contains a numeric value or a string.
(Optional) In the Aggregations and Variable Names section, click the Include Count check box if you want the response to include a count of the records returned. To use the returned count in a subsequent orchestration step, enter a variable name in the adjacent field.
(Optional) Use the following features in the Fields grid to further define the data aggregation:
"Having" icon. Click this icon next to a field for which you want to provide additional filtering criteria on an aggregation.
The Data Request design page displays the field in the Having section on the right.
a. Click the drop-down list next to the field and select the operand.
b. In the adjacent field, enter a hard coded value or variable.
"Group By" icon. Click this icon next to any field that you want the aggregate results grouped by. In the "Group By and Variable Name" section on the right, you can enter a variable name.
Using "Group By" may result in multiple rows being returned, one for each unique combination of a group. For example, you might return total orders for an entire year for customers, and group the results by customer. In this case, the data request response will return a unique row for each customer with the customer's total orders for the year.
Note: Variables are only supported in the first row of a response. If a query contains multiple rows, only the values from the first row will be available as variables."Order By" icon. For any fields used in an aggregate or "group by," click this icon to arrange return data in ascending or descending order.
(Optional) Click the Options button to configure settings that control how the AIS Server processes a data request at runtime. See Configuring Form Request and Data Request Processing.