Business Objects 4.14

We are getting ready for the 4.14 patch/version. Is there anything new we
can expect to see relating to new problems with 4.14 ?

Anthony B. Moore
Front End Development
BellSouth Cellular Corp.
(770) 351-1382
email: Anthony_B_Moore@bscc.bls.com


Listserv Archives (BOB member since 2002-06-25)

Not aware of any problems. Certainly there is an improvement. Earlier
version used to corrupt the complex LOVs when exported to repository,
which is corrected in 4.1.4

– Vasan

We are getting ready for the 4.14 patch/version. Is there anything new we
can expect to see relating to new problems with 4.14 ?


Listserv Archives (BOB member since 2002-06-25)

We just upgraded to the 4.1.4 service pack to fix a bug with Document Agent.
But below are the other bug fixes that this new version offers:

XV. 4.1.4 version

Contents
New in 4.1.4 version
Problems solved in 4.1.4 version

New in 4.1.4 version

New products and features

Products
Rapid Deployment Templates: updated templates and universes and new
universes for BAAN
and Oracle APPS 11.0
Dutch 4.1.4 version
Japanese 4.1.4 version
Italian BusinessMiner 4.1.4 version
DB2 Olap for the French, German, Spanish and Italian 4.1.4 versions

Features
Using BusinessObjects 4.1.4 with WebIntelligence 2.0: Authentication

 If you do not wish to use the Business Objects security and
 authentication method, you must configure the BusinessObjects
 client installation on the ReportServer machine to support the
 use of another authentication method.

 Alternate methods are supported using another a new authentication
 DLL. This DLL is supplied with BusinessObjects 4.1.4

 To change the method for WebIntelligence, you must configure the
 Web Server, and WebIntelligence. Full instructions are contained
 in the Administrator Guide of WebIntelligence.

      Setting Up the Driver

      This section:

         * Describes what to do before you can use the
           WebIntelligence authentication driver,
         * Provides information on the drivers installed with
           WebIntelligence and BusinessObjects, and
         * Explains how to activate and deactivate the
           driver.

      Before You Begin

      First, ensure that you create users with the Supervisor
      with the same user names as in NT or in the Web Server
      Basic Authentication Scheme. Note that there is no need
      to assign passwords to Business Objects users when
      working with the WebIntelligence authentication driver,
      as passwords are not checked if the user names match.
      The password is verified by the Web Server, which thus
      provides the authentication.

      Drivers Installed with BusinessObjects 4.1.4

      Three drivers are installed with BUSINESSOBJECTS, under
      \BusinessObjects:

         * KGLUIDRV.DLL This is the default driver, called by
           the application when using BusinessObjects
           Authentication standard mechanism. To Be used with
           WebIntelligence only if BusinessObjects Security
           is the only one you are going to use with
           Webintelligence 2.0. By Default this is the
           Authentication Driver used when refreshing 4.1
           Document with WebIntelligence.
         * KNTUIDRV.DLL This is the NT authentication driver.
           NOT to be used with WEBINTELLIGENCE 2.0
         * KBOUIDRV.DLL A copy of KGLUIDRV.DLL.
         * KBWUIDRV.DLL This is the WebIntelligence
           Authentication driver. This driver supports any
           Webintelligence Scheme you may select through the
           Admin Panel facility. The supplied DLL is valid
           only for BusinessObjects 4.1.4

      Activating the WebIntelligence Authentication Driver

      The driver is based on the BusinessObjects 4.1 Plug &
      Play security driver mechanism, so all you have to do
      is activate it. To do this:

             1. Delete or remove KGLUIDRV.DLL from
                \BusinessObjects.
             2. Rename KBWUIDRV.DLL to KGLUIDRV.DLL
                in \BusinessObjects installation Folder.

           To go back to the default driver

             1. Delete or remove KGLUIDRV.DLL.
             2. Copy KBOUIDRV.DLL under \BusinessObjects
                to KGLUIDRV.DLL.

Documentation: what’s new in Service Pack 4

Updated Configuring DAS as an NT Service document
This document now contains essential troubleshooting information based on
real-life deployments. It is available in both printed and electronic
formats.

Updated BusinessObjects Developer’s Guide and online help
These documents have been significantly tested and revised. The online help
also contains previously undocumented scripting samples.

New Rapid Deployment Templates Documentations
New guides are available for:

  • Oracle 10.7.
  • PeopleSoft HR 7.5
  • Sales and Distribution, Materials Management and HR for R3 3.x

Enhancement requests
This section lists, per module, the customer enhancement requests that have
been introduced in 4.1.4.

BusinessObjects
Vantive case CS001073468 Bug Number 24094
You should not be able to insert or update tables in a database using the
Free Hand SQL editor of BusinessObjects.
Fixed. You can only use the SELECT command if your user profile is not
“General Supervisor”. Same thing if you work in workgroup mode (no
BOMain.key).

Installer
Vantive case 302035468 Bug Number 24082
You should be able to add the path to the profile file in setup command
line.
Fixed.

Problems solved in 4.1.4 version

This section lists, per module, the customer cases that have been solved in
4.1.4.

Application Development Environment
Vantive case 302046722 Bug Number 25278
When opening a document in read-only mode via ADE, you get an unexpected
error.
Fixed: In ADE you can now manage the Read-Only documents.

BusinessObjects
Vantive case AP13229 Bug Number 21659
Duplicate rows are displayed when the changing sort order.
Fixed.

