|
Hyperion (Brioquery) 8
Best Practices and Important Facts
Be aware of these important facts prior to using Hyperion (BrioQuery) 8. If you discover something about Hyperion 8 that you want to share with others, feel free to email that information to Desktop Technologies so we can update this page regularly with pertinent information.
|
Always use Hyperion Brio 8 from YAMS. Do not copy the Hyperion Brio 8 software to your local system. This will ensure that the software you are using is always up to date.
|
| Brio 5 queries will NOT open in Hyperion (BrioQuery) 8. |
| Thus far, Hyperion 8 will open and run Brio 6 queries without problems. However, more testing is currently being done to validate this finding. |
| Brio 6 will open and process Hyperion 8 queries. However, if your query contains features that are not available in Brio 6, you may get errors. |
Administrative Staff computers have been setup to automatically run the correct version of BrioQuery (i.e. Version 5 or Version 6) when you double-click a .BQY file. This feature does not work with Hyperion 8.
Therefore, you should launch Hyperion 8 and use "File\Open" to open your saved query.
|
| During testing Hyperion Brio 8, keep all Brio 8 queries in a separate directory. YAMS will automatically create a default directory for your Brio 8 queries (C:\Data\Brio\Brio8). |
| Prior to testing your Brio 6 queries in Hyperion 8, we recommend that you make a backup copy of your queries. |
| Preliminary testing indicates that OCE (Open Catalog Extensions) files modified with Hyperion Brio 8 software are unusuable in Brio 6. More testing and feedback is needed to validate this finding. |
Developer's Information
What's New in Hyperion (BrioQuery) 8
Explorer and Designer are developer tools used to create BQY documents.
They both remain the same with a few feature enhancements. |
| New Export to HTML options - New row and pixel options for putting breaks in HTML pages when pre-generating output. This new feature is required for the Intelligence iServer, but extended to HTML exporting in the Brio clients. |
| Enable/Disable Document Scripts option - The execution of document scripts can be enabled or disabled for all clients, desktop clients (Explorer and Designer), Scheduler (scheduling functionality via the web), Thin Client (Intelligence iServer), and the plug-in client (Insight). |
| Save user-defined properties - Insight, Explorer, and Designer now provide the ability to save user-defined properties with a BQY document. This enables a BQY document to remember user information. For example, limit values that a user enters one day can be re-established the next day when the user returns to the document. This feature also enables users to store the date that a document last processed so that two charts can be side-by-side to show historical data in an EIS section. |
| New licensing - A license key is all that is required to install Explorer or Designer. |
| New registry location for Insight, Explorer, and Designer - Uses the same user hive but a different key under that hive. |
| No support for version 5.x Detail sections - It is not possible to display a Detain section in Brio 8. Detail sections are not displayed, even if they exist in a document. Version 6.2 is the oldest version that shows a Detail section. |
| New/changed database and API support - The Data Access Service requires multi-threading capabilities supported by CTLib for Sybase instead of DbLib, and support for Essbase 6.5, which is the equivalent of DB2 OLAP 8.1. |
| Mac clients supported via the Intelligence iServer only. There is no client/server version for macintosh clients. |
|