Upgrading Calculated Items Oracle BI Presentation Catalog: Other Upgrade Considerations

Planning to Upgrade from Oracle BI 10g to BI 11g 1-23 When you upgrade iBots that were set to start immediately, their Frequency setting on the Schedule tab of the Agent editor is Never. The actual start time from the Start Immediately schedule is guaranteed to be in the past, so is no longer valid. ■ In previous releases prior to 11g, you could create iBots that delivered the content to you as the owner of the iBot if you had selected the Me option. If you upgrade an iBot in which the Me option is selected, then the owner of the agent in 11g is one of the following: – A subscriber, if the agent is published. – A recipient, if the agent is not published. ■ In previous releases prior to 11g, you could create iBots that were conditionally triggered based on the results of requests now known as analyses. In this release, to create agents that are conditionally triggered, you use conditions. You can use an inline condition, that is, one that you define at the point of use and do not save to the Oracle BI Presentation Catalog, or you can use a named condition, that is, one that you have saved by name in the catalog. For more information, see Working with Conditions in Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition. An iBot conditionally triggered in a previous release prior to 11g is upgraded to use an inline condition with the default name of AgentCondition1. This inline condition evaluates whether the number of rows returned by the selected request is greater than 0. Note that you can still edit these conditions from within the agent, see the location of the analysis that it is based on, and save it elsewhere in the catalog. ■ In previous releases prior to 11g, you could specify that when a particular iBot completed, a custom Java program action was to execute. In this release, custom Java program actions are upgraded to Invoke Java Jobs actions and continue to run as before. However, these actions are read-only. For any new custom code that you want to run on the server, use the Invoke Java Method EJB action or the Invoke Web Services action.

1.3.2.6 Upgrading Pivot Tables

Note the following when upgrading pivot tables: ■ In 10g, by default, all rows of pivot tables are displayed. In 11g, you can page through the data as you can with table views, so by default, the first 25 rows are visible. When you click Graph Pivoted Results in the Pivot Table editor, you see a graph that displays only what is currently displayed on-screen in the pivot table. A graph is displayed per section in the pivot table. Users can then page through that graph using tape deck controls. ■ A pivot page prompt does not combine columns into one drop-down list. Instead, every column has its own drop-down list. ■ For pivot tables, there is an additional row in the column headers for the row heading labels. If there are no columns in either row or column, then there is also an extra column area or row area.

1.3.2.7 Upgrading Interactions in Views

In previous releases prior to 11g, you could set up interactions at the view level, which allowed you to override the interactions that had been set up at the criteria level. In this release, you create all interactions at the criteria level. If you upgrade