2024 CMS+CMP integration release notes

  • Updated

Follow this article to receive email notifications when new Optimizely Content Management System (CMS) + Optimizely Content Marketing Platform (CMP) integration packages are available for 2024. Product packages are found on the Optimizely NuGet server. 

Are you looking for release notes before January 2024? See the Optimizely Release Notes on the Optimizely World site.

You can find prior versions of user guides and when functionality was released or deprecated at the following locations:

November 28, 2024

EPiServer.Cms.WelcomeIntegration 2.0.0

Enhancements

  • Changed the behavior for DAM asset metadata so it is no longer populated upon page request and cached.

    Instead, Optimizely Content Marketing Platform (CMP) stores the metadata in the database upon publishing a page or block that contains references to DAM assets. The taghelper and htmlhelper available use the metadata stored in the database while creating the <img> tag.

    The metadata is updated by a scheduled job called Optimizely CMP DAM asset metadata maintenance. See also the blog post by Robert Svallin: DAM integration new major version, performance improvements and Library Picker folder selection 

  • Added the ability to organize CMP content in folder structures. You can configure, globally or by type, which folder to open in the CMP Library Picker with the DAMOptions class that has two new properties:

    GlobalRootFolderGuid – configure a global folder
    RootFolderForTypes – define separate folders based on types

November 5, 2024

Optimizely.Cms.Cmp.Publishing 1.4.0

Enhancement

  • Added the ability to retrieve CMP asset metadata from Optimizely Graph instead of querying the API. See CMS + CMP + Graph.

Bug fix

  • CMS-35511 – Fixed an issue in the DAMAssetDataTransferHandler and IdentityMappingService that caused an error if the importing DAM asset had the same Uri with an existing DAM asset where both had the same Provider and ProviderUniqueId but different contentGuid.

    This scenario could happen if you had two instances of CMS that referred to the same DAM asset, and then you exported the data from one instance and imported that data into another instance.

September 20, 2024

Optimizely.Cms.Cmp.Publishing 1.3.0

Enhancement

  • The publishing integration can connect multiple individual Optimizely Content Management System (CMS) installations to a single Optimizely Content Marketing Platform (CMP) instance.

    However, if you had one CMS installation with multiple sites, you previously could not connect each site to a different CMP because CMS could not send the content update event when a particular piece of content is edited; this prevented the preview from being automatically captured and updated while a user is editing and being stored with the asset for approvals.

    You can now associate a website with different CMP instances so that the teams responsible for these sites can manage their work in CMP.

September 19, 2024

Cmp.Client 1.1.0

Enhancement

  • Defined the following settings to support multiple CMP instances per CMS site:
    • StartPage Id
    • CMP instance Id (Organization Id) associated with the site
    • OAuth settings (client id and secret) to authenticate with Integration API and Orchestrate API
    • OAuth settings (client id and secret) to authenticate with CMP API.

      The settings format could be put in Optimizely:Cmp section as below:

       "MultiInstances": {
  "Mappings": [
    {
      "Application": {
        "ApplicationId": "4F2BE131-9AA7-4954-9C46-90CADC76146B",
        "ClientId": "cms_client_1",
        "ClientSecret": "mysecret",
        "AllowActAs": false
      },
      "CmpInstance": {
        "ClientId": "cmp_client_1",
        "ClientSecret": "bigsecret",
        "OrgSSOId": "",
        "DegradedMode": true
      }
    },
    {
      "Application": {
        "ApplicationId": "E13D9D50-5C81-4F36-A60D-F8DBBF735239",
        "ClientId": "cms_client_2",
        "ClientSecret": "mysecret2",
        "AllowActAs": false
      },
      "CmpInstance": {
        "ClientId": "cmp_client_2",
        "ClientSecret": "bigsecret",
        "OrgSSOId": "",
        "DegradedMode": true
      }
    }]
}

May 21, 2024

EPiServer.Cms.WelcomeIntegration 1.3.9

Enhancement

  • Updated the dependency on Optimizely.Cmp.Client to version 1.0.0.

March 14, 2024

EPiServer.Cms.WelcomeIntegration 1.3.8

Bug fix

  • CMS-32559 – Fixed an issue where images added from the CMP DAM to the contentArea in CMS carried the incorrect alternative text.

February 27, 2024

EPiServer.Cms.WelcomeIntegration 1.3.7

Bug fixes

  • CMS-31232 – Fixed an issue where if you clicked Replace after you selected a CMP Digital Asset Manager (DAM) asset, the CMS assets selector window displayed instead of the CMP DAM one.
  • CMS-32226 – Fixed an issue where to replace an image that you selected from CMP DAM, you had to delete the image and select a new one.