Release Note

T-Server for Siemens HiPath 4000 CSTA III

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2011–2016

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.001.02 [12/19/16] – General X     X X X
8.1.001.01 [02/09/16] – Hot Fix       X   X
8.1.001.00 [01/21/16] – General X     X X X
8.1.000.13 [03/04/15] – Hot Fix X     X X X
8.1.000.12 [12/18/14] – Hot Fix X X X X X X
8.1.000.11 [10/27/14] – Hot Fix X X X X X X
8.1.000.10 [10/06/14] – Hot Fix X X X X X X
8.1.000.09 [04/16/13] – Hot Fix         X X
8.1.000.08 [07/24/12] – Hot Fix         X X
8.1.000.07 [12/02/11] – General X X X X X X
8.1.000.04 [06/27/11] – General X X X X X X

Link to 8.0 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.genesys.com for more details.

This release note applies to all 8.1 releases of T-Server for Siemens HiPath 4000 CSTA III.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see T-Servers. Please contact your Customer Care representative if you have any questions.


Release Number 8.1.001.02 [12/19/16] – 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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This version was first released as a Hot Fix on 09/14/16. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections or modifications:


T-Server now correctly generates EventPartyChanged on the origination DN of the main call when a consultation is made to a routing pilot, routed to another pilot within the same RCG, and then transfer is completed. Previously on transfer completion, T-Server generated EventPartyChanged only for the routing device. (UKTS-17476)


T-Server now properly handles scenarios where calls that are retained after leaving T-Server scope return to scope before being cleared from T-Server. Previously in such a scenario, T-Server might have failed. (UKTS-17422)


Top of Page


Release Number 8.1.001.01 [02/09/16] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


T-Server now correctly handles PBX events with two or more entries in private extensions fields. Previously, T-Server might have failed when processing such events. (UKTS-17410)


Top of Page


Release Number 8.1.001.00 [01/21/16] – 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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections or modifications:


T-Server now correctly handles errors in scenarios involving supervised routing and recovers immediately. Previously, T-Server might provide incorrect errors in such scenarios and recovered from errors only on the expiration of supervision timeout. (UKTS-17402)


T-Server now correctly performs a Check Call cleanup when an inbound trunk snapshot does not provide the expected information. Previously, T-Server deleted checked calls due to rejection of snapshot call functionality requested for such calls. (UKTS-17392)


T-Server now provides reporting that is compatible with Interaction Concentrator (ICON) requirements:


Top of Page


Release Number 8.1.000.13 [03/04/15] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.71. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


T-Server now correctly reports routing on native Routing Points when no information regarding a calling device is available and a transfer is performed on another PBX node. Previously, T-Server did not report EventRouteUsed and EventDiverted events for a second routing after:

(UKTS-17258)


T-Server now correctly handles forwarding to Emulated Routing Points (RPs). Previously, when a consultation call was made to a device that had forwarding to an Emulated RP enabled, with the call routed and transfer completed, T-Server did not report of an EventPartyChanged event for a device where monitoring originated. (UKTS-17239)


T-Server now correctly handles Emulated Routing Points (RP) after restoring connection to the PBX. Previously, T-Server incorrectly deleted the association of the Emulated Routing Point with its members when the link was reconnected, which resulted in loss of routing functionality to that Emulated RP. (UKTS-17111)


T-Server now correctly handles the restart of a link and reports an agent as logged out, when an agent disconnects the phone from the network while T-Server is disconnected. Previously, T-Server considered that agent as logged in. (UKTS-17109)


Top of Page


Release Number 8.1.000.12 [12/18/14] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.71. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Release Number 8.1.000.11 [10/27/14] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.71. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


During transfers, T-Server now properly initializes transferring parties whose CallerIDs the switch has hidden. Previously, a crash could result. (UKTS-17179)


Top of Page


Release Number 8.1.000.10 [10/06/14] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.71. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


RCG (Routing Point or ACD Queue) devices monitored via the r prefix notation must be parsed into integer device identifiers in requests to the switch. This translation occurs at the point of reading from the configuration. Previously, in version 8.1.000.09, T-Server incorrectly cleared the translated device identifiers from its memory on CTI link failure. When the link was restored, T-Server sent the incorrect string r identifiers in requests to the switch. T-Server now caches the device identifiers so that RCG devices can be re-monitored successfully after CTI link failure. The RCG group monitor *888 is unaffected. (UKTS-16721)


Top of Page


