How does Flexwhere for Desktop communicate with the backend of Flexwhere?

Flexwhere for Desktop communicates with the backend of Flexwhere via an IP address.

How is the IP address determined from version 3.0 of Flexwhere for Desktop for Windows?

From version 3.0 of Flexwhere for Desktop (Windows), this IP address is determined automatically. Based on the IP-whitelist, which is set by your organization, Flexwhere knows which URL is needed.

When is it necessary to override the automatic URL?

Sometimes it is necessary to override the automatic URL. These situations are: there are multiple organisations with the same IP address; as a Flexwhere customer you want to test something in an acceptance/test environment; an IT supplier serves multiple customers of Flexwhere; or a Flexwhere employee wants Flexwhere for Desktop to communicate with a customer's environment.

How can the automatically determined URL be modified?

For the above situations, the automatically determined URL can be modified in the appsettings.json config file. You do this by explicitly giving the URL that is correct.

What should be added to the appsettings.json config file?

The appsettings.json config file should include: "AlternativeConfigurationUrl": "https:// .flexwhere.com/tray/config". In the example, should be replaced by your own organisation name.

Does the automatically determined URL work for on-premises customers and customers with a private cloud?

No. For on-premises customers and customers with a private cloud, the automatically determined URL will not work. The URL should be added in the appsettings.json config file as described in this article.

How do I adjust Flexwhere's automatically determined settings for Desktop?

Q: How do I adjust Flexwhere's automatically determined settings for Desktop?

You can adjust the automatically determined settings by overriding the URL in the appsettings.json config file. This is necessary in situations such as multiple organisations sharing the same IP address, testing in an acceptance environment, or when the automatic URL does not work. In the config file, you explicitly define the correct URL using the AlternativeConfigurationUrl setting.

Flexwhere for Desktop communicates with the Flexwhere backend via an IP address. Starting with version 3.0 of Flexwhere for Desktop (Windows), this IP address is automatically determined based on the IP whitelist.

Sometimes it is necessary to override the automatic URL. These situations are:

There are multiple organisations with the same IP address;
As a Flexwhere customer you want to test something in an acceptance/test environment;
An IT supplier serves multiple customers of Flexwhere;
A Flexwhere employee wants Flexwhere for Desktop to communicate with a customer's environment.

For the above situations, the automatically determined URL can be modified in the 'appstettings.json' config file. You do this by explicitly giving the URL that is correct. This looks like the following:

{
  "Logging": {
    "Enabled": true,
    "LogLevel": {
      "Default": "Debug"
    }
  },
  "LocalSettings": {
    "AlternativeConfigurationUrl":"https://<clientname>.flexwhere.com/tray/config",
    "TimeoutSeconds": 3,
    "TimeoutFactor": 1.5,
    "HideExit": false
  }
}

Note: For on-premises customers and customers with a private cloud, the automatically determined URL will not work. Thus, the URL should be added in the appsettings.json config file as described in this article.