Release Note

Genesys Interactive Insights

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2010–2011

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
8.0.100.05 [03/28/2011] – General X X X X   X
8.0.001.03 [11/16/2010] – General X X X X   X
8.0.000.32 [09/27/2010] – General X X X X   X

Link to Reporting and Analytics Aggregates 8.0 Release Note (Cumulative)
Link to 7.6 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.

This release note applies to all 8.0 releases of Genesys Interactive Insights (GI2).

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information on any third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions


Release Number 8.0.100.05 [03/28/2011] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Genesys Interactive Insights.

Corrections and Modifications

There are no corrections or modifications for this release.

Top of Page


Release Number 8.0.001.03 [11/16/2010] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Genesys Interactive Insights.

Corrections and Modifications

This release also includes the following corrections and modifications:


When you set the Business Objects CMS port number during Interactive Insights installation to a value different from its default, 6400, you will no longer encounter the following error message when deploying a universe or reports:

An unexpected error occurred during the installation of Genesys Interactive Insights. Please check the prerequisites and run the installation again. Should the problem persist, please contact Genesys Technical Support.

(ER# 263309774)


Top of Page


Release Number 8.0.000.32 [09/27/2010] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Genesys Interactive Insights.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:


The Summary tab on the Agent Conduct Report has been updated to reflect an accurate count of short interactions handled by a given agent. Previously, this count was not normalized and instead was incremented for every group of which the agent was a member. (ER# 254084618)


Interactive Insights no longer overwrites BOE properties, permissions, or membership of the Interactive Insights-supplied users or user groups when you upgrade Interactive Insights from a previous release (that is, uninstall and then reinstall GI2). (ER# 234060556)


When you specify a value greater than 0 at the From Hour prompt of certain reports and then run the report, the results for measures that were defined using the DB delegated function are no longer empty where they should contain values. (ER# 229281573)


Values in the list boxes of report prompts no longer repeat as they did in previous releases. Previously, this issue occurred under some circumstances when you first ran a report and selected to expand Show List Of Values. The ALL value, for example, no longer appears twice. (ER# 183836167)


Timestamps now display correctly when you operate the Business Objects server on Linux platforms using JDBC drivers. In previous BOE releases, time was displayed as 00:00:00 in the Daily Agent Login-Logout and Daily Agent State Detail Interactive Insights reports under such circumstances. You no longer must change drivers (to Oracle Client or DB2 Client) as a workaround. Upgrade to BOE XI 3.1 Service Pack 3, however, is required. (ER# 196251318)


The deployment procedure was improved such that installation no longer fails during the importation of certain objects into the BOE XI repository when it already contains objects of the same name but that use different object IDs. Previously, as a workaround, you had to rename or delete the existing objects before re-installing the product. (ER# 229971501-BOE)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product. Some of the issues are specific to BOE software but are apparent through the Interactive Insights reports or universe. Where this is the case, the Genesys-associated Engineering Request (ER) number is suffixed with "‑BOE".


There are several look-and-feel issues with running reports when using the Mozilla Firefox browser such as shifted rows, misaligned table cells, and incomplete display of data. These issues are not apparent when using the Microsoft Internet Explorer browser or in Applet mode on Firefox.


If you are using a BOE cluster, then all BOE nodes that serve the InputFileStore and OutputFileStore servers must have access to the same storage location. This location can be a network share, SAN share, clustered filesystem, and so on, but all FileStore servers must point to the same location.

After you establish the shared location, use the following procedure to update BOE server parameters for all nodes to point to that location. The procedure uses a UNIX file path, UNIX commands, and /mnt/boshare as the shared location, but you can substitute Microsoft Windows commands and the directory of your own shared location:

  1. Create the following subdirectories for the input and output file stores:
    mkdir /mnt/boshare/input
    mkdir /mnt/boshare/input/temp
    mkdir /mnt/boshare/output
    mkdir /mnt/boshare/output/temp
  2. Make sure that the user account from which the BOE servers are run is the owner of the /mnt/boshare directory and all of its subdirectories and has read and write access to them.
  3. Then, for each node of the BOE cluster, perform the following steps:

    1. In the Central Management Console, browse to the Servers section and open the properties of server <NODENAME>.InputFileRepository.

    2. Enter the following values:
      Temporary Directory -> /mnt/boshare/input/temp
      File Store Directory -> /mnt/boshare/input
    3. Save and close the server properties.

    4. Right-click the server and select restartto restart the InputFileRepository.

    5. Next, open the properties of server <NODENAME>.OutputFileRepository.

    6. Enter the following values:

      Temporary Directory -> /mnt/boshare/output/temp
      File Store Directory -> /mnt/boshare/output
    7. Save and close the server properties.

    8. Right-click the server and select restartto restart the OutputFileRepository.

(ER# 295377854)

Found In:   8.1.000.05 Fixed In:  

In an environment where Business Objects components are installed on a VMWare cluster, the Web Intelligence Processing Server located on backup virtual machine stops and does not restart when the primary virtual machine ungracefully shuts down. This makes GI2 reports nonoperational. To address the situation, apply the solution described in this Release Note for ER #288212632. (ER# 296343761)

Found In:   8.1.000.05 Fixed In:  

On RedHat Linux 5.3 and above, you might notice the following symptoms:

To correct the problem:

  1. Contact Genesys Technical Support to obtain Placeholders utility from SAP KB Article 1449399.
  2. Copy the Placeholder.sh utility to any location on the virtual machine where BusinessObjects software is installed.
  3. Edit the BOHOME entry at the start of the Placeholders.sh file to reflect the install location of the BusinessObjects environment.
  4. Execute the following commands:
    Placeholders.sh -cms  -pass  -global -update WEBI_LD_PRELOAD '$LD_PRELOAD$'
    Placeholders.sh -cms  -pass  -global -update MDAS_LD_PRELOAD '$LD_PRELOAD$'

(ER# 288212632)

Found In:   8.1.000.05 Fixed In:  

If you have an active session on a backup machine while the primary machine ungracefully shuts down, you may get a dialog box with the following message:

Invalid session. Please close your browser and log on again.(WIH 0013)

You can then close the browser or login again, using the following steps:

  1. Click the OK button on the error message. A dialogue box with user name/password prompts will appear.
  2. Enter login and password.
  3. If you had a report open at the time of the shut down, you will see an empty report. Click the Close document button (the X in the top right corner of the page) to close it.
  4. If you did not have a report open, click any InfoView button (such as Document List).

You can then continue working with the current instance of the browser. (ER# 296800902)

Found In:   8.1.000.05 Fixed In:  

GI2 nodes do not support VMotion and can be moved to a new host only by cold migration (that is, by moving the GI2 nodes to the new host when the virtual machine is powered off). For details, see the VMWare Knowledge Base at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003797.

(ER# 296026835)

Found In:   8.1.000.05 Fixed In:  

The number, duration, and average of agent-initiated consultations for interactions (stored in the Consult Initiated, Consult Initiated Time, and Avg Consult Initiated Time universe measures in the Agent\Activity class) always yields a zero value when used in a query that includes the Queue or Queue Group dimension. This issue does not impact any of the Interactive Insights reports, but you might encounter this problem in custom reports that you design. (ER# 274836041)

Found In:   8.0.000.32 Fixed In:   8.1.000.12

Drilling on the Summary tab of the Agent Not Ready Reason Code report will cause values in the ranking tables to disappear. (ER#s 267117450, 267117443)

Found In:   8.0.001.03 Fixed In:   8.1.000.12

GIM users who partition Info Mart *_FACT tables on Oracle RDBMSs must perform additional manual steps to set this configuration up for aggregation. After Info Mart is initialized with your partitioned schema and after aggregation successfully initializes succesfully, you must execute the following SQL script:

drop INDEX IDXR_RSSF_DT;
drop INDEX IDXR_IRF_SDT;
drop INDEX IDXR_MSF_IID;
drop INDEX IDXR_MSF_SDT;
drop INDEX IDXR_RSF_SDT;
drop INDEX IDXR_RSRF_SDT;
drop INDEX IDX_RSSF_AGR_DB;
drop INDEX IDX_IRF_AGR_DB;
drop INDEX IDX_IRF_IID;
drop INDEX IDX_IRSF_AGR_DB;
drop INDEX IDX_MSF_TIRF;
drop INDEX IDX_RSF_AGR_DB;
drop INDEX IDX_RSRF_AGR_DB;

create index IDX_IRF_IID on INTERACTION_RESOURCE_FACT(INTERACTION_ID) local;
create index IDX_MSF_TIRF on MEDIATION_SEGMENT_FACT(TARGET_IXN_RESOURCE_ID) local;
create index IDXR_MSF_IID  on MEDIATION_SEGMENT_FACT(INTERACTION_ID) local;
create index IDXR_IRF_SDT  on INTERACTION_RESOURCE_FACT (START_DATE_TIME_KEY,RESOURCE_GROUP_COMBINATION_KEY,RESOURCE_KEY) compress 2 local;
create index IDXR_RSF_SDT  on SM_RES_STATE_FACT         (START_DATE_TIME_KEY,RESOURCE_GROUP_COMBINATION_KEY,RESOURCE_KEY) compress 2 local;
create index IDXR_RSSF_DT  on SM_RES_SESSION_FACT       (START_DATE_TIME_KEY,RESOURCE_GROUP_COMBINATION_KEY,RESOURCE_KEY) compress 2 local;
create index IDXR_RSRF_SDT on SM_RES_STATE_REASON_FACT  (START_DATE_TIME_KEY,RESOURCE_GROUP_COMBINATION_KEY,RESOURCE_KEY) compress 2 local;
create index IDXR_MSF_SDT  on MEDIATION_SEGMENT_FACT    (START_DATE_TIME_KEY,RESOURCE_GROUP_COMBINATION_KEY,RESOURCE_KEY) compress 2 local;
create index IDX_RSRF_AGR_DB on SM_RES_STATE_REASON_FACT ( DURATION_BUCKET(START_DATE_TIME_KEY,END_DATE_TIME_KEY), START_DATE_TIME_KEY, END_DATE_TIME_KEY ) compress 2 local;
create index IDX_RSF_AGR_DB  on SM_RES_STATE_FACT        ( DURATION_BUCKET(START_DATE_TIME_KEY,END_DATE_TIME_KEY), START_DATE_TIME_KEY, END_DATE_TIME_KEY ) compress 2 local;
create index IDX_RSSF_AGR_DB on SM_RES_SESSION_FACT      ( DURATION_BUCKET(START_DATE_TIME_KEY,END_DATE_TIME_KEY), START_DATE_TIME_KEY, END_DATE_TIME_KEY ) compress 2 local;
create index IDX_IRSF_AGR_DB on IXN_RESOURCE_STATE_FACT  ( DURATION_BUCKET(START_DATE_TIME_KEY,END_DATE_TIME_KEY), START_DATE_TIME_KEY, END_DATE_TIME_KEY ) compress 2 local;
create index IDX_IRF_AGR_DB  on INTERACTION_RESOURCE_FACT( DURATION_BUCKET(START_DATE_TIME_KEY,END_DATE_TIME_KEY), START_DATE_TIME_KEY, END_DATE_TIME_KEY ) compress 2 local;

If errors result pertaining to the drop INDEX statements above, this is an indication that RAA was not properly initialized—you must deploy and set up RAA as described in the Reporting and Analytics Aggregates 8.0 Deployment Guide and then rerun this script. (ER# 260217368)

Found In:   8.0.000.32 Fixed In:   8.0.100.05

In multi-tenant configurations where one tenant's schema shows data only for that particular tenant, the Detail Interactive Insights reports will not report Interaction activity that crosses the tenant barrier. (ER# 260050606)

Found In:  8.0.000.32 Fixed In:  

Exercise caution when selecting prompt values for the Detail reports especially if your Info Mart is a sizeable one storing a lot of unpurged detail (fact) data. The default prompt values supplied when opening such reports are for demonstration purposes and the reports query fields many of which are not indexed. The lengthy, full-table scans that result when the range of values specified in the prompts is wide might not complete before Web Intelligence times out. Performance of the detail reports improves significantly when you narrow the selection of values at all prompts. (ER# 259604661)

Found In:   8.0.000.32 Fixed In:  

If you try to parse some universe objects or perform a check of the GI2 Universe in Designer, you might encounter one or more of the following messages:

Parse failed: Invalid Definition (UNV0023)
Parse failed: Exception:DBD� (DBMS dependent message)

You can ignore these messages—for the following objects—because the Interactive Insights reports that employ these objects function properly.

Dimensions

Flow/Active
Flow/Interaction ID
Flow/Start Timestamp
Flow/End Timestamp
Flow/Customer ID
Flow/From
Flow/To
Flow/Agent/Queue Order
Flow/Segment ID
Flow/Duration
Service Objects/Pre-Set Day Filter
Service Objects/Pre-Set Date Filter

Conditions

Queue/PreSetAndDateRange Abn
Queue/PreSetAndDateRange Ans
Service Objects/Agent (single)
Handling Attempt/Customer ID
Handling Attempt/PreSetAndDayAndTimeRange
Ixn State/Ixn State PreSetAndDayAndTimeRange
State/Agent State PreSetAndDate
Session/Session PreSetAndDate
PreSetAndDateRange (in all classes)
PreSetAndDate (in all classes)
(ER# 258784277)

Found In:   8.0.000.32 Fixed In:  

If an agent's current state is in progress when agent-state data is extracted and transformed within Info Mart, then the aggregation of this data will round the agent's state duration up to the nearest aggregation interval, which is 30 minutes, by default. After the state ends and after the subsequent GIM extraction and transformation, the aggregation of this data will be updated to reflect the actual duration. In other words, durations of current agent states are always round up to 30 minutes until these states end and are transformed. (ER# 256527670)

Found In:   8.0.000.32 Fixed In:  

In some cases (and especially if system time in not perfectly synchronized in multi-site environments), the reports might yield warm consult counts and durations for agents where no warm consultation occurred. (ER# 256527666)

Found In:   8.0.000.32 Fixed In:  

In the agent and queue reports, drilling up for agent group (or queue group) results and then back down again and removing the report's drill filter might yield doubled results for those agents (or queues) that belong to two or more agent (queue) groups where the contact center activity performed by the groups overlap. To have the report display correct data in this situation, refresh the report's query (by clicking the Refresh button). (ER# 256339463)

Found In:   8.0.000.32 Fixed In:  

All of the Interactive Insights reports reference the DATE_TIME Genesys Info Mart table to identify the date and time keys that should be used to query data. If this table is not populated or if report users request data for dates that extend beyond the date/time keys stored in this table, the reports will return No Data. Refer to the Genesys Info Mart 8.0 Deployment Guide for information about how to populate this table. (ER# 254094061)

Found In:   8.0.000.32 Fixed In:  

The Summary tab on the Agent Conduct Report does not reflect an an accurate count of short interactions handled by a given agent. (ER# 254084618)

Found In:   7.6.200.09 Fixed In:   8.0.000.32

When drilling down from hour-level aggregation to sub-hour level-aggregation on the Main tab of Business Results reports, Web Intelligence may become unresponsive and appear to hang. If this should occur in your environment, restart the Web Intelligence Processing Server. (ER# 254009771)

Found In:   8.0.000.32 Fixed In:  

The BOE server cannot correctly process the complex query generated by the Interaction Volume Summary Report when you drill for results. Drilled results that are returned may contain unexpected or missed data. (ER# 251979921)

Found In:   8.0.000.32 Fixed In:  

The Interactive Insights reports will count an invitation for collaboration that an agent declines as Consult Received Accepted when the agent uses Genesys Agent Desktop (or a custom desktop using the same SDK) to decline the invitation. Refer to ER 247946331 in the Genesys Info Mart 8.0 Release Notes for additional information. (ER# 250850268)

Found In:   8.0.000.32 Fixed In:  

In multi-tenant environments, it is no longer necessary to run the make_gi2 script against each tenant schema as is documented in the Genesys Interactive Insights 8.0 Deployment Guide. (You must still run it, though, in GIM's main db schema.) Instead, you can issue the updateAliases runtime parameter when invoking aggregation to create tenant views of GI2 objects. Refer to the Reporting and Analytics Aggregates 8.0 Deployment Guide and User's Guide for additional information. (ER# 260108899)

Found In
Document Version:
  80ii_dep_09-2010_v8.0.001.00
Fixed In
Document Version:
  80ii_dep_11-2010_v8.0.001.03

The BOE server may stop or hang indefinitely during the following Web Intelligence operations:

These operations are most commonly performed on the Summary tab of Interactive Insights reports. (ER# 233433961‑BOE)

Found In:  7.6.200.09 Fixed In: 

When running Interactive Insights against an Info Mart on the DB2 RDBMS, report results might yield data that is rounded incorrectly for those measures that were defined using the DB delegated function. If the formula for such measures yields fractions (such as averages and percentages), the resultant values will be rounded down only to the tenths place—for example, 0.2 instead of 0.23. To obtain a higher degree of precision, update the measure's definition in Designer to use 1.0000 wherever 1.0 is used. In the modified formula, specify as many zeros as the degree of precision that you are trying to achieve. (ER# 229971505‑BOE)

Found In:  7.6.200.09 Fixed In: 

During the UNIX installation of BOE XI, you may encounter an error regarding the UTF-8 locale setting. If this parameter is set incorrectly, installation will cease. To correct this, issue one of the following commands prior to installation:

export LANG=en_US.utf8
export LANG=en_US.UTF-8

The command you select depends on your UNIX platform. (ER# 220315067‑BOE)

Found In:  7.6.100.07 Fixed In: 

In Report Info, the values for prompts that allow multiple selections display values in the order you selected them rather than alphabetically. (ER# 185568701‑BOE)

Found In:  7.6.000.26 Fixed In: 

The user prompts in reports that prompt for date values, such as Start Date and End Date, contain an extraneous time component (shown as 12:00:00) that is not required for report generation. Furthermore, the Business Objects Report Server ignores any time values that you might designate for such prompts. (ER# 185568808‑BOE)

Found In:  7.6.000.26 Fixed In: 

If you specify improper BOE credentials when prompted during the installation of Interactive Insights or if some other problem results that impacts the deployment of the Interactive Insights universe and reports to the Business Objects repository, the final screen of the Interactive Insights installation routine nonetheless reports that installation was successful. (ER# 185630156)

Found In:  7.6.000.26 Fixed In: 

Take care when interpreting report results that show data which has been drilled up from its original aggregation level. The layout of each report defines section breaks which are appropriate only to the original aggregation level designed for the report. For example, the Agent Interval Based Report has been designed with a section break on Agent Name. The Call Volume Service Type Report (the name of the report in the 7.6.x releases) has been designed with a section break on Service Type Name. (In 8.0, the name of this report is Interaction Volume Service Type.)

The composition of these section breaks is not dynamic in light of drilling operations that are performed on the report. Drilling up to Agent Group in the Agent Interval Based report, for example, does not redefine the section break to occur on agent groups. As such, reports for drilled aggregation levels display results that may appear unbecomingly sectioned.

As a workaround, you can customize a report to provide results that are appropriately sectioned for the desired aggregation level. (ER# 195952061‑BOE)

Found In:  7.6.000.26 Fixed In: 

Top of Page


Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.


There are no discontinued features.


Top of Page


Internationalization

Information in this section is included for international customers.


There are no known issues related to internationalization.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page