Release Number 8.1.000.09 [04/16/13] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.60. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server now correctly processes the callback-dn configuration option on no-answer supervision. Previously, T-Server might have incorrectly processed the redirect for the call including a hidden (unknown) originator identity with a call back DN. (ER# 317899989)


T-Server now correctly populates the AttributePreviousConnectionID attribute value in EventPartyChanged and sends the next DN-related event in the following scenario:

Warning! Do not use the report-local-connid-changes option unless you are instructed to do so by Genesys Customer Care.

Previously in this scenario, T-Server generated an EventPartyChanged event with the AttributePreviousConnectionID attribute value incorrectly set to ffffffffffffffff and failed to generate the first DN-related event for the call (EventRinging, EventQueued, or EventRouteRequest events, depending on the type of DN at which the call arrived).

(ER# 316888704)


T-Server now correctly handles call events from a switch that have a blank Call ID. In addition, the monitored device that detects a blank Call ID is put out of service to reflect this unexpected DN condition. The device is then restored back to service after receiving a CSTA connection cleared event that has null local connection information that corresponds to a Genesys EventOnHook event. Previously, T-Server unexpectedly terminated in these scenarios. (ER# 317676930)


Top of Page


Release Number 8.1.000.08 [07/24/12] – Hot Fix

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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.001.45. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server now correctly decodes CSTA call events that contain empty CallID attribute fields. Previously, T-Server sometimes became unstable when it received these CSTA call events from the PBX. (ER# 300934995)


T-Server now correctly reports the OtherDN attribute after the call is redirected (routed and/or forwarded) from an unmonitored DN. Previously, T-Server might not have properly tracked the OtherDN attribute changes. (ER# 299507145)


Top of Page


Release Number 8.1.000.07 [12/02/11] – 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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.000.25. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server no longer sends an EventNetworkReached message on an Alerted device. (ER# 284945511)


T-Server no longer occasionally goes into an infinite loop in scenarios where DNs are disabled and enabled in quick succession in the configuration environment. (ER# 283242602)


T-Server no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)


Top of Page


Release Number 8.1.000.04 [06/27/11] – 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 of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.000.19. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of T-Server for Siemens HiPath 4000 CSTA III.

Corrections and Modifications

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


Reporting of EventReleased after a failed Two-Step Transfer has been corrected to fix the other party DN. (ER# 236640888)


Reporting of Single-Step Transfer to an Emulated Route Point has been corrected to remove the incorrect third-party DN in the related events. (ER# 226594679)


Reporting of Single-Step Transfer to a Route Point and/or Queue has been corrected to remove the incorrect third-party DN in the related events. (ER# 100976)


T-Server now ignores unsupported agent workmodes for native agent requests, no longer failing not-ready self-transition requests when such workmodes are used. (ER# 221762854)


T-Server no longer passes empty strings to ASN encoder. Previously, T-Server would terminate operation under Windows in this scenario. (ER# 271030661)


The option kpl-loss-rate has been removed from T-Server. (ER# 274704653)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


T-Server might improperly report the field OtherDN in events for consultation calls or incompletely report scenarios involving the transfer of an internal call to an external destination, because of incorrect interpretation of a missing network destination in PBX reporting when the following scenario is executed:

Workaround: Configure outbound trunks in PBXs so that the information from the PBX contains the correct remote destination.

Found In: 8.1.001.00 Fixed In: 

T-Server does not apply values of the restart-period configuration option other than 10 seconds. (ER# 285626365)

Found In: 8.1.000.07 Fixed In: 

T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)

Found In: 8.1.000.04 Fixed In: 8.1.000.07

Currently, the Framework 8.1 T-Server for Siemens HiPath 4000 CSTA III Deployment Guide omits the following option description. The next published version of the document will include this information.

legal-guard-reason
Default Value: 0
Valid Values: 0254
Changes Take Effect: Immediately

Specifies the value of the Reason Code key in AttributeExtensions that T-Server will report in an EventAgentNotReady message that is sent as a consequence of the legal pause phase.

Found In: 8.1.x Fixed In: 

Because of incorrect switch reporting of an unmonitored transfer, in the following scenario, T-Server cannot link the transfer to the outbound consultation leg of the initial transfer. As a result, T-Server creates a new call to represent the unknown secondary call and performs a standard two-step unmonitored transfer to the newly created unknown call. When the first part of the chained transfer is completed, this unknown call is the final result.

(ER# 234758803)

Found In: 8.0.001.01 Fixed In: 

Switch reporting does not provide any information about call forwarding before the call arrives at the final destination. The forwarding DN is never referred to in any  events and the event causes are always reported as single-step transfer. Consequently, T-Server cannot detect this scenario nor correct it. (ER# 206778801)

Found In:  7.6 Fixed In:


When a conference is initiated to a Routing Point and then routed to an external DN, once the conference is established, the conferenced-in party releases. In this case the PBX may not always provide the correct information to T-Server and therefore sometimes T-Server may not generate EventPartyDeleted. (ER# 172756104)

Found In:  7.6 Fixed In:


When an unmonitored device makes a transfer to a monitored device, there are three EventPartyChanged events reported, one of which has a new connection ID. This is caused by the switch reporting the unmonitored transfer in two steps, and in each step only one primary old call is reported. Therefore when the first transferred event is received, T-Server creates the missing other call and performs a partial transfer. The second event completes the transfer, and the partial transfer party and call are destroyed, leading to three EventPartyChanged events. (ER# 172146007)

Found In:  7.6 Fixed In:


In the following scenario, the PBX reports that the failed party is blocked, and no event is generated by T-Server. The Release request times out. The agent can release the blocked party using the Reconnect function.

  1. The agent initiates a transfer to a busy destination.
  2. The switch reports dialing and then destination busy.
  3. The agent tries to release the dialing party on the transferring device.

(ER# 171703324)

Found In:  7.6 Fixed In:


DTMF can only be attached on an outbound call. (ER# 67256051)

Found In:  7.5.001.14 Fixed In:


It is not possible to make a chained consult call to a queue or native Routing Point. (ER# 84098421)

Found In:  7.5 Fixed In:


The following limitations apply when dialing invalid numbers:

Make call to invalid
When an invalid destination is dialed over a trunk, in some cases T-Server generates EventDestinationBusy with a call state of SitInvalidNumber. However, on some trunk types, the PBX does not provide enough messaging to generate this.

Consult Call to invalid
On a call of type consult, the PBX does not provide enough information to generate EventDestinationBusy with a call state of SitInvalidNumber.

Route/single-step transfer/redirect to invalid
The PBX does not always provide a failed event when one of the above requests is attempted to an invalid destination via a trunk. Consequently, the operation often times out.

(ER# 76010842)

Found In:  7.5 Fixed In:


When an external call, made over a Cornet trunk, is transferred to a third site, T-Server may generate the following events on the H4000: EventHeld, EventPartyChanged and EventRetrieved. This is due to switch reporting. (ER# 105416852)

Found In:  7.5 Fixed In:


This problem occurs due to incorrect reporting from Siemens. If DND and/or Forwarding are set, on startup, T-Server is unable to display the correct status for these features for VoIP telephones. (ER# 67187437)

Found In:  7.5 Fixed In:


The One Number Service (ONS) allows two phone sets to be linked together so that if either number is dialed, both phone sets will ring. The numbers are set up so that one is Primary and one is a Slave.

This feature has the following CTI limitations:

(ER# 71255199)

Found In:  7.2 Fixed In:


When using an emulated Routing Point as the voice transfer destination of a campaign that uses CPDServer with a digital Dialogic board, the OCS option call_transfer_type must be set to one_step. If it is set to two_step the outbound call can not be successfully transferred to an agent. (ER# 47736513)

Found In:  7.2 Fixed In:


After a call is redirected externally, the PBX reports the call state on the external T-Server as Forwarded rather than OK. This also occurs if the call is redirected to a Routing Point and then routed externally. (ER# 52594028)

Found In:  7.2 Fixed In:


A consult call, routed from an emulated Routing Point to a GVP port, cannot be transferred. (ER# 40762866)

Found In:  7.2 Fixed In:


Releasing a device in Ringing state generates an EventError, because the switch reports a Diverted event instead of ConnectionCleared, and the Divert is not matched with the EventReleased.

See the following scenario as an example:

Main T-Server (H4000 CSTA III)
Remote T-Server (H300h)

In this scenario, 2102 is released (EventReleased has Call State: NoAnswer), however an EventError is generated.

(ER# 40682589)

Found In:  7.2 Fixed In:


The PBX does not allow a recalled call to be redirected, so it is not possible to use No-Answer Supervision on calls that have been recalled. (ER# 34840571)

Found In: 7.2 Fixed In:


In the following scenario, when DN1 drops the call, an EventReleased is generated on DN3 but not on DN1. Another RequestReleaseCall is required on DN1 in order to get an EventReleased. However, then the Consult call remains in a Held state on DN1 and it is not possible to do anything with it (Release/Retrieve/Reconnect) via CTI. It has to be dropped by DN2 or manually. Setting the configuration option auto-reconnect-on-fail to true will prevent this issue.

  1. DN1 MakeCall to DN2. DN1 InitiateTransfer to DN3. DN3 AnswerCall. DN1 AlternateCall.
  2. DN1 Drop active call (to DN2) using ReleaseCall.

(ER# 30533702)

Found In: 7.2 Fixed In:


ISCC/COF only works with already initiated calls. Examples of call flows that T-Server is able to handle with the COF feature are:

In release 7.2, new configuration options (cof-ci-defer-create, and cof-ci-defer-delete) control the operation of COF, resolving some of the previous limitations, but the following restriction still applies:

(ER# 101805,101544 )

Found In:  7.1 Fixed In:


When making a single-step transfer via ISCC with cast-type set to direct-ani the token used by ISCC is the origination of the primary call and not the destination. This does not match the ANI and the remote connection fails. (ER# 74387, 55715)

Found In:  6.5.3 Fixed In:


Chained consult calls are not supported on an analog line. Also single-step transfer of the destination of a consult call from an analog line is not supported. This affects VTO scenarios where a consult call is made to a Routing Point then routed to a VTO port. (ER# 87207, 86812).

Found In:  CAP 2.0 CSTA 3  Fixed In:


At start-up, T-Server tries to snapshot configured devices so it can restore call configuration. However, due to the way the Snapshot service is implemented in CAP v1.0, it is not possible to distinguish established state from originated/dialing. T-Server therefore treats dialing parties as established at startup. (ER# 75739, 75740)

Found In: CAP 1.0 Fixed In:


    CAP v1.0 sometimes fails to report the end of agent wrap-up state. The agent may remain in wrap-up state for CTI applications, while in fact he is ready to accept new calls. The agent must log off and log on again to clear this situation. (ER# 75741, 75742)

    Found In: CAP 1.0 Fixed In:


    When operating with HiPath 4000 UV6, T-Server is unable to support ACD configurations that contain *888. RCG devices must be explicitly configured in the configuration environment. (ER# 285626452)

    Found In: Unspecified Fixed In: 

    When operating with HiPath 4000 UV6, T-Server is unable to provide correct reporting for calls that are abandoned while they are parked because of insufficient switch reporting. (ER# 285626414)

    Found In: Unspecified Fixed In: 

    If a direct call is made to an emulated Routing Point and not routed, after a while the switch moves the call to another Hunt Group member. When this happens the switch provides a Connection Cleared event but does not tell T-Server that the call has been diverted. This means that on the emulated Routing Point, T-Server generates EventQueued and EventRouteRequest followed by an EventAbandoned and then a new EventQueued and EventRouteRequest. T-Server will retain the same ConnID unless retain-call-tout is not configured. If retain-call-tout is not set or set too low then T-Server will generate a new ConnID on the new EventQueued and EventRouteRequest. (ER# 102221966)

    Found In:  Unspecified Fixed In:


    It is not possible for primary and backup T-Servers to synchronize call information when a backup T-Server starts after a call was created. In this case, call control will not be maintained by T-Server after switchover, and therefore ACW behavior cannot be predicted. Setting configuration option ha-sync-dly-lnk-conn to true will prevent call synchronization problems. (ER# 88084618)

    Found In:  Unspecified Fixed In:


    When an inbound call using Q931 trunk arrives at an extension, a CTI single-step transfer request to a QSIG trunk is rejected by CAP. Two-step transfer is not affected. (ER# 66570914)

    Found In:  Unspecified Fixed In:


    When QSIG Path optimization is used to transfer calls to an extension (for example, from an IVR connected to such a trunk), the PBX does not report the call delivery to the transfer destination correctly. T-Server is expecting a Delivered event but instead receives a ServiceInitiated event. This means that T-Sever cannot generate the ringing event until the call has been answered manually. (ER# 66570904)

    Found In:  Unspecified 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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.


    Windows Server 2003 is no longer supported.

    Discontinued As Of: 8.1.001.02

    Solaris 9 is no longer supported.

    Discontinued As Of: 8.1.001.02

    The HP-UX PA and HP-UX IPF operating systems are no longer supported.

    Discontinued As Of: 8.1.001.00

    The Red Hat Enterprise Linux 3.0 operating system is no longer supported.

    Discontinued As Of: 8.1.000.04

    The Solaris 8 operating system is no longer supported.

    Discontinued As Of: 8.1.000.04

    The Tru64 UNIX operating system is no longer supported.

    Discontinued As Of: 8.1.000.04

    The AIX 5.1 and 5.2 operating systems are no longer supported.

    Discontinued As Of: 8.1.000.04

    Top of Page


    Internationalization

    Information in this section is included for international customers.


    There are no known internationalization issues for this product.


    Top of Page


    Additional Information

    Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

    Product documentation is provided on the Genesys Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

    Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation 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