Vantive case AP17886 Bug Number 21790
Linked OLE objects inserted in your reports are displayed as black images
when saving your documents as .htm and open the resulting .htm in a html
browser.
Fixed.

Vantive case CS10666 Bug Number 22183
When you create a report using a stored procedure data provider and you
select the “Prompt for Value” option, a user is not prompted when he
refreshes a report.
Fixed with limitation: Before you run the report for the first time, you
must enter a value inside the Value text box of the Stored Procedure Editor
dialog box.

Vantive case AP22346 Bug Number 22262
BusinessObjects crashes when creating a user object and getting help on
function. The problem occurs when you edit the formula in the Formula box.
Fixed.

Vantive case AP22400 Bug Number 22266
Bad calculation with negative result using the DayNumberOfMonth(),
DayNumberOfWeek(), DayNumberOfYear(), MonthNumberOfYear(), Quater(), Week(),
and Year() functions.
Fixed.

Vantive case 302048117 Bug Number 22709
If a function contains more than 3 parameters, from the fourth field and
onwards you cannot enter a value inside the User Objects dialog box.
Fixed.

Vantive case 302029943 Bug Number 22812
When converting a 3.1 query using a condition "Query: One Item in version
4.1.x, BusinessObjects crashes.
Fixed.

Vantive case AP27141 Bug Number 23560
Under Windows 95, BusinessObjects crashes when fetching data (about 725000
rows).
Fixed.

Vantive case AP27621 Bug Number 23563
BusinessObjects crashes when running a query from the Query Panel if the
generated SQL script is bigger than 30 Kbytes.
Fixed.

Vantive case 302037448 Bug Number 23721
When openning a 3.1 document in 4.1.x version, variables using objects, name
of which starts with a minus (-), are not correctly converted.
Fixed.

Vantive case SE27186 Bug Number 23845
Depending on universe properties, refreshable option from the Data Manager
purges the data provider instead of not refreshing it.
Fixed.

Vantive case NE26161 Bug Number 23921
Cannot select SQLNet 2.3 for a new connection
Solved in setting the driverge.sbo file’s ‘Oracle_8=’ parameter to ‘SQL*Net
2.3’ instead of ‘Net8 Client’

Vantive case 302040071 Bug Number 24344
BusinessObjects crashes when running a specific query using UNION.
Fixed.

Vantive case 302049402 Bug Number 24429
BusinessObjects crashes when displaying the SQL statement of a query
containing at least two objects referring each other in QueryPanel.
Fixed.

Vantive case 302049399 Bug Number 24434
You get incorrect results in your report when you make calculation on
measures having the same name and coming from the same universe.
Fixed.

Vantive case US30913 Bug Number 24565
Concurrent send of documents to the repository causes an error. If there are
a large number of users and several users send the same document to the
repository at the same time one (or several) users will get a Database Error
22394 Unique Constraint Violated.
Fixed.

Vantive case 302025302 Bug Number 25316
The number of values in an InList condition is limited to “99”.
Fixed.
To change this limit, add the MAX_INLIST_VALUES parameter in the appropriate
PRM file and choose the value needed. The maximum value is 256 and the
default value is 99

Vantive case 302038239 Bug Number 25356
With IBM DB2 MVS and comma set as decimal separator: users cannot see the
list of universes published in the repository
Fixed. A space was added after commas to enable IBM DB2 MVS to recognize
commas as separators.

Vantive case 302037910 Bug Number 26893
Informix-Net only: if BusinessObjects is working in the background and you
press the ESC key, this action is applied to BusinessObjects instead of the
active application.
Fixed.

OLAP Express
Vantive case 302037292 Bug Number 25402
Performances of BusinessObjects against both PERSONAL EXPRESS and EXPRESS
SERVER is a bit slow.
Fixed.
The performance has been improved

BusinessQuery
Vantive case SE26699 Bug Number 23689
@Variables and -var command line option does not work properly with
BusinessQuery.
Parameters can be used now if they are available in the environment
variables or if they are set in BusinessQuery options.
Fixed.

Designer
Vantive case CS10719 Bug Number 24282
With IBM DB2 MVS and comma set as decimal separator: when importing a
universe, the following error appears “Truncating error 22001
[IBM][CLI-Driver] DB2 SQL 0302N”.
Fixed. Same as Vantive case 302038239.

Vantive case 302025068 Bug Number 25145
Exporting a universe could overwrite LOVs belonging to other universes.
Fixed.

Vantive case 302040073 Bug Number 24692
If a table is deleted in a core universe, the joins related to this table
are kept in the derived universe.
Fixed.

Vantive case 302049692 Bug Number 25138
Designer crashes when modifying a join after refreshing the structure.
Fixed.

Document Server
Vantive case 302039784 Bug Number 25317
When you run several tasks at the same time, only one is successful.
Fixed.

Vantive case 302045378 Bug Number 26197
You cannot refresh document containing @prompt object (defined at the
universe level) when changing universe whereas BusinessObjects and Designer
are open.
Fixed.

Supervisor
Vantive case 302031801 Bug Number 24134
Users restrictions are deleted after performing a repair on the security
domain.
Fixed.

Vantive case 302038183 Bug Number 24287
Security hole when disabling universes for a Supervisor-Designer.
Fixed.

Vantive case 302038399 Bug Number 24339
User Definition print-out is not correct for the General Supervisor profile.
Fixed.

Vantive case 302053372 Bug Number 23658
DB2/AS400, Ingres and Teradata: If your table names contain underscore
characters, columns do not appear in the Designer Structure window.
Fixed.


Listserv Archives (BOB member since 2002-06-25)