Client Switching and Saved Amparex Setups

This page explains which WP2Amparex settings to apply to a connected
Which Amparex clients are associated with them, and what happens when login credentials are changed
happened.

Status

Branch and consultant photos have been available since 2.3.0 stored on a client-by-client basis.
Since 2.4.0 Does this also apply to appointment categories and appointment logic? The
The manual order of branches and advisors is also
stored on a per-client basis. If your installation includes the section
Saved Amparex Setups is not yet displayed; the installed version is
It's still too old, or the corresponding release hasn't been installed yet.

Why are there saved setups?

WP2Amparex can be used in an installation with different Amparex access points
be connected. Here's an example of how that happens:

  • on an internal test installation;
  • For customers with multiple websites and different
    Amparex clients;
  • when a technical API user is replaced;
  • when a client is temporarily disconnected and then reconnected later.

Without client-specific storage, settings such as appointment categories
or images would be overwritten during the switch or would have to be updated.

How much data is stored per Amparex setup?

The following information is stored on a client-by-client basis:

  • displayed appointment categories;
  • Order of appointment categories;
  • internal category descriptions;
  • displayed category names;
  • Category icons;
  • Start of the day in the calendar;
  • End of the day in the calendar;
  • the option Disable Advisor Steps;
  • Branch photos;
  • Consultant photos;
  • Order of the stores in the front end;
  • Order of the front-end consultants.

The following remain global:

  • Core Design Values;
  • Email text and signature;
  • License status and license key;
  • General plugin options;
  • Support and Debug Settings.

How does WP2Amparex recognize a setup?

WP2Amparex creates internal client namespaces from the Amparex API URL and
all currently available stable client identifiers from the
Amparex Branch Information.

The namespace is intentionally not based solely on the technical API username.
So when a client receives new technical login credentials,
Client-specific settings are retained as long as the same
Amparex system associated with the same client ID.

Depending on availability, client identifiers may include, among others, the following
Amparex data taken into account:

  1. Sales Tax ID (vatNumber)
  2. Commercial Registry Data
  3. Tax ID Number
  4. Posting Client (bookMandator)
  5. Company Name (name1)
  6. Main Branch ID

If Amparex later provides an additional identifier with a higher priority,
A pre-populated setup for the same client remains active. For example,
For example, a VAT ID that was added later does not trigger a clean restart,
if a setup based on the tax ID number that is still being provided
exists.

Procedures for Changing Clients

When another Amparex client is connected:

  • WP2Amparex loads its own category, scheduling logic, image, and
    Sequence Setup.
  • If there is no setup for this client yet, the
    Client-specific fields are left blank or filled with the standard fallback values.
  • The settings from the previous client remain saved.
  • When switching back to the previous client, its categories,
    Appointment logic, images, and sequences have been restored.
  • Are there multiple saved namespaces that are known to belong to the current
    belong to the same client, the desired setup can
    with Use Setup be selected.

Existing global category settings from older versions are retained when
The first recognized clients are assigned to this setup once. As a result,
Existing category configurations are not lost during the update.

Delete old setups

In the Settings Center, there is a section Saved Amparex Setups.

There, WP2Amparex demonstrates:

  • the detected setup name;
  • whether it is the currently active setup;
  • the internal namespace;
  • the identifier type from which the namespace was derived, for example
    VAT ID or Tax ID Number;
  • how many categories, store images, consultant images, store locations, and
    consultant positions are saved;
  • which start of the day, which end of the day, and which consultant step status
    The setup includes:;
  • when the setup was last detected.

For inactive setups of the same currently connected client, the following appears:
Use Setup. Configurations from another API system or tenant can
cannot be activated this way.

The API username and API URL are located in the API section, directly above the
Setup Management. They are not duplicated for each setup: The login credentials are
global; not part of the client-specific data configuration. In particular,
The full Amparex alias URL may contain sensitive connection information
is included and is therefore not saved separately in the setup history.

With Delete Setup Setups that are no longer needed can be removed.
Before deleting, WP2Amparex asks for confirmation one more time.

Only client-specific data for this setup will be deleted:

  • Appointment Categories;
  • Start and end times in the calendar;
  • the option Disable Advisor Steps;
  • Branch photos;
  • Consultant photos;
  • Branch and consultant sequences;
  • the setup's registry entry.

Do not delete:

  • Amparex credentials for the currently saved plugin;
  • License information;
  • Email texts;
  • Design;
  • Reservation details;
  • other client setups.

Recommendations for Test Installations

For central test installations, the procedure is as follows:

  1. Connect to Client A.
  2. Check or maintain categories, scheduling logic, images, and sequences.
  3. Save settings.
  4. Connect to Client B.
  5. Maintain categories, scheduling logic, images, and sequences for Client B.
  6. Switch back to Client A.
  7. Check whether categories, scheduling logic, images, and sequences from Client A
    reappear.

If many test clients have been tried out, outdated setups in the
Section Saved Amparex Setups clean up.

Technical Reference