New Features in This Release

Visual Indicator of Disconnected Repositories

If a connection can't be established with a server repository it will display a grey icon instead of the normal gold icon.  Once a connection is established it will switch to a gold icon.  A server repository may be unavailable because the server can't be reached, is down, or the user can't authenticate to it.

Canceling Credentials Stops Prompts

In Loupe Desktop if you cancel the username/password dialog for a given server you won't be prompted again until you either exit Loupe Desktop or click on the red Credentials Required note in the status bar.  The server repository will indicate that it's disconnected as a reminder of its status.

User Lockout Adjustments

With server users now being used for Loupe Desktop we've seen a notable increase in users being locked out.  After discussing this with a few customers we've upped the number of consecutive bad password attempts it takes to lock out a user from 6 to 10 and added logic to prevent repository administrators (in Standard Edition) and cluster administrators (in Enterprise Edition) from being locked out. 

User Name is now distinct from Email Address

You can now configure a distinct user name from the email address for a user account in Loupe Server.  User names must still be unique but no longer are required to be a valid email address.

Compatibility

Loupe 3.7.0 is generally backwards compatible with 3.0 with the following notes:

• Agent: Compatible with Server & Desktop versions 3.0 and later.
• Server: Fully backwards compatible with older Agents and Loupe Desktops, any version.
• Desktop: Compatible with Server versions 3.7.0 and later.  Compatible with any version of Agent.

Agent API Changes

There are minor additions to the Agent API in version 3.7.0.  Accordingly, the Gibraltar Agent has a new assembly version (3.7.0.0).  The changes are:

• New: Gibraltar.Agent.Log.ApplyConsent: This method improves auto-send consent scenarios by allowing background processes to respect the consent settings of a different UI application in the same product.
• Modified: Gibraltar.Agent.Packager.SendToServer: To support the new Enterprise Server better a new repository option has been added to certain overloads.
• Modified: Gibraltar.Agent.Packager.SendToServerAsync: To support the new Enterprise Server better a new repository option has been added to certain overloads.

Review Loupe 3.7 Notes

Since this is an update release you should read Getting Started - What's New - Version 3.7 for a more complete picture of the new capabilities since version 3.0.

Defects Fixed In This Release

Agent

• Fixed: Debugger breakpoint when there is a corrupt local log file present.
• Fixed: Send Session on Exit doesn't work when an Application Base Directory or Repository is specified

Desktop

• Fixed: Adding a repository you don't have access to repeatedly prompts for credentials
• Fixed: If you lose access to a repository you get repeatedly prompted for credentials.
• Fixed: New Metric Chart dialog can't be completed for metrics without quantitative data.
• Fixed: Unable to open session from web link if not in user repository.
• Fixed: When selecting a time frame for opening a session a different time frame may be loaded due to time zone differences between the session and the current user.
• Fixed: Desktop Alerts do not display for server repositories.

Server

• Fixed: Application Events Statistics charts calculate the top versions incorrectly, showing the first N versions regardless of them being the top versions.
• Fixed: External users (E.g. from Active Directory) can be locked out within Loupe even when not locked out in Active Directory.
• Fixed: Loupe Server UI always indicates that users are under Active Directory management on user list even when no AD management is configured.
• Fixed: In Enterprise Server when a user edits their profile their email address is cleared.
• Fixed: In Enterprise Server promoting a user from a virtual user to a full or administrative user doesn't update them in the cluster core database so they still can't sign in.
• Fixed: In Enterprise Server when a user edits their profile if they are a repository administrator they are promoted to a cluster administrator.