1. Home
  2. Management
  3. How do I adjust FlexWhere’s automatically determined settings for Desktop?
""
Eddy

How do I adjust FlexWhere’s automatically determined settings for Desktop?

FlexWhere for Desktop communicates with the backend of FlexWhere via an IP address. From version 2.0 of FlexWhere for Desktop (Windows+Mac+Linux) this IP address is determined automatically. Based on the IP-whitelist, which is set by your organization, FlexWhere knows which URL is needed.

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

  1. There are multiple organisations with the same IP address;
  2. As a FlexWhere customer you want to test something in an acceptance/test environment;
  3. An IT supplier serves multiple customers of FlexWhere;
  4. 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 config file. You do this by explicitly giving the URL that is correct. This looks like the following:

In the example above should be replaced by your own organisation name.

Note: The default config file for FlexWhere for Desktop 2.0 contains the following sentence:

<Add key=”AlternativeConfigurationURL”.
value=https://<clientname>.flexwhere.com/tray/config/> –>

Replacing <clientname> with the name of your organisation is not sufficient.
The sections at the beginning and end of this line indicate that they are considered comments
. Therefore, take the line above this block as an example.

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

Note: In the default config file included with version 1.1.4 and below of FlexWhere for Desktop, one of the following lines is included:

<add key=”ConfigurationURL” value=https://<clientname>.flw3.nl/tray/config/>
<add key=”ConfigurationURL” value=https://<clientname>.flexwherecom/tray/config/>

These rules are no longer used as of version 2.0. To avoid confusion, we recommend removing this line.

Updated on 13-09-2021

Was this article helpful?

Related Articles