Page 1
Business Objects EPO 2.4.2
Release Notes
Page 2
Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
Copyright Copyright © 2007 Business Objects. All rights reserved.
Third-party
Contributors
Business Objects products in this release may contain redistributions of software licensed from
third-party contributors. Some of these individual components may also be available u nder
alternative licenses. A partial listing of third-party contributors that have requested or permitted
acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Page 3
Business Objects EPO 2.4.2 Release Notes
Contents
1 Introduction................................................................................................................................7
1.1 How to use this document ............................................................................... 7
2 What’s New in 2.4.2 ..................................................................................................................9
3 What’s fixed in 2.4.2................................................................................................................11
3.1 Fixed Issues................................................................................................... 11
3.1.1 Administration...................................................................................... 11
3.1.2 Model Construction.............................................................................. 11
4 Known Outstanding Issues...................................................................................................... 13
4.1 Issues Outstanding........................................................................................13
4.1.1 General................................................................................................ 13
4.1.2 Administration...................................................................................... 13
4.1.3 Model Construction.............................................................................. 13
4.1.4 Book Building....................................................................................... 14
4.1.5 End User Products .............................................................................. 15
4.1.6 Reporting Tools...................................................................................15
4.2 Known Limitations.......................................................................................... 15
Contents
|
5 Installation and Configuration Updates...................................................................................17
5.1 Database Upgrade / New Database..............................................................17
5.2 EPO Installation.............................................................................................17
5.3 Previous Installation and Configuration Upgrades ........................................ 18
6 Documentation Changes.........................................................................................................19
6.1 Document updates in previous releases .......................................................19
6.1.1 French Documentation........................................................................19
6.1.2 Data Bridge User Guide ...................................................................... 19
6.1.3 EPO Administration & Security Guide.................................................19
6.1.4 EPO Console User Guide ................................................................... 19
6.1.5 EPO Database User Guide for Microsoft SQL SERVER....................19
6.1.6 EPO Database User Guide for Oracle ................................................ 20
6.1.7 EPO Installation Guide........................................................................21
6.1.8 EPO Link for Proclarity........................................................................21
6.1.9 EPO MDX Connector Guide................................................................ 21
6.1.10 EPO Reference Guide......................................................................... 21
6.1.11 EPO Suite System Requirements ....................................................... 21
6.1.12 EPO User Guide.................................................................................. 21
6.1.13 EPO Work Manager User Guide.........................................................22
7 Changes for 2.4.1.................................................................................................................... 23
7.1 New Features ................................................................................................23
7.1.1 General................................................................................................ 23
7.1.2 Setup and Configuration...................................................................... 23
7.1.3 End User Products .............................................................................. 23
7.2 Fixed Issues................................................................................................... 24
7.2.1 General................................................................................................ 24
7.2.2 Setup and Configuration...................................................................... 24
7.2.3 Administration...................................................................................... 24
7.2.4 Data Import / Export ............................................................................ 25
7.2.5 Model Construction.............................................................................. 26
7.2.6 Book Building....................................................................................... 27
7.2.7 End User Products .............................................................................. 27
7.2.8 Work Process Functionality................................................................. 28
8 Changes for 2.4.0.................................................................................................................... 29
8.1 New Features ................................................................................................29
8.1.1 Setup and Configuration...................................................................... 29
8.1.2 General................................................................................................ 29
3
Page 4
Business Objects EPO 2.4.2 Release Notes
|
Contents
8.1.3 Model Building......................................................................................29
8.1.4 Book Building .......................................................................................30
8.1.5 EPO Data Loader – Oracle Edition......................................................30
8.1.6 EPO Console .......................................................................................31
8.1.7 MDX Connector....................................................................................31
8.2 Fixed Issues ...................................................................................................31
8.2.1 Setup and Configuration ......................................................................31
8.2.2 Administration ......................................................................................31
8.2.3 General ................................................................................................31
8.2.4 Model Building......................................................................................32
8.2.5 Book Building .......................................................................................33
8.2.6 End User Products...............................................................................34
8.2.7 Data Bridge ..........................................................................................34
8.2.8 EPO Data Loader – Oracle Edition......................................................35
8.2.9 EPO Console .......................................................................................35
9 Changes for 2.3.1.....................................................................................................................37
9.1 New Features.................................................................................................37
9.2 Fixed Issues ...................................................................................................37
9.2.1 Setup and Configuration ......................................................................37
9.2.2 Model Building......................................................................................37
10 Changes for 2.3.0.....................................................................................................................39
10.1 New Features.................................................................................................39
10.1.1 Setup and Configuration ......................................................................39
10.1.2 Model Building......................................................................................39
10.1.3 Book Building .......................................................................................40
10.2 Fixed Issues ...................................................................................................41
10.2.1 Setup and Configuration ......................................................................41
10.2.2 General ................................................................................................41
10.2.3 Model Building......................................................................................41
10.2.4 Book Building .......................................................................................41
10.2.5 EPO Data Loader – Oracle Edition......................................................42
11 Changes for 2.2.0.....................................................................................................................43
11.1 New Features.................................................................................................43
11.1.1 Setup and Configuration ......................................................................43
11.1.2 Administration ......................................................................................43
11.1.3 General ................................................................................................45
11.1.4 Model Building......................................................................................45
11.1.5 Book Building .......................................................................................46
11.1.6 End User Products...............................................................................47
11.1.7 Data Bridge ..........................................................................................47
11.1.8 EPO Data Loader – Oracle Edition......................................................47
11.2 Not Supported ................................................................................................47
11.2.1 End User Products...............................................................................47
11.3 Fixed Issues ...................................................................................................47
11.3.1 Administration ......................................................................................47
11.3.2 Model Building......................................................................................47
11.3.3 Book Building .......................................................................................48
11.3.4 End User Products...............................................................................49
11.3.5 Data Bridge ..........................................................................................49
11.4 New Documentation.......................................................................................49
11.4.1 EPO System Information......................................................................50
12 Changes for 2.1.0.....................................................................................................................51
12.1 New Features.................................................................................................51
12.1.1 General ................................................................................................51
12.1.2 Setup and Configuration ......................................................................51
12.1.3 Administration ......................................................................................51
12.1.4 Model Building......................................................................................51
12.1.5 End User Products...............................................................................52
12.1.6 EPO Service Manager .........................................................................52
4
Page 5
Business Objects EPO 2.4.2 Release Notes
12.1.7 Data Bridge.......................................................................................... 53
12.2 Fixed Issues...................................................................................................53
12.2.1 General................................................................................................ 53
12.2.2 Setup and Configuration......................................................................53
12.2.3 Administration...................................................................................... 53
12.2.4 Model Building.....................................................................................54
12.2.5 Book Building....................................................................................... 55
12.2.6 End User Products ..............................................................................55
12.2.7 Report Manager................................................................................... 56
12.2.8 Data Bridge.......................................................................................... 56
12.3 New Documentation ......................................................................................56
12.3.1 EPO Microsoft SQL Server 2000 Database User Guide..................... 56
12.3.2 EPO Oracle Database User Guide......................................................56
Appendix A Business Objects Information Resources.............................................................. 57
A1. Documentation and information services ......................................................58
A2. Documentation............................................................................................... 58
A3. Customer support, consulting and training.................................................... 59
A4. Useful addresses at a glance ........................................................................ 60
Contents
|
5
Page 6
Business Objects EPO 2.4.2 Release Notes
|
Contents
6
Page 7
1 Introduction
Note: Please contact Business Objects Customer Assurance if you require a French
translation of this document.
This document is designed to provide a list of updates and corrections made between releases
of Business Objects’ EPO application.
This document is updated for each software release and it is recommended that you read it
prior to installing any new or updated software distributed by Business Objects.
Enhancement Requests that are included in releases are also detailed within this document.
1.1 How to use this document
This document describes new features and updates to both the software and the
documentation in version 2.4.2 of the EPO Suite. These are listed in the following separate
sections:
What’s New in 2.4.2
•
Business Objects EPO 2.4.2 Release Notes
Introduction
|
•
What’s fixed in 2.4.2
•
Known Outstanding Issues
•
Installation and Configuration Updates
•
Documentation Changes
Sections 2 and 3 follow the same format, being arranged into separate areas of the product.
They are:
• General – Items that cover more than one area, such as Login changes, EPO
Console
• Setup and Configuration – Information about changes to the installation and
configuration of the suite, such as new minimum requirements
• Administration – Administrative tasks such as Security, System Information, Audit
• Data Import / Export - Including Data Bridge, EPO Data Loader and EPO Model
Builder import / export functionality
• Model Construction – For items specific to model infrastructure and dimension
functionality
• Book Building – For items specific to book building, such as Grids, Data Explorer
and Book design
• End User Products – For items specific to end users, such as Acrobat PDF view and
web or Book Viewer access
• Work Process Functionality – EPO Work Manager application
• Reporting Tools - Including EPO Report Manager, EPO MDX Connector, EPO Link
for ProClarity
The documentation updates and corrections are listed in the following section:
Documentation Changes
•
This section is separated into 3 sub-sections. They are:
• New Documents – For new documentation added to the EPO suite.
7
Page 8
Business Objects EPO 2.4.2 Release Notes
|
Introduction
• Documents reissued for this release – For existing documents that have been
reissued.
• Document updates in previous releases – For details of changes made to existing
documents.
Each document is listed separately.
8
Page 9
2 What’s New in 2.4.2
There are no new features in version 2.4.2 of the EPO suite of products.
Business Objects EPO 2.4.2 Release Notes
What’s New in 2.4.2
|
9
Page 10
Business Objects EPO 2.4.2 Release Notes
|
What’s New in 2.4.2
10
Page 11
Business Objects EPO 2.4.2 Release Notes
3 What’s fixed in 2.4.2
The following section describes the fixes in version 2.4.2 of the EPO suite of products.
3.1 Fixed Issues
3.1.1 Administration
• EPO_AU_SECURITY audit trigger s not working on Oracle (963235)
Audit was not updating the EPO_AU_SECURITY table in Oracle.
3.1.2 Model Construction
• Activity Driver consolida tions are zero after data change with calculation option
selected (984887)
In a specific model, when Calculation including all leaf activity driver values was set, if
an Activity Driver value was changed, then the Activity Driver consolidations were being
set to zero.
• Problem with copying versions (979955)
In a specific model, after carrying out Copy Version, the calculations were not always
correct.
• Resource Driver Assignment screen for Services not working correctly (Oracle)
(962533)
Setting Resource Driver Services assignments was saving incorrect data to the database.
What’s fixed in 2.4.2
|
11
Page 12
Business Objects EPO 2.4.2 Release Notes
|
What’s fixed in 2.4.2
12
Page 13
Business Objects EPO 2.4.2 Release Notes
4 Known Outstanding Issues
The following is a list of all known outstanding issues within the EPO suite of products. Any
caveats with the software are also noted here.
4.1 Issues Outstanding
4.1.1 General
• Activity Analysis Migration
Any users intending to migrate from version 1.5.x Activity Analysis are requested to seek
assistance from your Business Objects Account Manager.
• Hiding accelerator chara cters is not consistent (3207)
Windows XP Theme "Hide underlined letters for keyboard navigation until I press the Alt key" is
not always effective. Sometimes the accelerator characters are underlined on entry to a
window, without pressing the Alt key.
4.1.2 Administration
Known Outstanding Issues
|
• Line item / Responsibility Center Direct Activity (5433)
Any change to a Line Item / Responsibility Center Direct Activity (for example, setting it to
‘Spare Resource’) caused the relevant entry in the database table to be deleted and then
regenerated, rather than updated. This causes an extra line to be written for each change, and
also for every other line in the table.
• Exception in EPO when selecting non-exis tent Security Descriptor from Dimension
screen (3061)
After deleting a Security Descriptor from the Security screen, it may still be selected in the
Dimension Security Dropdown within the Dimension screen. As the item no longer exists, this
causes an exception.
• Change Own Password Security descriptor
The security descriptor for Change Own Password Security has now been removed. However,
when importing a model that had been exported prior to release 2.0.4 (with security), the old
descriptor will appear. This may be ignored as it will not influence password security, or it can
be deleted.
4.1.3 Model Construction
• Group bar doesn't scroll to allow dimensions to be copied to groups not in view
(4636)
In the main screen Group Bar, it is not possible to drag a dimension from a group to another
group that is not in the currently visible area of the screen. To move a dimension to a position
beyond the current viewing area, it may be necessary to move it in stages.
• Assignments – Buttons not av ailable when screens are maximized (4482)
The ‘Activities Reassignment’ and ‘Cost Object Assignment’ screens open in such a way that
the ‘Apply’ and ‘Clear’ buttons may not be visible within the window. The screen can be
manually adjusted to make the buttons visible.
• Rules wizard drops out of selection window (4232)
The Rules wizard appears to drop out of the Dimension Item Selection Dialog if you double
click on the dimension tree. In fact, if you have highlighted a valid selection, it simply accepts
this and returns to the Simple Expression Editor window, without requiring the OK button to be
pressed.
• Large Fonts in DimensionTree control
When you use large fonts, if you open and expand a DimensionTree dropdown control, the
selected item’s description is truncated.
13
Page 14
Business Objects EPO 2.4.2 Release Notes
|
Known Outstanding Issues
4.1.4 Book Building
• Changing currency in Books and Data Explorer does not refresh automatically
(5202)
In Modelbuilder, Books Editor, changing the currency does not refresh the display
automatically. The only way to get the currency to change is to scroll down the grid or reload
the book. Also in Modelbuilder Data Explorer, changing the currency does not refresh the
display automatically. However it is quickly refreshed by clicking on the display.
• Some fonts not appearing for controls on the web (4380)
The fonts ‘Script’, ‘Webdings’ and ‘Wingdings’ may be set for any book control in a book,
however they will not appear in the web browser. These fonts may still be used successfully for
text.
• View Builder –Save format inconsistent if changing format when loading view (5457)
If you have made changes to a view that was loaded from the database, and then select to
load a new view from disk, the changes to the first view will be saved onto disk, instead of the
database from which it was originally loaded. This also happens in the reverse situation where
you have made changes to a view that was loaded from disk and select to load a new view
from the database – the first view will now be saved onto the database instead of disk. In order
to save the view in its original format, select an appropriate Save action before selecting the
Load action.
• View Builder - duplicate grid value names when using 'Add to column/row’ (4323)
In View Builder, you can select an item from Grid Values and use the Grid Values Context
Menu functions Add to Column or Add to Row, to add this item to your layout. The Add to
Col/Row functions do not perform any validation on your selection and so it is possible to
create a layout with duplicate Column or Row Header names. The layout may be populated
with unidentified values, where this duplication has occurred, therefore care should be taken
when using these functions to create a layout.
• Saving to Acrobat PDF format in Editable Books (4360)
It is not possible to save to Acrobat PDF format from an editable Book. It is possible from a
read-only Book.
• View Builder - Limitations in Graph Mode (4831 )
Some grids cannot be represented in certain graphical forms, for example when no headers
exist on one of the axes. Limitations also exist with grids using the Replace with Keys option,
which dynamically alters the view of your data to the selection in the Pivot Bar. Representation
of expanded groups can also be affected for similar reasons with particular graph types.
• Context menu sometimes stops working for books section of Group Bar (4427)
After building books in Model Builder for a while, the context menu on the books section of the
Group Bar sometimes stops working, i.e. the context menu doesn't appear when you right click
on a book.
• Relational View – Primary aliases don’t get applied straight away (4888)
When a relational data view is created in Data Explorer, then you change the primary alias, the
change is not applied instantly – you either have to refresh the view or scroll up and down in
the book. (Note: This fault also occurred previously when viewing the relational view on the
web via a book, but it has now been fixed on the web.)
• Intermittent Horizontal Scroll Bar Inactive in Grids
Intermittently scroll bars do not respond in Grids. Refreshing the page by resizing or
expanding / contracting the Headers will solve this problem.
• Graph Axis Persistence
Changing the angle of a Graph axis is not persisted after saving and closing a Book.
Reopening the Book will display the default angle. To be fixed in a later version.
• Single Grid Header
A layout containing only a Header on the vertical axis will not be displayed in Preview mode.
Always ensure there are Headers on both axes.
• Book Scripting (2775,3079)
In book scripting, ‘chart.visible = false’ does not work.
14
Page 15
Business Objects EPO 2.4.2 Release Notes
Known Outstanding Issues
4.1.5 End User Products
• Default EPO books fail to load when first opened (4749)
In a Windows 2000 SP4 operating system with IE6 SP1 you may find that you cannot display
the default book after the EPODataX.cab file, the ActiveX toolbar, has been downloaded and
installed for the first time. This problem is resolved by closing the Internet Explorer session
and launching a new session.
• On the web, Data Explorer in PDF is blank (4712, 4444)
When displaying the Data Explorer in PDF form on the web, the data pane and some
dimension trees are blank. To be fixed in a later version.
• Elements of dimension hierarchy display differently in dim tree control in web
browser (5066)
Dimension security can be set on both dimension items and groups in both the Main and
Attribute hierarchies. In some circumstances this can produce versions of the dimension tree
that differ, depending on whether the book is displayed on the Web or in a Win32 client
(including Book Viewer).
• Lost Parameters after PDF view
In the web, if a parameter is used to build a view and you switch to PDF and then back to
‘Normal’ view, the parameter is lost.
• Navigating between Models using back and forward IE buttons
It is possible to navigate between models using the Internet Explorer back and forward buttons
but the default books and Grids may not be correctly populated.
• Cursor Display in Edit Boxes (2659)
The cursor is not displayed in Edit Boxes in Web Books. To be fixed in a later version.
• Small fonts in Internet Explorer
Large/small fonts are unsupported in Web books.
|
4.1.6 Reporting Tools
• Avoiding Report Manage r OLE Error
Using the "Administrator" account to authenticate Report Tasks will generate an OLE Error
80020101. This error results from there being a single Administrator license. To avoid this
message create a new account, add it to the Administrator group, and use it as the security
credentials for running the Report Task.
This error message will be amended to provide more information in future releases.
4.2 Known Limitations
• Database Upgrade – New Database
For the current installation there is a database upgrade to version 2.4.2.
No loss of data should occur, but Business Objects recommends that you take a backup of
your models before running the scripts.
• Choice of CSV delimiter for Export / Illegal Characters in Import (4598)
Care should be taken to select an appropriate delimiter when exporting data to CSV. For
example, the use of a comma symbol (,) for the delimiter, would adversely affect the structure
of the exported data if a comma symbol is also used in any item name. Problems that may
result from this during subsequent imports could manifest in the appearance of illegal
characters (e.g. “) and corruption of data. In cases where the comma symbol is required in
item name(s), an alternative delimiter such as a semicolon (;) should be used.
• Multiple web sessions on the same client ca n freeze
In a Windows 2000 SP4 operating system with IE6 SP1 you may find that opening multiple web
browser sessions that load EPO books can lead to one or all of the sessions freezing. These
sessions cannot be reactivated and must be terminated (and the web user session logged off
using the EPO Monitor or EPO System Information tool on the Model Server). This problem is
15
Page 16
Business Objects EPO 2.4.2 Release Notes
|
Known Outstanding Issues
caused by a known issue with Internet Explorer Service Pack 1. See this article on the
Microsoft web site for more information:
recommends contacting Microsoft Product Support Services to obtain the hotfix.
• Contraction of Dimension Trees in Web Books
When you open a Dimension Tree in a Web Book, it will not contract automatically if you then
click away from it. The Dimension Tree needs to be contracted manually by clicking on it to
close the structure.
• Use of Ctrl+A shortcut in Data Explorer on the Web
In a Win32 client the Ctrl+A shortcut can be used to select all the hierachy elements within
the Data Explorer control. However, if an embedded Data Explorer control within a book is
viewed via the Web, the same shortcut will select all the elements in the page rather than
in the control.
• Anti-Virus software may block e-mails
If anti-virus software is running on the Work Manager server it may interfere with the sending
and receiving of e-mails. You may receive the message "Unable to open socket to e-mail
SMTP server on port number: 25". As a result you will not be able to send or receive e-mails
via the Work Manager process. This is due to the anti-virus software blocking port 25. We
would recommend that port 25 be excluded from anti-viral inspection in order to allow mail to
pass freely between servers and clients.
• Deleting an alias does not display item values correctly (3441)
If the primary alias for a model is set to a Data Alias, the values from this Data Alias will
continue to be displayed after it has been deleted, even though the primary alias is reset
automatically to the Default Alias. If you go into Select Data Aliases, where the primary alias is
now set automatically to Default Alias, and click OK, the correct default item values will now be
displayed. Alternatively, the default item values will appear correctly, the next time the model is
closed and reopened.
http://support.microsoft.com/?kbid=837162, which
16
Page 17
Business Objects EPO 2.4.2 Release Notes
Installation and Configuration Updates
5 Installation and Configuration
Updates
5.1 Database Upgrade / New Database
• IMPORTANT INFORM ATION
For the current installation there is a database upgrade to version 2.4.2.
There were significant changes to the database scripts for Release 2.2.0. Therefore, for any
users upgrading from a release prior to 2.2.0, to avoid database errors, please ensure that the
scripts are executed exactly as specified in your Database User Guide. It is also important to
check the Rebuild log files for errors at each stage before proceeding to the next set of scripts.
The action required differs according to which version of Activity Analysis or Predictive
Planning you are upgrading. Please refer to the appropriate section below.
Activity Analysis upgrades from version 1.x
Any users intending to migrate from version 1.x Activity Analysis are requested to seek
assistance from your Business Objects Account Manager.
Activity Analysis upgrades from version 2.x
Predictive Planning upgrades from version 1.x or 2.x
For Activity Analysis upgrades from a 2.0.x version, you may follow the same procedure as for
Predictive Planning upgrades.
You may choose to upgrade your existing database to 2.4.2 or build a new version 2.4.2
database. No loss of data should occur, but Business Objects strongly recommends that you
take a verified backup of your database and export models to XML before running the upgrade
scripts.
To optimize performance and Rules, models should be exported to XML and imported into the
version 2.4.2 database after upgrade.
|
5.2 EPO Installation
• Licensing
New license keys will be required to successfully upgrade EPO from version 1.x to 2.4.1. This
may be provided in the form of an ELF file that should be loaded using the Registration
Information screen. Please refer to sections 3.4 and 5.5.4 in the Installation Guide for details
on license keys and their use.
• Silent Installer
A Silent Install application is available on the CD that allows installations and configuration of
Windows client machines. It may be used to install Servers but must be manually configured.
Activity Analysis or Predictive Planning must be uninstalled to run successfully.
Note: This facility is not currently documented. If you wish to use this please contact
Business Objects.
• Web Deployment Cab file Upgrade
The EPODataConnection Control downloaded by EPO Web Users has been upgraded. This
will require a new file to be downloaded by all Web Users who connect to the upgraded
system.
Problem with Web Default EPO books failing to load when first opened
In a Windows 2000 SP4 operating system with IE6 SP1 you may find that you cannot display
the default book after the EPODataX.cab file (the ActiveX toolbar) has been downloaded and
installed for the first time. This problem is resolved by closing the Internet Explorer session
and launching a new session.
17
Page 18
Business Objects EPO 2.4.2 Release Notes
|
Installation and Configuration Updates
Please refer to the EPO Installation Guide document for information on web deployment.
5.3 Previous Installation and Configuration Upgrades
• Communication via Sockets
DCOM will continue to be the default method for inter-machine communication. However,
during EPO Installation, it will now be possible to select the option to use TCP/IP sockets
instead, and this will remove the requirement for configuration of DCOM settings.
There is no need to reset any previous DCOM configuration settings from an earlier installation,
since they will have been removed by the Uninstall process.
• Database Auditing
During EPO Server Configuration, the EPO Database Auditing screen will appear. This gives
you the option to enable or disable database auditing. For further information, please refer to
the EPO Installation Guide.
For Microsoft SQL Server Database users, the user who performs the configuration MUST be a
member of the database ‘DBO’ user group for Audit to function correctly. If restricted user
access is required and Audit needs switching on, you must run EPO Configure first as a user
who is a member of the DBO group, and then run again as the restricted user.
• Enable Single Sign On secondary web login (5495)
When running EPO Configure the user can now choose to 'Enable Secondary Logon' for the
Win32 and/or Web applications. If logging onto the Web through SSO fails for any reason, then
the user will be able to login manually if the option to 'Enable Secondary Logon' has been set.
18
Page 19
Business Objects EPO 2.4.2 Release Notes
6 Documentation Changes
There have been no changes to the documentation supplied in Release 2.4.2.
Note: The French documentation and Help files in this version describe Release 2.4. For descriptions of
new features and updates that exist in Version 2.4.2, please see the English documentation.
6.1 Document updates in previous releases
6.1.1 French Documentation
French translations of the following documents are now available, that describe Release 2.4:
• ALG Data Bridge Use r Guide
• EPO Administration & Security Guide
• EPO Console User Guide
• EPO Installation Guide
• EPO Link for ProClarity
• EPO MDX Connector Guide
• EPO Reference Guide
• EPO Report Manager User Guide
• EPO Service Manager
• EPO Suite System Requirements
• EPO System Information
• EPO User Guide
• EPO Work Manager User Guide
Documentation Changes
|
6.1.2 Data Bridge User Guide
This document has been reissued and version Release 2 Issue 5 is now available. It contains various
changes; in particular please note the following:
• Section 2.2.6.1 LOOKUP
Wording has been revised to correct the example and clarify the requirements (4042).
6.1.3 EPO Administration & Security Guide
This document has been reissued and version Release 2.4 is now available. It has been restructured
and contains additional Security Descriptor information.
6.1.4 EPO Console User Guide
This document has been reissued and version Release 2.4 is now available. The following sections
have been updated with information on the new option Encrypted Password (4840):
• Section 1.3.1.1 Creating a parameter list
• Section 1.4.4 Command files
6.1.5 EPO Database User Guide for Microsoft SQL SERVER
(Renamed document from EPO MS SQL SERVER Database User Guide)
This document has been reissued and version Release 2.4 is now available. It includes changes in the
following areas:
• Sections 3.2.2 Microsoft SQL Server New Database Setup and 3.2.3 Microsoft SQL Server
Existing Database Upgrade
Added note re authentication checks for SQL scripts (4415)
19
Page 20
Business Objects EPO 2.4.2 Release Notes
|
Documentation Changes
• Added sections:
4.1.13 PPR_RBACTIVITYDRIVERVALUE,
4.1.14 PPR_RBCURRENCYRATES,
4.1.15 PPR_RBLINEITEMDETAILVALUE,
4.1.16 PPR_RBLINEITEMFIXEDVALUE,
4.1.17 PPR_RBLINEITEMVALUE,
4.1.18 PPR_RBLINEITEMVARVALUE,
4.1.19 PPR_RBRESOURCEDRIVERSPLIT,
4.1.20 PPR_RBRESOURCEDRIVERVALUE,
4.1.21 PPR_RBREVENUE,
4.1.22 PPR_RBSERVICEDRIVERVALUE,
4.1.23 PPR_RBSERVICEFACTOR,
4.1.24 PPR_RBSPREADVALUE,
4.1.25 PPR_RBWORKSHEETVALUE
New tables for exporting rule based values to database (4314)
• Added sections 6.3.48 PP_AU_EXTERNALACTIVITYVALUE
New table for Activity Level Results (4379)
• Added section 6.3.49 PP_AU_EXTERNALCOSTOBJECTVALUE
New table for Cost Object Level Results (4379)
6.1.6 EPO Database User Guide for Oracle
(Renamed document from EPO Oracle Database User Guide)
This document has been reissued and version Release 2.4 is now available. It includes changes in the
following areas:
• Section 3.2.2.1 Preparing a Database Area for EPO
Altered description of Character/National Character sets for Oracle 9i and 10g.
• Sections 3.2.2.3 Installing the EPO Database Structures and 3.2. 3.2 Running the Upgrade
Scripts
Added note re authentication checks for SQL scripts (4415)
• Added section 8.7 Additi onal Support Routines
Describes new functionality to load model data into Staging Table format (4349)
• Added sections:
9.1.13 PPR_RBACTIVITYDRIVERVALUE,
9.1.14 PPR_RBCURRENCYRATES,
9.1.15 PPR_RBLINEITEMDETAILVALUE,
9.1.16 PPR_RBLINEITEMFIXEDVALUE,
9.1.17 PPR_RBLINEITEMVALUE,
9.1.18 PPR_RBLINEITEMVARVALUE,
9.1.19 PPR_RBRESOURCEDRIVERSPLIT,
9.1.20 PPR_RBRESOURCEDRIVERVALUE,
9.1.21 PPR_RBREVENUE,
9.1.22 PPR_RBSERVICEDRIVERVALUE,
9.1.23 PPR_RBSERVICEFACTOR,
9.1.24 PPR_RBSPREADVALUE,
9.1.25 PPR_RBWORKSHEETVALUE
New tables for exporting rule based values to database (4314)
• Added sections 11.3.48 PP_AU _EXTERNALACTIVITYVALUE
New table for Activity Level Results (4379)
• Added section 11.3.49 PP_AU_EXTERNALCOSTOBJECTVALUE
New table for Cost Object Level Results (4379)
20
Page 21
Business Objects EPO 2.4.2 Release Notes
Documentation Changes
6.1.7 EPO Installation Guide
This document has been reissued and version Release 2.4 is now available. It includes changes to
describe the new Database Connectivity options (4624):
• Section 5.5.1 Database Communicati on replaces old section now renumbered as 5.5.1.1 EPO
Server Database Setup.
• Added ne w section 5.5.1. 2 Oracle Instant Server Database Setup.
• Amended section 8 title to “Removing and Upgrading the software” (4673)
Added information on how settings are affected by the uninstall process.
6.1.8 EPO Link for Proclarity
This document has been reissued and version Release 2.4 is now available. It has been amended
where the ODBO process has been replaced by MDX Connector.
6.1.9 EPO MDX Connector Guide
(Renamed document from ODBO User Guide)
This document has been reissued and version Release 2.4 is now available. It has been amended
where the ODBO process has been replaced by MDX Connector.
|
6.1.10
6.1.11
This document has been reissued and version Release 2.4 is now available. It includes changes to
describe the new External GridValues and Functions (4379):
• Added sections:
2.2.8 ExternalActivityFixedValue,
2.2.9 ExternalActivityValue,
2.2.10 ExternalActivityVariableValue,
2.3.19 ExternalCostObjectFixedValue,
2.3.20 ExternalCostObjectValue,
2.3.21 ExternalCostObjectVariableValue,
3.3.8 ExternalActivityFixedValue,
3.3.9 ExternalActivityValue,
3.3.10 ExternalActivityVariableValue,
3.5.20 ExternalCostObjectFixedValue,
3.5.21 ExternalCostObjectValue,
3.5.22 ExternalCostObjectVariableValue
This document has been reissued and version Release 2.4 is now available. It includes changes in the
following areas:
• Section3.6.1 ProClarity
Amendment for MDX Driver
• Section 3.2 EPO Application Server
Amendment for Database Connectivity options (4624)
EPO Reference Guide
EPO Suite System Requirements
6.1.12
This document has been reissued and version Release 2.4 is now available. It includes numerous
revisions, with changes specifically in the following areas:
• Section 2.6.1.2 Model Calculation Options
Further model calculation options added in Release 2.3.0 (4409, 4411)
• Sections 5.1.4.5. Graph Tab and 5.2.8 Replace with key (4831)
EPO User Guide
21
Page 22
Business Objects EPO 2.4.2 Release Notes
|
Documentation Changes
Documentation updated to warn of limitations in Graph Mode.
• Section 5.2.10.4 Grid Formula Context Menu
• Section 5.2.11 Grid Data Context Menus
• Section 5.2.12 Color Coding Data Valu es
Amended for Grid coloring and formatting enhancements (4642) and Grid context menu changes (4418)
• Added sections 5.5 Data Explorer and 6.1.6.18 Data Explorer
Describes new Data Explorer functionality and how Data Explorer layouts may be displayed in books
(4078)
• Added section 6.1.6.12.1 Image Hotspots
Describes new functionality for hotspots for images in books
• Added section 7.6.4 The Activity Driver Rule Wizard
Describes wizard for creating derived Activity Drivers (4522)
• Section 7.8.1.2 Selecting Dimensions
New selection options on Export Dimensions screen context menu (4577)
6.1.13
This document has been reissued and version Release 2.2.0 Issue 1 is now available. Information on
Workflow URL’s for Book Viewer has been added to the following sections (3263):
• Section 3.1.3.3 Add Link to EPO Book
• Section 3.1.4 Create Books
• Section 5.2.5 Example URL
• Updated Section 7 Work Manager Functions List
EPO Work Manager User Guide
22
Page 23
7 Changes for 2.4.1
The following section describes the new features and product amendments that were
introduced in version release 2.4.1 of the Enterprise Performance Optimization suite of
products.
7.1 New Features
The following is a list of new features released in version 2.4.1 within Predictive Planning /
Activity Analysis.
7.1.1 General
• e-Authentication for Single Sign On (5524)
(Initially implemented in EPO Version 2.4.0 SID Fix 2)
The EPO framework is now able to store a Security Identifier (SID) against a user in the
EPO system as an alternative means of User access, instead of the Username and
Password. The use of SIDs increases the security of SSO integration, as a SID is not
easily identifiable with a specific user.
When a SID is used to login, the Windows Client user interface and Web user interface will
display the Username, rather than the SID.
System administrators will be responsible for creating the appropriate SQL scripts to
synchronise their organisation’s SSO system with the user tables in EPO.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.4.1
|
7.1.2 Setup and Configuration
• Setup displays EULA
When installing EPO the End User License Agreement needs to be accepted in order to
continue.
• Enable Single Sign On secondary web login (5495)
When running EPO Configure in a Single Sign On configuration the user can now choose
to 'Enable Secondary Logon' for the Win32 and/or Web applications. This allows the user
to manually log into the Web using a secondary username.
7.1.3 End User Products
• ActiveX Single Sign On override (5495,5472)
If logging onto the Web through SSO fails for any reason, then provided that ‘Enable
Secondary Logon’ has been set during EPO Configure, the usual login form will be
displayed. If the configuration option has not been set, then an error message will be
displayed.
It is still possible to use the following override procedure if necessary:
Cancel the login dialog or any error message, then while holding down the Shift key, click
on the Refresh icon or the GO button. You will then be able to enter the required
username and password.
23
Page 24
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.1
7.2 Fixed Issues
The following is a list of fixes released in version 2.4.1 within Predictive Planning / Activity
Analysis.
7.2.1 General
• French User Help updated
The French translation of the EPO User Help is now available, describing Release 2.4.0.
• EPO Console failing in Korean envi ronment (5375)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Issue when using “prefixdate” and “log” commands together. In the resulting log file there
were characters missing from the file paths
• Correct Dimensions used when reading ESP files in EPO Console scripts (5035)
(Fixed in EPO Version 2.4.0 Patch 240-001)
ESP files using the Target Responsibility Center and/or Target Activity dimensions were
not being exported correctly by EPO Console.
7.2.2 Setup and Configuration
• Configuring a secondary model server with an Oracle EPO database using OCI
(5015)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Following EPO Configure, PADMainOCCI and PADModelOCCI executable files must be
manually registered as service and server respectively.
7.2.3 Administration
• Cost object driver audit table and cost object audit assignment record not being
updated (5429)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When an activity driver name was removed from the system, the associated audit table for
cost object driver was not updated. Similarly, when Cost Objects 1 to 5 were removed, the
associated cost object audit assignment record was not updated accordingly.
• Audit data amendments (501 0)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Corrections have been made to the auditing of attribute mappings data which previously
were recording inserts as updates.
• Auditing Snapshot routines (4984)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Corrections to snapshot routines allow deleted items to be correctly recorded in snapshot
audit data. Previously the DeleteUser and DeleteDate fields were not being updated.
• Default book audit record correctly updated
(Fixed in EPO Version 2.4.0 Patch 240-001)
Removing the default book was not being audited.
• Correction to auditing of External Costs (500 9)
(Fixed in EPO Version 2.4.0 Patch 240-001)
When removing an audited model, the ExternalActivityValue/ExternalCostObjectValue
database audit tables were not being correctly maintained.
24
Page 25
Business Objects EPO 2.4.2 Release Notes
7.2.4 Data Import / Export
• Export of Cost Object values stops after 800Mb memory limit reached (5545)
When exporting a large amount of Cost Object values (several million) to CSV text format
(or any other format), the export process was freezing at the point where the memory
requirement for the PADModel process involved in the export went above 800Mb.
• Problem exporting CURRENCYRATE table (5538)
The CURRENCYRATE table was not being exported automatically when selected (it was
only exported if the option “Include all rule based values” was set).
• Periods jumbled upon xml import (5309)
A model had periods arranged in chronological order and they appeared correctly in the
attribute hierarchies. When the model was exported to XML and imported into a new
model, the ordering of some of the periods was lost and the periods within the attribute
consolidation were no longer in chronological order.
• Duplicate records when exporting ReassignTrace table (5486)
(Fixed in EPO Version 2.4.0 Fix Feb07)
Many duplicate rows were generated when exporting the ReassignTrace table. Only
unique records are now exported.
• Problem importing some models via Model Builder (5366)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Some models were unable to be imported as XML via Model Builder, but were able to be
imported via EPO Console. This was due to a memory overrun in the record importer.
• Incorrect operation ID (5 316)
(Fixed in EPO Version 2.4.0 Patch 240-003)
On an Oracle database, when an XML file was imported into EPO containing
LineItemDetailValue records the items were created in the audit tables but with an
Operation ID of 2 instead of 1
• Database Write Back: export of traceback unsuccessful (5031)
(Fixed in EPO Version 2.4.0 Patch 240-002)
A problem was found where traceback records were not being exported to database using
the Database Write Back option. This problem only occurs with specific models and an
enhancement has been implemented to remedy this.
• Data Bridge Lookup does not work when item names contain a single
apostrophe (‘) (5017)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Any item in the data which had one apostrophe character in it did not get recognized,
whereas an item with two apostrophes did.
• Deletion of User Id data when using the DataBridge Replace option (5199)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When using the DataBridge Replace option, the DeleteUserId and the AuditId details of
the user who had deleted previous audit data was being overwritten by a subsequent
user’s ID, when the second user imported data.
• Data Bridge import of ExternalCostObjectValue s (4990)
(Fixed in EPO Version 2.4.0 Patch 240-001)
ExternalCostObjectValues were not being loaded correctly by Data Bridge when the Blank
option was selected for optional fields.
Changes for 2.4.1
|
25
Page 26
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.1
7.2.5 Model Construction
• Copy Period removes External Activity Value (5551)
When using Copy Period to make a copy of the period, the External Activity Value was
deleted from the source period and no value was copied to the new period.
• Resource Driver Overrides being removed (5178)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When adding a Resource Driver Assignment Override while the filter was on, the other
existing overrides were removed. To avoid this problem, the ‘Add’ button will now be
disabled while filtering is on. This prevents Resource Driver Assignment Overrides being
added unless the filter is off.
• Issue deleting an attribute on line items (5324)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Deleting an attribute on line items from the attribute consolidation page removed the line
item values for the line items that previously had this attribute checked.
• Top level items in Dimension views were highlighted by default but attributes
were not shown (5075)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When a dimension view was opened the top level item was highlighted but if it had
attributes assigned to it, these were not displayed. Also, it was not possible to assign
attributes by selecting the checkbox.
• Unchecking an activity attribute removed the cost object assignment for the
activity (5250)
(Fixed in EPO Version 2.4.0 Patch 240-003)
On an Oracle database, when an attribute on an activity with a cost object assignment was
checked and subsequently unchecked, the cost object assignment was removed. Also, if a
cost object assignment was created on a specific version and the version was then
deleted, the assignment was not deleted although it should have been.
• Server appeared to hang after a simple rule edit (5205)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Problems experienced after a simple rule edit on a specific model where, for example,
entering a blank line would cause a reboot.
• Smart Delete was not deleting some previously calculated results (5406)
(Fixed in EPO Version 2.4.0 Patch 240-003)
The Smart Delete function was not working correctly when a Restricted Parent had more
than one child.
• Memory Management improvement for large models (5036)
(Fixed in EPO Version 2.4.0 Patch 240-001)
An enhancement has been made to the EPO memory management routines to allow
models with several gigabytes of result data to open more quickly.
• Memory management problems with multiple models when running with OCCI
(5037)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Problems with Load Stored Values and Reports when running with multiple models in
OCCI installations.
• Cannot select an alias as a parameter for a rule (5002, 5003)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Using the simple expression editor it was not possible to choose an alias as a rule
parameter. The 'Select Alias' dialog should have been displayed but instead the rule
wizard produced an error message.
26
Page 27
Business Objects EPO 2.4.2 Release Notes
7.2.6 Book Building
• TargetCostObjectValue grid is very slow to return values (5531)
When asking for a very large number of values, a grid containing TargetCostObjectValues
was slow to return, and so a new algorithm has been implemented to improve this.
• Hotspot linking to external file (5468 )
(Fixed in EPO Version 2.4.0 Fix Feb07)
Problem linking a hotspot to an external file using the syntax external:file:///pathtofile.
There was no code in place in ModelBuilder to handle external links. This has now been
implemented.
• Consolidation Rule being ignored (54 92)
(Fixed in EPO Version 2.4.0 Fix Feb07)
This relates to displaying custom Currencies in a grid. Where items had a consolidation
rule applied, this was being ignored and the items were being summed, rather than having
the specific method of the rule applied.
• SourceActivity LineItem Values incorrect for some models (5425)
(Fixed in EPO Version 2.4.0 Patch 240-003)
SourceActivityLineItem values were being calculated incorrectly, and also summarized
incorrectly before export.
• Data Explorer not reflecti ng structure change (5410)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When items were moved in a dimension hierarchy from their original location, the
Traceback layout previously saved in Data Explorer no longer reflected them, although a
newly-generated one did.
• Target Cost Object Values not matching Traceback (5300, 5321, 5356)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Target Cost Object Values were not matching Traceback values and CostObject Values
on a grid designed to show product costs by Responsibility Centre and Activity (that the
cost originated from, prior to reassignment).
• Consolidation in External Activi ty Value Grid not correc t (5291)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Different currency External Activity values were not consolidating to the correct value.
• Displaying a grid with ResourceDriverSplit resulted in PADModel crash (5372)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Model processes were locking up 100% of the server resources when displaying a grid
showing ResourceDriverSplit consolidations.
• Changes to book charts not being s aved (4945)
(Fixed in EPO Version 2.4.0 Patch 240-003)
When a chart in a book was being changed e.g. from a bar graph to horizontal, the
changes appeared to be lost. This only occurred in a grid where the columns had Replace
with Keys set. The Replace with Keys process was losing the series formatting.
• Retrieval of view related information (4880, 4190)
(Fixed in EPO Version 2.4.0 Patch 240-001)
The display of Load and Save dialogs has been speeded up when loading views for the
first time In Book Viewer and Data Explorer.
Changes for 2.4.1
|
7.2.7 End User Products
• ActiveX needs to be updated (5480)
(Fixed in EPO Version 2.4.0 Fix Feb07)
ActiveX control failed to upgrade after EPO 2.4.0 patch installation. Version checking may
not have taken place in affected Patch versions. The header.asp file has been corrected to
ensure that proper version checking is performed.
27
Page 28
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.1
• Unable to log into EPO over the web (5326)
(Fixed in EPO Version 2.4.0 Patch 240-003)
It is now possible to log into EPO over the web using Unicode characters.
• Numbers in web books returning to original value after applying updates
pending (5236)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Values entered into a grid on a web book reverted to their original values after applying
Updates Pending, as well as other unexpected grid behaviour. Changes were being
allowed before the model was fully loaded.
• Incorrect font size display in Dimension List on the web (5308)
(Fixed in EPO Version 2.4.0 Patch 240-003)
In Book Builder, the Dimension list was displaying in the correct font size and style, but in
the web the font information for the Dimension List was being lost.
• Javascript errors causing errors when opening model or pages (5081)
(Fixed in EPO Version 2.4.0 Patch 240-003)
Further validation has been added for the syntax of any generated or created Javascript. It
now picks up any instance where the code module is not properly formed, and it will
generate an error when viewed in a web browser.
• EPO Configure not configuring the header.asp file correctly (5327)
(Fixed in EPO Version 2.4.0 Patch 240-003)
The ActiveX toolbar is now displaying correctly in all supported Korean environments.
• The .dllhost process was timing out intermittently and crashing the web server
(5338)
(Fixed in EPO Version 2.4.0 Patch 240-003)
This only occurred in a 3 tier environment when using IIS, when some users accessed the
web or started a work flow process. It gave an internal server error (500), and crashed the
dllhost.exe. EPOCOMPP.DLL and EPOOM.DLL files have now been installed to correct
the problem.
• Internet Explorer error message when attempting to load a book containing a
Data Explorer object
(Fixed in EPO Version 2.4.0 Patch 240-001)
When using the web via Internet Explorer version 6 SP2, an error in the EPO code was
picking up the web server name instead of the application server name and attempting to
forward requests to an invalid server.
7.2.8 Work Process Functionality
• Book Viewer reports Invalid Workflow ID error if opened using .ebk file (4999)
(Fixed in EPO Version 2.4.0 Patch 240-001)
Corrected problem when using .ebk file to open Book Viewer so it no longer reports an
Invalid Workflow ID error.
28
Page 29
8 Changes for 2.4.0
The following section describes the new features and product amendments that were
introduced in version release 2.4.0 of the Enterprise Performance Optimization suite of
products.
8.1 New Features
The following is a list of new features released in version 2.4.0 within Predictive Planning /
Activity Analysis.
8.1.1 Setup and Configuration
• Database Connectivity (4624)
A choice of database access protocol is now available during EPO Configure. This
allows Windows to use OCI rather than OLEDB to communicate with an Oracle database.
8.1.2 General
Business Objects EPO 2.4.2 Release Notes
Changes for 2.4.0
|
• French translations of PDF’s and Help updated
The French documentation and Help Files are in line with the English versions and
describe Release 2.4.0.
• Document Accessibility and Indexing
All EPO Product documentation PDF’s are now issued in accessible format, using the
Adobe accessibility features.
In addition, a PDX index file is available for the documentation PDF’s. This provides two
options for a search index: as a separate Index file, and as part of the Search facility within
each document.
• Invoke other EPO products from within Predictive Planning / Activity Analysis
(4318)
There is now an option to launch other EPO products from within Predictive Planning /
Activity Analysis. The Launch option on the Tools menu can be used to start the following
utilities:
• ALG Data Bridge
• EPO Work Manager
• EPO Report Manager
8.1.3 Model Building
• Importing data to Cost Object Costs (4379)
Two new tables are available that allow Activity Level Results and Cost Object Level
Results to be imported/entered directly into a model (EXTERNALACTLINEITEMVALUE &
EXTERNALCOSTOBJECTVALUE). The new values are:
• ExternalActivityFixedValue
• ExternalActivityValue
• ExternalActivityVariableValue
• ExternalCostObjectFixedValue
• ExternalCostObjectValue
• ExternalCostObjectVariableValue
• Export rule based values to database (4314)
29
Page 30
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.0
When using Export to Database, Rules Data Tables may now be exported with Data when
the option Include all Rule Based Values is selected.
• Activity Driver Rule Wizard (4522)
When you run the Rules Manager for Activity Drivers, there is now an option to select the
Activity Driver Rule Wizard. This wizard provides a simplified method for creating
derived Activity Drivers. These are Activity Drivers with values that are computed from
other Activity Drivers using rules.
• New options on Export Dimensions screen (4577)
In the Export Dimensions tab of the Export function, there are additional facilities for
selecting items in the hierarchy trees. These options are available on the right-click context
menu:
• Select All - selects all the items in the tree
• Clear Selection - clears the selection (this can also be achieved by clicking
anywhere at the side of the hierarchy)
• Invert Selection - will select the opposite of what is already selected
• Select All Leaves - selects all the leaf-level items in the tree. You can then use
Invert Selection to select all the consolidated members.
8.1.4 Book Building
• Data Explorer (4078, 4317)
A relational data view is now available in EPO called Data Explorer. It allows Model
Builders and Book Builders to create tabular views of data records with selection features
that enable specific data values to be targeted easily. These views can be stored as
layouts for future use and for incorporating into books. A book can contain multiple Data
Explorer layouts if required.
• Advanced color formatting introduced for the grid and report controls (4642)
Advanced formatting options have been introduced for coloring the cells in grids and
reports in EPO. Range-based formatting (the ability to color the foreground and
background of a cell depending upon the value) has been available for some time in EPO.
This has now been extended so that a user may setup coloring for individual
columns/rows, grid-values and formulas.
• Hotspots for images in books
Hotspots can be added to images in your books that allow you to jump to another book,
just by clicking on the hotspot. A hotspot can be used to link to books in the same model
or another model. The link will become effective when viewing the image in a published
book.
• Grid popup menu changes (4418)
A number of changes have been made to the Grid Data right-click context menu. This will
make the functions clearer to use, while unnecessary functions have been removed.
• View Builder “Design” tab (4060)
To clarify the difference in functionality between the design and view modes of the View
Builder screen, the caption for the Grid tab has been changed to Design.
8.1.5 EPO Data Loader – Oracle Edition
• Model Converter facility (4349)
The Oracle Data Loader packages have been provided with the additional facility to load
existing model data into Staging Table format. This enables the model data to be
transferred into Oracle tables ready to be loaded into a new model.
30
Page 31
8.1.6 EPO Console
• Parameter for password entry (4840)
A new option has been added to EPOConsole Wizard called Encrypted Password, to allow
an encrypted password to be held in the EPO Console command file. This enables EPO
Console to be run in an environment where it is preferred that user passwords are not
stored as plain text.
8.1.7 MDX Connector
• OLE DB for OLAP replaced
The ODBO (OLE DB for OLAP) process has been replaced by MDX Connector. All
previous ODBO functionality is now provided by the MDX Driver.
8.2 Fixed Issues
The following is a list of fixes released in version 2.4.0 within Predictive Planning / Activity
Analysis.
8.2.1 Setup and Configuration
Business Objects EPO 2.4.2 Release Notes
Changes for 2.4.0
|
• Removing Excel Link for EPO (not supported) (4148)
EPOWeb.xla file was being installed in error with each installation of EPO. File has now
been removed from the installation files.
• IP filter rules were not being saved correctly (4486)
When using EPO Cfg in file mode (i.e. Run | epocfg /file), IP filter rules were not being
saved to ALTransportCoord.ipt, but were incorrectly being saved to .ecf file. Now fixed.
• Install PDF documents and create shortcuts to them instead of help files (4670)
From the Windows Start menu, selecting ALG Software>EPO>Documents was providing
links to the online Help files. This has now been changed to provide links to the PDF
documents.
8.2.2 Administration
• Missing French Translations in Security Descriptors (4388)
In the French version, in the Security Descriptors screens the caption for the Edit
Descriptions button was in English.
Similarly, in the Group/Descriptor Assignment, the security access levels were in English
(Full Access, Edit Data, No Access, etc.)
• In User and Group Maintenance, 'New Model Group' has been renamed to
'Default Model Group' (4287)
'New Model Group' in User and Group Maintenance was a misleading title, as it did not
suggest what the function really did, so the wording has been changed to 'Default Model
Group'. This now correctly suggests that a model group will be assigned by default, rather
the user being able to create a new group.
8.2.3 General
• The 'Manage Properties' option on the Tools menu has been renamed to
'Manage Item Properties' (3989)
This change is to clarify that 'Manage Properties' refers to Item Properties, and not to
something else.
31
Page 32
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.0
8.2.4 Model Building
• Error when creating a specification export file (4661)
This problem was caused when, having created a specification export file for the revenue
table in EPO 2.2.0, the .esp file was subsequently reopened. This error message was
displayed: ‘An error has occurred Error Opening File’.
The error was caused when the file was generated. Export specifications were incorrectly
encoding special characters, like ampersands and quotes, in Item Names.
• Issues exporting ActivityLineItem values to CSV (4509)
An export of ActivityLineItem values from some models produced a couple of issues:
• The export took a much longer time than exporting other results values, such as
CostObjectValue or ActivityCostObjectValue
• The output contained batches of 628 identical records.
Timings and data are now corrected and improved.
• Some models on Windows 32 under Windows 64 run slower (4403)
The paging mechanism was slower when running a 32 bit application. Memory
improvements have been added, also a cacheing fix. Overall there has been a 15%
improvement in calculation times.
• Activity Driver Value not consolidating (4355)
After performing Driver Analysis the Activity Driver Value was not consolidating the parent
value. Now fixed.
• The CSV file is incorrect when exporting TraceBackValue with a filter on RC
item group (4836)
When exporting the TraceBackValue in CSV and filtering on a RC group, duplicated rows
were generated in the CSV file. Now fixed.
• CalculateSlice wizard interface doesn't recognize TARGET values as
parameters (4819)
The wizard for creating a CalculateSlice rule didn't recognize any TARGET (i.e. virtual)
dimensions. This could lead the user to believe that their CalculateSlice rule was invalid,
whereas in fact the slice would be processed correctly. This has been fixed so that:
1) The slice definition now supports Target dimensions for rows and columns.
2) Key values are now correctly identified if they are in Target Dimensions. (Item names
are still flagged if they are valid but from the wrong dimension.)
• Filtering the export of ActivityLineItemValue caused PADModel to crash (4720)
(Fixed in EPO Version 2.3.1 Patch 231-001)
If you tried to export the table ActivityLineItem value with a filter on the Activities or on the
Line Items, Model Builder crashed. The message "Please wait” was displayed, and the
application wouldn’t finish.
• Problem with EPOCodeFromName (4713)
(Fixed in EPO Version 2.3.1 Patch 231-001)
The EPOCodeFromName function appeared to return zero when a variable was passed
into it, but returned the correct result when a literal was passed into it. Item names
containing numbers were being misinterpreted.
• Model not fully calculated (4783)
(Fixed in EPO Version 2.3.1 Patch 231-001)
In certain models, the results were never fully calculated. There was always one
combination of version and period that was not calculated by these two calculation options:
Calculation excluding summary movement values and Reassignment Driver
Calculation Option. If you forced the calculation for a particular combination of version
and period, then a different combination remained uncalculated.
• Models with activity driver rules that reference cross version cost object values
only work on single processors (4662)
(Fixed in EPO Version 2.3.1 Patch 231-001)
32
Page 33
Business Objects EPO 2.4.2 Release Notes
Because a separate thread is used to calculate each Version/Period the system can start a
calculation on a version/period that is based on another version/period that is currently
being calculated, (but not complete) on another processor.
• Issue with Reassignments (4688)
(Fixed in EPO Version 2.3.1 Patch 231-001)
Services were not being reassigned correctly, and incorrect values were being reported.
• Issue with CalculateSlice (4793)
(Fixed in EPO Version 2.3.1 Patch 231-001)
CalculateSlice didn't work correctly with values with TargetActivities or
TargetRespCenters. There were critical alerts when they were executed.
• Load stored values not working (4805)
(Fixed in EPO Version 2.3.1 Patch 231-001)
When transferring data between certain models, the target model cannot load stored
values (ActivityDrivervalue) from the source model. The result is always 0, and 0 stored
values are loaded.
• Value in a rule disappears after the rule is closed and reopened (4671)
(Fixed in EPO Version 2.3.1 Patch 231-001)
This occurred when the negative value -3 was entered in a Detailed Revenue Rule. If you
ran the rule and then closed and reopened the model, the -3 was gone. This only
happened with this specific number. The model alerts reported ‘invalid parameter’.
Changes for 2.4.0
|
8.2.5 Book Building
• Change to totaling to take account of periodic exchange rates (4051)
This problem was caused when a model used a periodic exchange rate. The processing
has been amended so that this will not impact on totals calculations.
The screenshot below shows that prior to the fix, the two line item values of $2000 each,
were affected by the periodic exchange rate so that the total was incorrectly displayed as
$4007.5758.
The following screenshot shows that the total of the two line item values is now correctly
displayed as $4000.
• Error when validating a grid formula of this type: 1/(b-c) (4377)
This issue arose because the formula, when evaluated, equated to 1/0 which is 'infinity',
and was not accepted as a valid formula.
However, the formula accepted brackets if a "+" sign was used instead of a "-". It also
accepted validation when its value was 1/0, when the "-" sign is not used. For example
a/(b+c), where b=0 and c=0, is accepted. However, the formula was not accepted when it
was a/(b-c) where b and c are not zeros.
Identifiers are now set to be random values so that the chances of accidentally evaluating
to give a division by zero are negligible.
• Invalid formula in grid when renaming items (3720)
When renaming an item used in a formula in a grid, the formula became inactive and
displayed the character ( * ) in the grid. Now fixed.
• Change to summary screen on Book Publication Wizard (4518)
33
Page 34
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.0
When a user selects a book to publish and then clicks on Next, the Summary Screen is
displayed. Previously, this screen was Free Text so a user could type anything in, which
could cause problems.
This has now been set to read-only.
• Problem using "Remove low values" option (4631)
In a grid, when using "Remove low values" option with grid values and grid formulas
mixed, all rows disappear when selecting the "Preview" tab. This occurs specifically when
the formula is the item nearest the axis, and the row/column contains a grid value. Now
corrected.
• The page counter was inactive in read-only books (4360)
There was a difference in the page counter between when opening a Book as read-only
then selecting print preview, and when opening the book for editing then selecting print
preview. In the first case it would show as 0/0 and would remain inactive, whereas in the
second case it would show as 1/1. Now fixed.
• DimensionTree object property 'Drop Height' is not displayed in web page
(4641)
When a value was assigned to the property Drop Height in a Book containing a Dimension
Tree object, it wasn’t being reflected when the Book was displayed on the Web.
Also, changes to the Drop Height made in the property or script seemed to be overridden
by the "physical" height of the tree (from when it was last closed) the next time the tree
was re-opened.
• Clarification of cell information (4292)
In View Builder Design Mode, the Grid Data context menu item “Audit Details” has been
renamed “Last Modified”. This is to clarify that this is not related to the optional database
auditing function, but simply holds the time, date and username for the last operation
performed on the selected item.
• Letters not available in Book Builder (4687)
In the Book Builder application, the letters á and é (lowercase and uppercase) were not
available. They are now available again.
• Activitylineitemvalue grid view incorrect in Book Viewer and Web (4844)
In a particular model, the Activitylineitemvalue grid appeared correctly in View Builder, but
in Book Viewer or the web, the activities were not consolidating and consolidated cells
appeared as editable zeros. The problem has been fixed.
• Traceback Consolidation Issue (4785) )
(Fixed in EPO Version 2.3.1 Patch 231-001)
There was a problem with incorrect traceback consolidation for target activities in grids.
The consolidated total was being reported incorrectly.
8.2.6 End User Products
• Removing low values on Web generates duplicated values (4668)
(Fixed in EPO Version 2.3.1 Patch 231-001)
When applying the Remove Low Values option to a grid when using IE for EPO Web,
values are duplicated several times in RC and Period combos, and rows are duplicated
several times in grid.
8.2.7 Data Bridge
• Change to comment inserted by SPE wizard for "Ignore Characters" (4346)
The comment inserted by the SPE wizard for "Ignore Characters" was misleading. The text
was “Ignore any input lines containing specified characters”, which implies the entire line
was ignored, but actually it was only the character.
The text now says “Ignore any of the specified character(s) in input lines”.
• C++ 'Buffer Overrun' crash (4790)
(Fixed in EPO Version 2.3.1 Patch 231-001)
34
Page 35
Business Objects EPO 2.4.2 Release Notes
Importing a small set of data into the CellMemo table via Data Bridge caused the error
“C++ crash in DBUI.EXE”.
8.2.8 EPO Data Loader – Oracle Edition
• Self-referencing parent child records in EPO Data Loader (4343)
Problem when importing hierarchy data that has self-referencing parent child records. Now
corrected by updating constant name.
• EPOLoad install problems (4559)
(Fixed in EPO Version 2.3.1 Patch 231-001)
There was an issue when upgrading the EPOLoad tables on an Oracle database,
specifically with the 210-220 and 210-230 upgrades. This was due to missing fields on the
‘PPLOAD’ series of tables.
8.2.9 EPO Console
• Mappings incorrect when another Alias used with EPO Console (4786)
When EPO Console is used for an export CSV file with an alias different to the default, the
mappings were incorrect. The output is now correct when using both the EPO Console
Wizard and the normal export.
Changes for 2.4.0
|
35
Page 36
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.4.0
36
Page 37
Business Objects EPO 2.4.2 Release Notes
9 Changes for 2.3.1
The following section describes the new features and product amendments that were
introduced in version release 2.3.1 of the Enterprise Performance Optimization suite of
products.
9.1 New Features
There are no new features in the version 2.3.1 release.
9.2 Fixed Issues
The following is a list of fixes released in version 2.3.1 within Predictive Planning / Activity
Analysis.
9.2.1 Setup and Configuration
• Fix to EPO Configure for standalone installs (4558)
EPO Configure in Silent mode was not working correctly.
• Processing problems in multi-user environment with Sockets Communication
(4675)
This problem has been fixed by making the Sockets transport mechanism more robust.
Changes for 2.3.1
|
9.2.2 Model Building
• Performance improvement in Export to CSV for a consolidated set of period
results (4552, 4576)
The time it takes to export results for consolidated periods has been speeded up.
• Sockets transport mechanism caused Model Calculation Options to be ignored
(4630)
When EPO was installed using the Sockets Communication method, any previously
created models appeared to have all the Calculation Options selected (regardless of any
previous settings) and all the Calculation Option settings were ignored.
• Hierarchy items sometimes ignored on import (4595)
In a model with a hierarchy structure involving several levels of parent (or 'group') items,
the members of the attribute structure were not always imported correctly. It was found
that the bulk import routines did not cater for one specific combination of item: attribute
type '14' (for more information on Attribute Types see the 'Data Bridge User Guide').
This problem only affected the bulk import procedures in version 2.2.0 onwards.
37
Page 38
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.3.1
38
Page 39
10 Changes for 2.3.0
The following section describes the new features and product amendments that were introduced in
version release 2.3.0 of the Enterprise Performance Optimization suite of products.
10.1 New Features
The following is a list of new features released in version 2.3.0 within Predictive Planning / Activity
Analysis.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.3.0
|
10.1.1
• Option to replace DCOM with TCP sockets (3830)
EPO is no longer dependent on using DCOM for inter-machine communication, since the option to use
TCP sockets is now available. This option will provide an alternative foundation for development and
installation of EPO’s network communications. This gives users a mechanism that allows the flexibility to
use specific ports, and is easier to implement across domains, access through firewalls and to use with
NAT (Network Address Translation).
Inter-machine communication with the various EPO services can be secured through the use of IP
based filters that provide the ability to write rules which deny or permit access for each individual service.
For details of the installation procedures required to use TCP sockets, please refer to the EPO
Installation Guide.
• Microsoft Windows 2003 Server Release 2 supported
The EPO suite of programs now supports Microsoft Windows 2003 Server Release 2.
• 32-bit EPO supported on Microsoft 64-bit Windows
We now support the EPO suite of programs running as a 32-bit application in a Microsoft 64-bit Windows
environment. The EPO suite will still appear as a 32-bit application.
• Early authentication checks for SQL scripts (4415)
When running the SQL scripts to create the database schema during installation of the EPO database, a
message is now popped up, that will give an early indication of whether there are any problems with the
credentials provided for the machine name, database name, user name and password.
This will be helpful if the user is not quite sure which is the correct password or machine name etc. as it
will avoid the frustration of waiting for the script to finish, before finding out there is a problem.
Setup and Configuration
10.1.2
• New model calculation options (4409, 4411)
Four additional Model Calculation options have been added. These may be selected to speed up the
retrieval of high level cost object values during a full EPO calculation. By excluding lower level cost
object values from the calculation where they are not required, this can make calculation time up to twice
as fast.
The Model Calculation Options screen is selected from the Model menu.
Model Building
39
Page 40
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.3.0
The new options that have been added are:
• Calculation excluding summary cost object values – when selected the model calculation
will exclude Summary Cost Object Values (i.e. Cost Object values summarized at total Activity
and Line Item level) from the cost object calculations. All other cost object values will still be
calculated.
• Calculation excluding line item cost object values – when selected the model calculation
will exclude Line Item Cost Object Values (i.e. Cost Object values summarized at total
Responsibility Center and Activity level) from the cost object calculations. All other cost object
values will still be calculated.
• Calculation excluding activity cost object values – when selected the model calculation will
exclude Activity Cost Object Values (i.e. Cost Object values summarized at total Responsibility
Center and Line Item level) from the cost object calculations. All other cost object values will
still be calculated.
• Calculation excluding total cost object values – when selected the model calculation will
exclude Total Cost Object Values (i.e. Cost Object values summarized at total Responsibility
Center, Line Item and Activity level) from the cost object calculations. All other cost object
values will still be calculated.
For more detailed information on these values, please refer to the EPO Reference Guide.
10.1.3
• ActiveCalculateSlices (4310)
A new function is available which can be used to avoid contention issues between successive
CalculateSlice calls in multi-processor environments. You may wish to arrange for several slices to be
calculated in advance of using the books that display their consolidated values. Slices are dealt with one
at a time in a single processor environment, but this is no longer true when multiple processors are
performing these calculations, and can lead to contention problems. Some slices will calculate without
intruding greatly on the performance of others, but others will have a detrimental effect. In these
circumstances you can separate out those that conflict by using the EPO function
ActiveCalculateSlices.
This function returns the number of active CalculateSlice function calls that are currently being
processed. ActiveCalculateSlices can be used in polling loops in the Capacity Rule that is organizing
your CalculateSlice requests. You would place these between any conflicting slices to ensure they
obtain their optimum performance. For further information and examples, please refer to the EPO User
Guide and the EPO Reference Guide.
Book Building
40
Page 41
10.2 Fixed Issues
The following is a list of fixes released in version 2.3.0 within Predictive Planning / Activity Analysis.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.3.0
|
10.2.1
10.2.2
10.2.3
• Check license for appropriate OS (4435)
When a user logs in the EPO Server tests the license is correct for the Operating System it is running
on.
For users migrating from a different operating system, please note that it will be necessary to contact the
ALG Software Helpdesk for new serial number(s).
• EPO User Help updated (4026)
The online User Help and Reference Guide are now up to date in English for Predictive Planning /
Activity Analysis. The Help files are now in line with the EPO User Guide and EPO Reference Guide
documents.
• Importing XML with zero value lineitemvariability causes fixed/variable problem (4438)
In a model with no LineItemFixedValue records and some zero value LineItemVariability records, when
the XML is imported no records are inserted into the PP_LINEITEMFIXEDVALUE table but the zero
records are inserted into the PP_LINEITEMVARVALUE table. The effect of this is that when viewing the
fixed and variable values in the grid EPO identifies that there is a value in the Variability table and
displays it, resulting in a fixed and variable value of zero.
This has been fixed so that EPO recognizes that the variability record is zero and does not import it into
the table. Since there is no variability value EPO sets variability to 100.
• Problem of "Primary Activity Driver" context and problem of refreshing Primary Driver
Volume values (4416)
When applying the context "Primary Activity Driver" in a grid, EPO displays no Activity Driver in Preview
tab.
Also, Primary Driver Volume values are not refreshing properly when changing the Activity Driver Values
(for child items and consolidation).
These problems have now been fixed.
• The new database initialization scripts are incorrect for the Book Security Descriptor (4384)
When a new model is created in a new database, the access level for the Everyone group was incorrect
for the security descriptor, Book Security. The Access Level defaulted to Edit Data and this has been
corrected to be View Only.
• XML import of model containing aliases doesn't create alias, duplicates dimension members
(4425)
Problem fixed by including code that will map the XML parent child records to their default aliases as
defined in the XML file.
Setup and Configuration
General
Model Building
10.2.4
• Copy grid with headers gets exponentially slower with larger grids (4217)
• Copy from grid pastes rows onto alternate lines (4376, 4405)
If you copied a multi-line set of cells from a grid or book then pasted them into an EPO grid or book, or
another application (e.g. Excel, Notepad), they would be pasted onto alternate rows, leaving a blank line
or zero values in between. Also, 'Copy with Headers' was taking a lot longer than a straight copy, due to
the way memory was managed for large strings.
The way that memory is allocated has been changed to reduce the amount of memory allocations,
reallocations and copy memory operations, and the problem has now been fixed.
Book Building
41
Page 42
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.3.0
10.2.5
• Problems when executing Alias packages (4369)
When executing the Alias packages, primary key violation and execution error have been reported. The
problem has now been fixed.
• No documentation for upgrading EPO Data Loader (4408)
The documentation (EPO Oracle Database User Guide) did not mention the upgrade process for the
EPO Data Loader. This procedure is now included in the document.
EPO Data Loader – Oracle Edition
42
Page 43
11 Changes for 2.2.0
The following section describes the new features and product amendments that were introduced in
version release 2.2.0 of the Enterprise Performance Optimization suite of products.
11.1 New Features
The following is a list of new features released in version 2.2.0 within Predictive Planning / Activity
Analysis.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.2.0
|
11.1.1
• Database Upgrades
There have been significant changes to the database scripts for Release 2.2.0. Therefore to avoid
database errors, please ensure that these are executed exactly as specified in your Database User
Guide. It is also important to check the Rebuild log files for errors at each stage before proceeding to
the next set of scripts.
• Microsoft SQL Server 2005 supported
The EPO suite of programs now supports Microsoft SQL Server 2005.
• Database Auditing (3996)
An audit trail facility is now provided in the form of database audit tables which hold details of every
record inserted, updated or deleted. The audit tables are available for both Oracle and Microsoft SQL
Server database schemas. A full description of the audit tables is available in each of the Database
User Guides.
Auditing will only take place if this option is selected during EPO configuration. Auditing can then be
enabled for individual models at creation or by modifying at a later date.
• Web Client Installer
Included with version 2.2.0 is a new program that is designed for use by System Administrators to
provide a means of installing the EPO ActiveX web toolbar object without the necessity for the
installation to be performed by the client from within the web browser.
There are several benefits to using the installer program instead of the web download method. These
are:
Setup and Configuration
• The installation can be automated using a method such as Microsoft's System
Management Server. This type of program can also distribute the executable to all the EPO
clients at a convenient time.
• The client machine can be updated with the correctly-versioned control before they require
access to the EPO web books, thus reducing inconvenience.
A centrally-controlled roll-out of the installation will ensure that there is consistency of software
•
versions amongst the client community.
To install the program on the client simply run the executable WEBVIEWERSETUP.EXE that is located
in the 'Additional Installers' directory on your current EPO software CD.
11.1.2
• Security changes for Model Builders (3984)
In order to improve security the number of features controlled by descriptors has been increased and the
default privileges of the Model Builders group have been reduced.
A reduction in the default privileges for the model builders group means that access to models and the
dimensions within those models can be controlled on a user by user basis. This will allow several model
builders to work within the same system without being able to open each other’s models or to work
within the same model without being able to view or change selected information or make or change
selected assignments. Prior to these changes this was not possible as Model Builders had full access to
all aspects of all models.
Administration
43
Page 44
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.2.0
The default access for Model Builder will continue to give full access to all models. Upgrading an existing
database to 2.2.0 level will leave any prior security settings unchanged, except for two security
descriptors. The affected descriptors are as follows:
Descriptor Model Builder - New Default
Security descriptor security
Data Alias Management security
These new defaults can be changed if required.
By default, Model Builders will not have full access to Maintain Users and Groups menu but will have
access to the Group / Dimension Security and Default Book Assignment options. This is to prevent a
model builder from changing their group membership or altering descriptor access levels and so
potentially changing their overall level of access. Only members of the administrators group can fully
administer users and groups and their associated security. To further improve security, only
administrators now have access to the security tab on the Model Administration screen.
By default all models will still be accessible to all model builders unless they choose to implement the
new security. This is done by allocating a new user setting called “New Model Group” to individual model
builders. Once a model builder has been assigned a “New Model Group”, any new models subsequently
created by that model builder, may only be accessed by users that are also members of the same group.
Note that the act of allocating a “New Model Group” to a model builder does not automatically make the
user a member of that group and they will need to be assigned to it manually. The model security access
will remain associated with a model, regardless of whether it is copied, and this may only be amended
by an administrator. Therefore model access is no longer enabled solely by membership of the model
builders group.
Several new Security Descriptors have been created. These control the ability to open models,
administer users and groups and to access the assignment screens. Since these descriptors are new to
this release, permissions for all groups will default to the following settings (where FA is Full Access and
blank is No Access):
View only
No Access
Security Descriptor Admin Model
Builder
Resource Drivers
Assignment
Responsibility
Center / Activity
Assignment
Activity
Reassignment
Cost Object
Assignment
Open Models
Maintain Users and
Groups
FA
FA
FA
FA
FA FA FA FA
FA
Book
Builder
End
User
Everyone
Other
• Security Descriptor Security and Data Alias Management Security descriptors changed from
model specific to system wide
Levels of access to the descriptors Security Descriptor Security and Data Alias Management Security
could previously be set individually on a model by model and group by group basis. This has now been
simplified so that levels of access to these two descriptors are consistent across the entire system whilst
remaining specific to groups.
The new default level of access to these descriptors will default to View Only for Security Descriptor
Security and No Access for Data Alias Management Security in a new database and will change to these
levels from prior settings when a database is upgraded. This is true for all groups other than the
Administrators group who will retain the Full Access level to both. This better reflects the altered and
44
Page 45
Business Objects EPO 2.4.2 Release Notes
dominant role of the administrator in setting system security and resolves the issue of rationalizing
different levels of access in different models.
• Database Auditing (3996)
When creating a new model, database auditing may be enabled (providing that the option was also
selected during EPO configuration). Auditing can also be enabled / disabled for existing models via
Model Administration. Database Auditing provides an audit trail facility in the form of database audit
tables which hold details of every record inserted, updated or deleted.
• System Information Utility
A new tool EPO System Information is available to display information about the current status of the
EPO system. This utility brings many of the functions that are available elsewhere in the suite, and
which are of particular use to Administrators, into a single easy-to-use application.
Administrators can use this tool to check that the EPO system has all of the correct software installed,
and to manage users and models. The tool can also be used to produce detailed or summary reports
which may be requested by ALG Helpdesk to troubleshoot an issue or request.
See the new document EPO System Information for more information on this utility.
• When deleting a model, option to also delete associated grids and audit files (3866)
When deleting a model, the user is now asked if they also wish to delete all the model’s Audit records
and/or Views.
Note that it is still possible to delete individual layouts from your file store, using the Delete option in
View Builder / Load Layout, or to delete layouts from the database.
• Restricting ability to delete security alert records (3981)
Model Builders are now restricted from access to the Model Security tab and so cannot delete records.
Only the inbuilt administrator or a user who is a member of the Administrators group can view the
Security tab of the Alerts screen and therefore have access to the Delete Alerts buttons.
Changes for 2.2.0
|
11.1.3
11.1.4
• Accessibility
A number of changes have been introduced to areas of the EPO suite that will facilitate keyboard access
to functionality as an alternative to the mouse.
For further details of these keyboard actions and shortcuts, please refer to the PP User Guide.
• CalculateSlice function (3790)
A new function called CalculateSlice is available that should be called in Capacity Rules to preconsolidate slices of the model for a specific GridValue. This will allow grids that display slice values to
perform efficiently. However, note that this function returns results for every combination calculated,
including zero values. It should therefore be used with care, as it may produce very large numbers of
results.
It is strongly recommended that you discuss usage of this function with your ALG Software consultant.
• EPOCodeFromName function (3976)
The EPOCodeFromName will return the EPO Code of an item (or 0 if it is invalid). This will be very
useful in producing quick Item Property code values.
General
• Toolbar items have a keyboard shortcut (4092): In Model Builder, Book Builder and Book
Viewer, there is a new option in the View menu to Show all Menu Captions. This feature
alters the display of any toolbar items that are normally displayed solely as an icon, so that their
caption and keyboard shortcut are permanently on view alongside the icon. This enables
toolbar items be accessed by keyboard shortcuts.
• Numbered book list: In Book Viewer and the Web, the dropdown list of available books will
indicate a number for each book. This will allow books to be accessed by using a numerical
keyboard shortcut.
• Book access with keystrokes: Keyboard actions are available to set focus on the first
available control in the book. From there, it will be possible to move around the controls and
grid cells by using keystrokes.
Model Building
45
Page 46
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.2.0
• XML Import – speedup on Parent-Child (3854)
Import from an XML file is now faster, by using the same Parent_Child_Bulk load routines as Data
Bridge.
• Model speedups (3957, 4004)
Model calculations have been speeded up.
• Re-usable Export Specification File (3915)
The Export Specification file (.esp) is now re-usable across multiple models, by using the item name for
dimension members rather than the EPO ID.
Old specification files may still be used in the new 2.2.0 version of software. However, files created in
2.2.0 will not work with release 2.1.0 or older.
• Filtering includes alias names (3767)
When using a filter, the test string you specify will now be applied to all alias names in your hierarchy,
regardless of the primary alias. This will speed up filtering in large hierarchies. However, the resulting
filter hierarchy may include items with names that do not contain the characters you have specified,
although one of their alias equivalents will. (Note the EPO Code group is not included in filtering, but if
you need to locate items in the EPO Code group, you can do this by typing EPO followed by a number.)
• The PrimaryActivityDriver functions in Microsoft VBScript can be keyed by Version & Period
(3975)
The three ActivityDriver functions, DirectPrimaryActivityDriver, ServiceActivityDriver and
PrimaryActivityDriver are now keyed by Version and Period.
• Extra message to be displayed during Import (4028)
During import, an extra message will be displayed on the import dialog. While the XML validation
process is in operation the user is informed what is happening by displaying a message ‘Validating
XML’. This initial message will only appear near the beginning of fairly large imports.
• Security added to selections in Assignment Screens (4141)
Security has now been applied to the process of assigning and reassigning activities, costs and drivers.
The ability to create, amend or delete assignments in the appropriate screen will depend on a user’s
access to specific dimension elements relevant to the assignment.
Security access is determined for each type of assignment as listed below:
Type of Assignment / Reassignment Dimension determining security
Resource Drivers Assignment Line Items/Services
Resource Drivers Assignment Overrides Version, Period and Responsibility Center
Responsibility Center / Activity Assignment Activities and Responsibility Center
Activity Reassignment Activities and Responsibility Center
Activity Reassignment Overrides Version and Period
Cost Object Assignment Activities/Line Items/Services and Responsibility
Center
Cost Object Assignment Overrides Version and Period
In order to see assignments a user will need View Only or Edit Data permission on all of the dimension items that
comprise an assignment or reassignment. In order to be able to create or edit assignments or reassignments
then Edit Structure of Full Access permission is required.
11.1.5
• Text Properties in books may be set without selecting text. (2988)
Previously, the Property Editors dealing with Text only had an effect either when some text was
selected, or at the start of a new blank book where no text had yet been typed. Text Property
adjustments, made via the Property Panel have now been brought into line with text editors such as
Microsoft Word. Thus:
Book Building
• When the cursor is on some text, but none is selected, the current word (or unbroken block of
text) will be affected
46
Page 47
Business Objects EPO 2.4.2 Release Notes
Changes for 2.2.0
• When there is no text at the cursor position, adjustments will be applied to any text typed from
that position.
|
11.1.6
11.1.7
11.1.8
• Security Alerts (4032)
A user logged into either the Web or Book Viewer will now be reported as an ‘End User’ in the Security
Alerts screen, EPO Monitor and EPO System Information.
• Added support for Lookup fields in Wizard (4007)
Lookups are no longer stripped out of the Data Bridge wizard.
• Timestamp and associated deletion procedures
A new column for a timestamp has been added. This will hold the time that the record was imported to
the Staging Tables. Associated clean-up procedures for the Staging Tables area are also available to
delete records depending on their import date.
For further information, please refer to the EPO Oracle Database User Guide.
End User Products
Data Bridge
EPO Data Loader – Oracle Edition
11.2 Not Supported
11.2.1
End User Products
From Release 2.2.0, EPO Excel Link will no longer be a supported product, as it has been replaced by
the ODBO Link.
11.3 Fixed Issues
The following is a list of fixes released in version 2.2.0 within Predictive Planning / Activity Analysis.
11.3.1
11.3.2
• Model Delete speed-up
The Oracle database stored procedures for deleting models have been optimized for performance.
• Copy Model does not copy Item Properties (4043)
Scripts amended to resolve problem.
• In French version, Properties screen in EPO Console Wizard is out of line with commands
(4115)
In the French version, there were two commands to create a new model, whereas there is only one
command in the English version. Thus the parameters did not match with the appropriate commands.
This has been corrected by replacing the two commands with one.
Administration
Model Building
• Some Consolidation subtotals are calculated incorrectly (4218)
This fault was fixed by correcting a lock problem that could affect consolidation of Revenues.
• Divergent Errors (4170)
47
Page 48
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.2.0
Error message 'Excessive reassignment split detected'-'A reassignment split >100% for a target Activity
that itself is reassigned' appearing. Problem corrected by handling negative converging reassignments
so no divergent messages are output.
• Reduce the excessive number of Activity Split Values warning messages (4145)
Divergent alerts are no longer displayed where the total of the Activity Split Values is very near to zero.
• Duplicate hierarchy in the Versions dimensions after import (4164)
Caching problem has now been resolved.
• Bulk Import – Unique Constraint Violation Error (4210)
EPO Data Loader scripts amended.
• When adding a item to a dimension, using a name that already exists, the edit box is not
cleared (4165)
When adding a new dimension item that was rejected because it was the same as a reserved name e.g.
‘Revenue’, the edit box was not being cleared. Therefore when an alternative name was entered, this
was saved incorrectly. This problem has been corrected.
• Problem of importing PARENTCHILD table having attributes (4034)
Import did not correctly reinstate the relationship between a child item and its associated attribute, after
one of them has been deleted. This fault has been fixed.
• Deletion of Resource Driver Group sets unrelated costs to unallocated (4142)
Some Resource Drivers were deleted that were no longer used in any assignment tables or rules. The
costs in certain responsibility centres then became unallocated, even though the deleted drivers were
not used by these responsibility centres in their assignments. This fault has now been fixed.
• When using Copy Versions function, the Resource Driver Overrides are not copied (4155)
SQL routines updated to fix fault.
• Problem of exporting the ActivityLineItemValue table in CSV when filtering a group of
activities (parent) (4118)
When exporting the ActivityLineItemValue table in CSV format and filtering a group parent of activities,
duplicates were being generated for each combination. This has now been fixed.
• Spare Resource split is not consolidated (3480)
The Spare activity is in the activity group « Total ACTIVITES » with consolidation type + (Add). This
problem arose in specific circumstances and has now been fixed.
• Traceback records not being exported (4075)
If you assign all line items to direct to cost object then no records are exported if you export the
TRACEBACKTABLE. This fault has been fixed.
• When importing an XML into EPO the abort button works but the Esc does not (4023)
This has been fixed: the import can be aborted either by clicking the Abort button or pressing the Esc
key.
• Access violation error when opening Export window (3960)
If you open the Export window and load a spec file, change it, then run it. Next time you try to open the
Export window you get an access violation error, unless you close the application and re-open. This fault
has now been fixed.
• If a user does not have access to items in the period or version hierarchy menu items are
incorrectly displayed (4179)
This has now been fixed.
11.3.3
48
• Trees on Web and Windows not showing same results (4031)
In Windows (Book Viewer), when the user had no security access to a parent level item, the dropdown
menu was still displaying the child items, which was incorrect. However, the web gave the correct result
by not showing the child items. Thus it appeared that trees on the web and Windows were showing
different results. The problem in Windows has now been fixed by preventing the child items from being
displayed when the user does not have access to the parent.
• Parent attributes are not expandable within a Dimension Tree that is set to Replace With
Keys
Book Building
Page 49
Business Objects EPO 2.4.2 Release Notes
Changes for 2.2.0
When a Dimension Tree is used to control a keyset that defines a grid's layout it was found that an
attribute group could not be expanded to show the leaf attribute items. This has been corrected so that
leaf level attribute items should be visible.
• Book mark going back up a page does not work (4206)
When navigating up to a Bookmark higher up in the same Book, the application was scrolling up to the
Bookmark then down a few lines which took the Bookmark back out of view. This has now been fixed.
• TargetCostObjectValues taking too long to display (4084)
This has now been fixed.
• EPO Error when dropping a book inside a table. (3871)
To create a hyperlink, you can drop a book from the books hierarchy to the page. If you drop the book
inside a table cell, it caused an EPO framework error and no hyperlink. This problem has been fixed.
• Error TRVautoTableInfo.SetSubjet when opening a book (4020)
The problem is caused because the data view has no rows and no columns. The fix is to make reports
behave in a similar way to grids. This resolves the problem of opening a book that contains a control
based upon a grid that does not have either rows or columns.
• Getting unnecessarily asked to save layout when 'No' would have just been selected. (3964)
In View Builder, if you first selected 'New Layout' and then ‘No ‘when asked if you want to save the
layout, followed by 'Load Layout' , you would be asked again if you want to save changes. This was
unnecessary, since no changes had been made, and the fault has been fixed.
|
11.3.4
11.3.5
• Web cache speedup
The speed for caching of web values has been improved.
• Changing user password through the web failed (4045)
If a User’s properties were set to ‘User must change password at next login’ or the password expired,
Internet Explorer would hang after the user logged in. This has been corrected so that the user will be
prompted to changed their password and be presented with a dialog box to do so.
• Book property 'Top Item' for Target Responsibility Center is showing as "unavailable" in a
web book (4171)
The 'IsVisibleItem' call was failing for items from the SourceActivity and SourceRespCenter dimensions.
This has now been repaired.
• Datamanager.activate() and Datamanager.deactivate() not working (3659)
The datamanager.activate() and datamanager.deactivate() functions did not appear to work in a model
on the Web. This has now been fixed.
• Attempting to change about to expire password when prompted during web login causes
error message (3635)
During web login, if date related 'change password at next login is set' in user properties, and the user
accepts the option to change password when prompted by system, this triggers an error message. This
has been fixed.
End User Products
Data Bridge
• Cannot import a CSV file which has 750 plus characters across all columns via Data Bridge.
The maximum line length has been increased to allow more characters.
11.4 New Documentation
The following new documentation was released in version 2.2.0 within Predictive Planning / Activity
Analysis.
49
Page 50
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.2.0
11.4.1
This document describes the new utility EPO System Information (see 11.1.2)
EPO System Information
50
Page 51
.
12 Changes for 2.1.0
The following section describes the new features and product amendments that were
introduced in version release 2.1.0 of the Enterprise Performance Optimization suite of
products.
12.1 New Features
The following is a list of new features released in version 2.1.0 within Predictive Planning /
Activity Analysis.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.1.0
|
12.1.1
12.1.2
12.1.3
• EPO Data Loader
The EPO Data Loader can be used to transfer dimension hierarchy structures and data from
various data sources (files or databases) to intermediate loading tables, then transferred very
rapidly into EPO tables.
See the new document EPO Oracle Database User Guide for more information on this
feature.
• Configure EPO silently
We have extended the EPO Configure program to run silently so that a configuration file
created with the /FILE switch can be passed as a command-line argument to silently configure
EPO Servers. This option is particularly useful in conjunction with the EPO Silent Install
program (currently undocumented, but available on the release CD).
e.g EPOCFG.exe /FILE "C:\MyConfiguration.ecf"
• Single Sign On
The Single Sign On feature presents users with a single sign on to the system, thereafter
subsequent security checks will use the given security information, rather than prompt the user
to log in again.
Single Sign On is available using Windows NT Security, Oracle COREid, LDAP, or Active
Directory based security. It will be possible to select the required EPO Single Sign On Type
and EPO Web Single Sign On Type during EPO Configuration.
The Single Sign On functionality is available under individual license.
General
Setup and Configuration
Administration
12.1.4
• Export to Database
The Export to Database function is available under individual license.
Changes have been introduced to the Export functionality, allowing results tables to be written
to a database, rather than being written to a flat file. This is available for both SQL and Oracle
databases.
There is also a facility to export to database via the EPO Console. This allows the console job
to be scheduled overnight and so avoid affecting day-to-day performance. For further
information, see the EPO Console User Guide.
• Import and Export screens separated
Model Building
51
Page 52
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.1.0
The Import and Export functions have been given separate screens. This is intended to clarify
which functions are available during the two separate operations, and now includes an
improved progress and information bar for users to track how far the operation has proceeded.
In addition, the Abort function is now more responsive should an import or export be cancelled.
• Export of LICOSTOBJECTVALUE table enhanced
The export of results has been improved for the LineItemCostObjectValue table.
• New selection features in Export Dimensions screen
Users can now Expand All and Contract All items in the Export Dimensions hierarchy listing, as
well as Select All items using new options in the right-click context menu.
• Version / Period CostObject Assignment Override
New functionality has been added to Cost Object Assignments to allow overrides to be set by
Version / Period.
• Model Calculation Options
Model Calculation options may be selected to optimize calculation performance time and
results table size.
• Item Properties
Item Properties have been added to EPO. These will allow the model builder to assign userdefined values to individual items in a dimension and then refer to these in the rules. A series
of predefined properties will allow some internal functions to be added (such as previous and
next).
Three new functions are available in EPO:
• LeafPosition – the order of a leaf item in a dimension
• CodeByLeafPosition –the EPO Code of the supplied Item +/- an offset, i.e. lead and
lag
• ItemPropertyValue
• Improvements to make dimension hierarchies easier to use
Substantial work has gone into making the dimension hierarchies faster, and easier to work
with. Hierarchies will now display more quickly, and will scroll through large hierarchies
smoothly. Also, the insertion, deletion and movement of hierarchy items has been improved to
make them faster and more reliable.
12.1.5
• Third-Party Control Enhancement
EPO uses the latest versions of a third-party web control that offers significant speed-ups in
terms of formatting times. This greatly facilitates rendering Books for display on the Web.
• New PDF System
EPO no longer uses the EPO printer driver to generate PDFs. Instead, it uses a PDF
generator that has been integrated within the EPO applications. This should result in more
satisfactory PDF production.
• Adobe Acrobat 7.0
Adobe Acrobat versions 6.0.4 and 7.0 are supported by EPO Web User and BookViewer
applications.
• ProClarity v.6.0
ProClarity v.6.0 Maintenance Release 1.0 is supported by EPO.
End User Products
12.1.6
52
• Shows the path of current services
The Service Manager application has an extra column that displays the path to the file that
relates to the EPO service. This makes it easier for Administrators to cross-check version
information.
EPO Service Manager
Page 53
12.1.7
• Replace option for Cost Object Drivers
The REPLACE Option is now available when loading Cost Object Drivers via Data Bridge.
Data Bridge
12.2 Fixed Issues
The following is a list of fixes released in version 2.1.0 within Predictive Planning / Activity
Analysis.
Business Objects EPO 2.4.2 Release Notes
Changes for 2.1.0
|
12.2.1
12.2.2
• Database sessions not being cleared immediately from the database (3696, 3705,
3711)
Database sessions are now cleared in a timelier manner.
• The application server does not load any Revenue values from the database (3873,
3860, 3834)
When an existing model is loaded for the first time all Revenue figures stored in the database
were being ignored. This has now been resolved.
• The currency name for ZAR should be "South African Rand" (3797)
Corrected for this release.
• Need to make Reassignment calculation handle larger models (3595)
EPO v2.1 can now handle large models with complicated reassignments and produce results in
much less time than previous versions.
• Could create but not run a Console Wizard script if user was not a Local
Administrator (3735)
In previous versions use of the Console Wizard was restricted to the built-in Administrator user.
This has now been extended to all EPO users.
• French installation Cancel message appears in English (3385)
When the French language is chosen for installation the ‘Cancel’ button remained in English
during the installation. This has been changed to show ‘Annuler’.
• Report Manager warning label too short (3786)
In the configuration program, if the LocalSystem account is chosen when configuring the
Report Manager account, then the text label truncated the warning text. This has been
amended so that the text fits whichever account name is chosen.
General
Setup and Configuration
12.2.3
• Alerts (3536)
The User Preference that specifies Model Alert Page size is no longer valid as the paging
feature has been removed. This option has therefore been removed from User Preferences.
• Cannot assign users to attribute groups in Group/Dimension security screen (3781)
This facility has been enabled and attribute groups are now visible and can be chosen for user
assignments.
• Using the keyboard Delete button when renaming a Data Alias invokes Delete Data
Alias functionality (3226)
In Manage Data Aliases, while renaming an alias, if you press the keyboard Delete button (to
delete a character), this will take you into the Delete functionality. This key now correctly
removes the previous character as intended.
Administration
53
Page 54
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.1.0
• ResourceDriverPctSplit data appears to be editable when version is locked (3714)
This was an oversight in the locking mechanism that has been resolved for this release.
12.2.4
• Leaf item in new group (3613)
When creating a group level dimension item by adding a child, the method for naming the
additional leaf level item that is generated has changed. Formerly, where the group was
named ITEM, the leaf level item would be named ITEM (Detail). In future, the leaf level item
will now be named ITEM Detail (note that the parentheses no longer appear).
• New Standard Currencies (3739)
The list of standard currencies has been updated to include the Yen (Japan), Won (South
Korea) & Yuan (China).
• In-built Activity Driver Values not exported by default (3774)
The two standard derived Activity Driver Values (Revenue Activity Driver and Units Sold
Activity Driver) will only be exported if specifically selected in the Export Dimensions screen.
• Export to .CSV does not use the chosen alias (3869)
If an alternate alias (other than Default) is selected and then data is exported in that alias by
leaving the selected Alias drop down list unchanged (i.e. defaulted to the current alias) then all
objects are exported in the Default Alias. This has been changed to ignore the current state of
the drop-down list selection, and the export now uses the last selected alias, as expected.
• Creating a new Alias and changing the Value field deletes all previous Aliases apart
from EPO Code (3814, 3911,3839)
This was a display issue with the Manage Data Aliases screen. The aliases still existed, but
were not being displayed. This has been resolved.
• Changes to Dimension Names are not being made to the Default Alias (3503, 3795)
When dimension names were changed a corresponding change was not being made to the
default alias. The result of this was that if the alias was changed the new dimension names
would not appear. These two areas have not been linked.
• When importing a model the import sometimes imports twice (3827)
On occasion it took two clicks to close the import window, and between the clicks a second
import would start. The window now responds correctly to the first click on the Close button,
and the import is done only once.
• ‘Import complete’ message appears before the import completes (3674)
Improvements to the progress bar refresh have resolved this issue.
• Erroneous ignored record lines on Rules XML import (3609)
A model with consolidations in the Version or Period dimension would report ignored lines
when model XML was imported. These messages are no longer produced.
• Open model dialog displaying squares in the model description (3844)
Multi-line descriptions contained end-of-line characters that were displayed as squares at the
end of the description line. These have been removed.
• Items in a grid disappeared when using Print Preview Book in Model Builder (3823)
In one instance it was reported that values displayed in a grid were not visible when previewed
for printing. This has now been resolved and values are consistently visible when switching
between grid and preview.
• Exporting a model with a Version rule to XML with the "Includes Rule-based Values"
option EPO fails to export the values (3766, 3738)
This process was taking too long in large complex models, and has been reworked to reduce
export times to manageable levels. This affected other rule-based values that were dependant
upon Version or Period values to calculate.
• Security defaulted to Default Dimension security after import of XML where custom
security had been specified (3692)
Imports now keep the associated security descriptors, as specified.
Model Building
54
Page 55
Business Objects EPO 2.4.2 Release Notes
• Primary Driver Unit rate is not calculated if based upon a Summary Activity value
(3764)
Changes to the calculation of Summary Activity values have resolved this issue.
• Cost Object Assignment Version/Period setting remains after clearing the override
(3707)
In the Cost Object Assignment screen, after clearing a Version/Period override, the override
was cleared however in the Version/Period selection frame the Version and Period selection
was remaining.
• When defining an override for an Direct Activity in the Responsibility Center
Assignments screen the status “implied” is displayed for all RC assignments (3743)
Fixed to display only applied assignments where an association exists between the
Responsibility Center and the Activity.
• Rename Dimension from Source to Target Responsibility Center or Activity fails
(3100)
This now takes into account attribute groups and the correct (renamed) item appears in the
Dimension Tree control.
Changes for 2.1.0
|
12.2.5
• Copying Dimension Trees within a Table (1638)
DimensionTree controls that are linked to a set of Keys can now be copied to a different
location in a Table.
• Values not consolidating correctly upon data entry (3925, 3832)
It has been possible to see incorrect consolidations in a grid after data entry. Changes to the
internal EPO cache system have resolved this issue by clearing all structure and data caches
after a data change.
• View Builder does not close if an amended view is saved with the same name (3926)
This has been fixed so that changed views can be re-saved and the save dialog box will close.
• Changing model when grid builder is open doesn't always close down the grid
builder (3859)
Opening a model with a View Builder open EPO tries to closes down the existing grid, and
prompts for a save. If ‘Cancel’ was clicked EPO opened the Model Admin screen and left the
view open. In v2.1 the view is correctly closed before the Model Admin screen is presented.
• ‘Target’ items not filtered in View Builder Dimension filters (3837)
When any Target items (such as Target Responsibility Center) were filtered using the View
Builder’s filter options then the filtering was not applied to the dimension list.
• Values removed incorrectly when using ‘Remove low values’ or ‘Setup Auto filter’ in
grid (3755)
Summary Activity values were being removed from grids with AutoFilter or Remove Low
Values set when they did not meet the criteria for removal. This has been fixed for this release.
• Incorrect values appearing in the activity driver value field after Driver Analysis
(3758)
Related to issue 3824 (see 3.3.8 below) it was found that Driver Analysis operations were not
resetting some Activity Drivers. This now works as expected.
Book Building
12.2.6
• Model dropdown list in EPODataConnection control ignores security and displays
all models as if user is Model Builder or Administrator (3770)
Security has been re-applied for v2.1 such that the model list is restricted in accordance with
security settings.
• Copying & Pasting values within View Builder grids can cause values to become
un-editable (3637, 3644)
End User Products
55
Page 56
Business Objects EPO 2.4.2 Release Notes
|
Changes for 2.1.0
A copy and paste action on editable values caused the pasted values to display as un-editable
after the operation.
12.2.7
12.2.8
• Only Report shortcuts generated using the Administrator User work correctly (3822)
Report shortcuts created by other users, whether in the Administrator security group or not,
were not being allowed to run due to an incorrect licensing restriction. This restriction has been
removed.
• Cell memos fail to import (3804)
Data Bridge was adding the description of the table field to the specification script which
prevented the import from working as it should.
• Values in the Activity Driver Target Value field in the Activity Driver Value table not
being overwritten by zeros on import (3757, 3824)
In some versions it has been reported that it was not possible to overwrite activity driver values
with zeroes by importing the new values. This has been resolved for this release.
Report Manager
Data Bridge
12.3 New Documentation
The following new documentation was released in version 2.1.0 within Predictive Planning /
Activity Analysis.
12.3.1
Guide
EPO Microsoft SQL Server 2000 Database User
12.3.2
This is a new document, which describes the EPO Database Structure for Microsoft SQL
Server 2000.
This is a new document, which describes EPO Oracle Loading Procedures and the EPO
Oracle Database Structure.
EPO Oracle Database User Guide
56
Page 57
Business Objects Information
Resources
Page 58
A
Business Objects Information Resources
|
Documentation and information services
A1. Documentation and information services
Business Objects offers a full documentation set covering its products and their
deployment. Additional support and assistance are also available to help
maximize the return on your business intelligence investment. The following
sections detail where to get Business Objects documentation and how to use the
resources at Business Objects to meet your needs for technical support,
education, and consulting.
A2. Documentation
You can find answers to your questions on how to install, configure, deploy, and
use Business Objects products from the documentation.
What’s in the documentation set?
View or download the Business Objects Documentation Roadmap, available with
the product documentation at
The Documentation Roadmap references all Business Objects guides and lets
you see at a glance what information is available, from where, and in what
format.
http://www.businessobjects.com/support/ .
Where is the documentation?
You can access electronic documentation at any time from the product
interface, the web, or from your product CD.
Documentation from the products
Online help and guides in Adobe PDF format are available from the product Help
menus. Where only online help is provided, the online help file contains the entire
contents of the PDF version of the guide.
Documentation on the web
The full electronic documentation set is available to customers on the web
from support web site at:
http://www.businessobjects.com/support/ .
Documentation on the product CD
Look in the docs directory of your product CD for versions of guides in Adobe
PDF format.
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is there
something you particularly like or have found useful? Drop us a line, and we will do our
best to ensure that your suggestion is included in the next release of our
documentation: documentation@businessobjects.com.
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts. For information about
Customer Support visit:
http://www.businessobjects.com/ support/ .
58
Page 59
Business Objects Information Resources
Customer support, consulting and training
A3. Customer support, consulting and training
A global network of Business Objects technology experts provides customer support,
education, and consulting to ensure maximum business intelligence benefit to your
business.
How can we support you?
Business Objects offers customer support plans to best suit the size and
requirements of your deployment. We operate customer support centers in the
following countries:
• USA
• Australia
• Canada
• United Kingdom
• Japan
Online Customer Support
The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range of technical
information including knowledgebase articles, downloads, and support forums.
http://www.businessobjects.com/support/
|
A
Looking for the best deployment solution for your
company?
Business Objects consultants can accompany you from the initial analysis stage
to the delivery of your deployment project. Expertise is available in relational and
multidimensional databases, in connectivities, database design tools, customized
embedding technology, and more.
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, we can
offer a training package to suit your learning needs and preferred learning style.
Find more information on the Business Objects Education web site:
http://www.businessobjects.com/services/training
59
Page 60
A
Business Objects Information Resources
|
Useful addresses at a glance
A4. Useful addresses at a glance
Address Content
Business Objects product information
http://www.businessobjects.com
Product documentation
http://www.businessobjects.com/
support
Business Objects Documentation
mailbox
documentation@businessobjects.com
Online Customer Support
http://www.businessobjects.com/
support/
Business Objects Consulting Services
http://www.businessobjects.com/
services/consulting/
Business Objects Education Services
http://www.businessobjects.com/
services/training
Information about the full range
of Business Objects products.
Business Objects product
documentation, including the
Business Objects Documentation
Roadmap.
Send us feedback or questions
about documentation.
Information on Customer Support
programs, as well as links to
technical articles, downloads,
and online forums.
Information on how Business
Objects can help maximize your
business intelligence investment.
Information on Business Objects
training options and modules.
60
Loading...