Products
Packages [expand] [collapse]
Services
Released in version
1.23.0
1.22.0
1.21.0
1.20.0
1.19.0
1.18.1
1.18.0
1.17.0
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.2
1.7.1
1.7.0
1.6.0
1.5.0
1.4.0
1.3.2
1.3.0
1.1.0

Release notes for Episerver updates

This overview lists changes included in Episerver updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Episerver updates. Select a product, package, or service in the left menu, and filter for dates, features, or bug fixes.

  • See only new features (all features) - filter on item type Feature.
  • See only end-user (user interface) features - filter on item type UI Feature.
  • See only critical bug fixes - filter on item type Critical Bug.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Area Id Type Description Released
PROF-7781
  Out of the box filter definitions for Commerce

A default set of filter definitions are now included out of the box in Visitor Intelligence. Marketers can create segments based on Commerce events and profiles without asking developers to create their own filter definitions.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-6804
  [InsightUI][Segment]: Returns wrong profiles with profile filter definition - space in param

Precondition:

There is a profile filter definition which has at least one param in the query, like this one:

        {
            "Id": "fd_PDF_Name_eq",
            "Name": "PDF_Name_eq",
            "Description": "Name equal inputValue",
            "Query": "Name eq {{name}}",
            "Parameters": {
                "name": "string"
            },
            "Category": "Profiles Category",
            "Type": "Profiles"
        }

Steps to reproduce:

  1. Access to Insight > Segment > and click on Create a Segment button.
  2. Choose the filter definition in the precondition and insert the param name like: test 01.
    • Expected result: Returns only the profiles with name test 01.
    • Actual result: Returns many profiles which names do not have test 01.
  3. With the same filter definition, insert param name with value in double quotes like "test 01" - it returns the correct profile.
    If you click Save segment in step 2, this segment will have many profiles without test 01 in the name (exactly the number of profiles that are returned in step 2).
    Note: The same bug occurs if you insert parameter with value: test 00, but not for parameters test 02, test 03, test 04.
EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7847
  Time and count metrics for filter definitions

Marketers can now set the time or/and count metrics when creating a segment based on event filter definitions, and reuse the same filter definition in combination with the time period and the number of event occurrences.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-4579
  Visitor group personalization doesn't work for segments with a query on profile payload

Precondition:

Create profile test@test.com with Payload info like this:

"Payload": {
     "number": 2
}

Steps to reproduce:

  1. Using API, create a segment with ProfileQuery being Payload like this one:
    {
      "Scope": "default",
      "SegmentManager": "admin@example.com",
      "ProfileQuery": "Payload.number eq 2",
      "AvailableForPersonalization": true,
      "Archived": false,
      "FavoredBy": [
        "string"
      ],
      "Name": "Payload",
      "Description": "Payload"
    }
    
  1. Create a Visitor Group for the segment in step 1.
  2. Set personalize content for Visitor Group in step 2.
  3. Log in to the site with profile test@test.com and view the personalize content.

Expected result:

The user can see the personalized content.

Actual result:

The user cannot see the personalized content.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-6820
  [FilterDefinition] Can create a new profile filter definition with invalid property in Query

Create a new profile filter definition with an invalid property (which does not belong to the profile) in Query like this one:

POST: /api/v2.0/FilterDefinitions
{
    "Name": "Testing_VisitorGroup_input_value",
    "Description": "VisitorGroup with inputValue",
    "Query": "Testing eq {{value}}",
    "Parameters": {
        "value": "string"
    },
    "Category": "Profiles",
    "Type": "Profiles"
}

Expected result:

Returns 400 Bad Request with message Invalid filter definition.

Actual result:

Returns 201 Created and create new filter definition successfully.

The same thing happens if you create an event filter definition with an invalid property which does not belong to the track event.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-8001
  Only 10 profiles are listed when using MatchProfileById and MatchProfileByEmail for a segment

Steps to reproduce:

  1. Create a segment that includes more than 10 profiles.
  2. Get all profiles and emails that belong to the segment (they are less than 500 records), do MatchByProfileId or MatchByEmail
POST: segmentURL/segmentId/MatchByProfileId 

Expected result:

All the profiles based on profileIds/Emails should be returned.

Actual result:

Only 10 profiles are returned.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7894
  [ProfileAPI]: Inconsistent display the null value

1. Create a new profile:

POST: /api/v1.0/profiles
{
    "Info":
    {
        "ZipCode"null
    }
}

-> It returns 201 Created with body:

{
    "ProfileId""545db9d4-79f8-49cb-ae63-34ab6ca95647",
      .....
    "Info": {
        "ZipCode"null
     }
}

2. Get the newly created profile in step 1:

GET /api/v1.0/profiles/default/545db9d4-79f8-49cb-ae63-34ab6ca95647

-> It returns the profile with info:

 {
     "ProfileId""545db9d4-79f8-49cb-ae63-34ab6ca95647",
     .....
     "Info": {},
 }

Expected result:

The Info property should display consistent information.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7904
  Display UI warning when the time and occurrence metric may be incompatible with a specific filter definition

An indication/warning is now displayed in the user interface when a metric is not applicable with the selected filter definition.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7689
  Specific error message is not returned when KQL query is invalid

Steps to reproduce:

Execute an invalid query using the event preview endpoint, for example:

Events | summarize count() by Payload

Expected result:

Specific error message with details of what is wrong and ideally suggests how to fix the problem.

Actual result:
Generic error response is displayed, like this:

{"error":{"code":"400","message":"Failed to execute the query.","target":"","details":[]}}
EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7733
  [Segment_v2.0]: Returns 500 when creating a new segment without Query property

Steps to reproduce:

  1. Create a new segment with event/profile filter definition without Query property in Filters:
{
  "Scope""default",
  "SegmentManager""Franklin Cummings",
  "AvailableForPersonalization"false,
  "Archived"false,
  "FavoredBy"null,
  "Name""Testing Segment",
  "Description""Testing Segment",
  "Filters": {
    "Items": [
      {
        "Type""Events",
        "Parameters": {   
          "value""home"
        }
      }
    ]
  }
}

Expected result:

Returns 400 Bad Request with Validation Error.

Actual result:

Returns 500 Internal Server Error.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
1 2 3 4 5 6 Next