XMPL Release Notes

Prerequisites for XMPL installation:

  • uProduce version 8.2.3 and above
  • Windows Server 2016 and above Standard Edition
Version 3.5 Server (Dec 21, 2022)
  1. Fixed: The XMPL installer version 3.5 resolves issues regarding friendly URLs in uStore when set up for Fault Tolerance.
  2. Changed: During XMPL installation, friendly URLs are no longer synched by default.
    For migration, it is essential that friendly URLs are copied to the new server. To enable the copying, before beginning the installation, create a new registry key, ResetFriendlyUrls, and set it to 1.

Version 3.3 Server (Mar 24, 2022)
  1.  This version includes security improvements.
  2. PDF on Demand in a secured website now opens in HTTPs protocol.
    In order for the PDF on Demand document to be secured via HTTPs, you must configure an SSL certificate on the XMPL and uProduce servers. For more information, see Configuring a PDF on Demand Document to work with HTTPs.

Version 3.2 Server (Sep 9, 2021)
  1. Added: TLS 1.2 (Transport Layer Security protocol) is now fully supported in XMPL.
    This requires PersonalEffect version 10.0.2 and higher.
  2. Added: This version supports the geolocation and device reports for web touchpoints, to be soon released in Circle.
    These reports will include data starting from the installation date of this version.

Version 3.1 Server and Client (May 19, 2019)
  1. Added: XMPL Server & Client 3.1, together with Circle 7.0, support triggered external touchpoints with two new directives: xmp-success-trigger and xmp-clicked-trigger.
  2. Deprecated: The triggered email directives xmp-success-triggered-email and xmp-clicked-triggered-email are deprecated and replaced by xmp-success-trigger and xmp-clicked-trigger respectively. The deprecated directives are still supported, but it is advised to start using the new ones.

Version 3.0 Server and Client (Dec 25, 2018)
  1. Added: XMPL Server & Client 3.0, together with Circle 4.7, support SecURL which offers user authentication in personalized URLs. When the recipient attempts to access a PURL, he/she is prompted to sign in and provide user authentication. This protects unauthorized users from accessing private recipient information which is stored in ADORs. SecURL is implemented on a project level, and affects both managed and custom websites.
    SecURL is not supported in Template-Instance and Campaign-on-Demand (uStore).
    Read the help in English    Deutsch     Français   |   User Authentication    Video Training
  2. Added: XMPL website caching on the server. This ensures no downtime of websites during a Circle deployment.
  3. Added: Clear Browser Cookies. When a GURL which becomes a PURL (after a recipient submits information), you  can now clear recipient information and reset the page to be anonymous.This is useful when the same browser is used to sign up multiple recipients (e.g., at a conference check-in booth).
 Version 2.3 Server (Oct 4, 2018)
    1. Added: A new API has been added – IsRecipientExist. This API enables to check if a RecipientID exists in the current project.
    2. Fixed: Friendly URL now works in HTTPS in all cases.

Version 2.2 Server (May 13, 2018)

Note: The latest version of XMPL Server is recommended for customers who require tighter security or GDPR compliance.

    1. Fixed: Limits the passing of ADOR values just to the ones needed by the Web for the current recipient. This change prevents easily extracting additional ADOR values though the API. (136710).

Version 2.1 Server (Apr 29, 2018)
    1. Added: HTTPS support in websites. The XMPL Server 2.1 is a prerequisite for HTTPS. If you do not require HTTPS, you can continue using  your existing XMPL version.

Version 2.0 Server (Aug 27, 2017)
    1. Changed: The XMPL Server version is now uncoupled from the PersonalEffect version. You can continue working with your current XMPL Server version 8.x or 9.x. However, on repair, modify or upgrade you have to uninstall the current XMPL version and install version 2.0.
    2. Changed: When adding/removing a Circle account in the Agent, the change is automatically applied to XMPL and there is no need to reinstall XMPL each time (as it was before XMPL 2.0)