fighting for truth, justice, and a kick-butt lotus notes experience.

    HCL Traveler 11.0.1 FP1 aka released with fix for calendar notice routing when Traveler is in additional Domain

     Juni 2 2020 03:59:29 PM
    Traveler 11.0.1 Fix Pack 1 with Build Level Build 202005211639_30 includes fixes for the Traveler server and two new features.

    New Features:

    Support for Microsoft SQL Server 2019

    Traveler 11.0.1 Fix Pack 1 has been validated with Microsoft SQL Server 2019 as the Traveler server database when running in high availability mode.  

    Changes in calendar notice routing

    A side effect of the server support for Exchange ActiveSync (EAS) 16.1 introduced with Traveler 11.0.0 is that meeting notices from the Apple calendar application on these devices are sent using the Traveler server's Routing failures can occur if the Traveler server is not configured to route mail to and from the mail servers. Meeting notices from the HCL Verse client on Apple devices are not impacted as these notices are still routed via the mail server In configurations where customer wants to avoid routing these notices though the Traveler server then in this fixpack there is a new notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER that can be used to route the notices via the user's mail server Note that this setting does not apply to notices sent from HCL Verse mobile clients.

    Included Fixes:

    TRAV-4582        Traveler warning Unexpected tag in Options: Class


    Exchange ActiveSync 14.0 moved the Class XML element for GetItemEstimate commands from being a child of Collection to a child of Options which is a child of Collection. Traveler was not looking for Class as a child of Options and was logging a warning indicating an unknown child of Options was detected on the GetItemEstimate request. Traveler now expects Class to be a child of Options and no longer logs an incorrect warning. Traveler does not use the Class value, so there is no functional change - only no longer incorrectly logging the warning.

    TRAV-4519        Display name of groups with / on their names


    Display names for email addresses have been compacted by Traveler to the content before the first forward slash to save user interface space on the devices. However, some customers have asked that the full display name be used, so new notes.ini's have been added to give customers more display name options.

    NTS_ADDRESSCACHE_ENCODING_DISPLAY_NAME_COMPACT controls the display name for addresses that are not internet addresses and need to be encoded as described in "Address encoding for Microsoft Exchange ActiveSync devices" of the Traveler documentation. The default is true which means the display name is the content up to the first forward slash.

    NTS_ADDRESSCACHE_DISPLAY_NAME_COMPACT controls the display name for all other (not encoded) addresses. The default is true which means the display name is the content up to the first forward slash.

    TRAV-4372        Provide an option to avoid routing meeting notices via the Traveler server's when making changes from the Apple iOS or iPadOS Calendar application


    Invitations and other meeting notices will be routed via the Traveler server's when the meeting chair creates or updates the meeting from an Apple iOS or iPadOS Calendar application on a device syncing with Microsoft Exchange ActiveSync 16.0 or 16.1. This is the default behavior for HCL Traveler version 11.0 and later (note that there was no change in meeting notice routing from HCL Verse mobile clients). Failure to have routing and connection documents configured on the HCL Traveler server to/from the mail servers can prevent meeting notices from being received by the chair and/or invitees of the meeting.  To avoid routing these notices through the HCL Traveler server, the notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER can be set to True to route the notices via the user's mail server Product documentation will be updated with this new setting.

    Note for customers that manage their database schema: Traveler 11.0.1 Fix Pack1 does not include a database schema update.
    Traveler 11.0.1 FP1 Database Schema Level: 20190922
    However prior releases did include database schema updates (for example: Traveler 11.0.0 did include a schema update).  Depending upon what level of Traveler server you are upgrading from, there may be a database schema update required.

    Traveler 11.0.1 Fix Pack 1 can be used to install a new Traveler environment or update an existing Traveler environment running Domino 9.0.1.x, Domino 10.0.x, or Domino 11.0.x without requiring a Domino upgrade. It is always recommended to keep Domino at the latest level.  If updating Domino to 11.0.1.x, a minimum of Traveler 11.0.1 is required.

    More Details: