Tip:
Highlight text to annotate it
X
Welcome back to the Getting Started with Oracle Endeca Information Discovery v3.0 series.
This is the beginning of Part 5: Creating a Feature-Rich Studio Application.
This screencast will show you how to add a Record Details component and configure a Results Table.
As we saw in an earlier screencast, whenever you create a new application, a new workspace page is automatically created,
containing a Results Table. Let's go take another look at it.
Note a few things about this component: It displays individual sales transactions, that are the base records in the Oracle Endeca
Server data domain, so there is no need for aggregation in this table.
End-users can toggle between different types of data. Initially we see sales transaction data, but we can select another value, such as Product,
and see how the table is updated.
There may be times when you would like to see the full record details of a particular record. The Record Details component is designed just for
that purpose. Let's add it to our page.
The goal is to be able to click on a particular record within the Results Table, and have the full record display in the Record Details component.
But we need to make some configuration updates to the Results Table before that can happen. So let's do that now.
In the default configuration, the 'Automatic Configuration' checkbox is checked. Let's uncheck that so we can control the attributes
and attribute groups used in the columns, as well as configure them.
Now we can design this table to our liking. The Persistent Columns can contain one or more column sets, and are always displayed on the
left. In our results table, we'll use 'Record-Spec', which is our unique identifier for each record.
The Interchangeable Column Sets in our example are based on attribute groups created earlier in the screencast series.
They are the options end users select from a drop-down menu to control the data displayed in the Results Table.
Let's make some changes to the Record Spec column.
One improvement we can make is to lock the column, so that when you scroll to the right, this column is locked in place and always displayed.
The other key change we'll make is to change Column Actions from 'Refinement' to 'Show Details'.
Now when an end-user clicks a particular Record Spec, it will no longer refine the components by that value.
Instead, it will show the details of that record in the Record Details component, which is what we want.
There are a few changes we'll make to the Interchangeable Column Set too. Since Record Spec is a combination of the sales order number
and sales order line number, and is already being displayed, there really is no need to display the Sales Order Number and Sales
Order Line Number when the Sales Transaction attribute group is displayed, so let's hide those columns.
And let's hide revision number too.
Click 'Show Preview' to see how it looks so far.
We can see that the Sales Order, Sales Order Line Number, and Revision Number are no longer displayed under Sales Transaction.
We can also see that the Record Spec column is now locked, just as we configured.
Notice that the 'Other' column set contains the attributes not used in other attribute groups -- resulting in a hodgepodge of attributes.
Let's remove this from the Interchangeable Column Sets. If end users are interested in seeing the values of these attributes, they can
view them in our new Record Details component.
One other point before we close the configuration for this component.
In order for the Results Table and the Record Details component to work together, they need to be based upon the same view.
This Results Table is using the Base View. Let's confirm the Record Details component is also using the Base View.
Good. By default, it is set to the Base View.
Now let's click on a specific record in the Records Table, and view the results in the Record Details.
The Record Details component now populates with the details of that record. Notice the information is grouped by attribute groups,
including the 'Other' attribute group that we deleted from the Results Table.
Also notice that clicking on a specific record spec in the Results Table no longer causes the components to refine on that value as before;
that's because we changed the Column Actions for record spec from 'Refinement' to 'Show Details'.
Results Tables can also be used to display data aggregated by dimensions rather than showing detailed records as we've done here.
See the Resellers page and the Products page of the Getting Started application for examples.
Reference our documentation for more information on configuring Results Tables and Record Details components.
Before we finish here, let's rename this page 'Record Details'. In this screencast, you learned how to add a
Record Details component, and configure the Results Table so they work together.
In the next screencast, you will learn how to add and configure a pivot table.