Release notes for Episerver updates

1. Create a profile filter definition like this:

POST: /api/v2.0/filterDefinitions
        {
            "Name": "PDF_Name_with_quote_curly_bracket",
            "Description": "Name equal inputValue with single quote and curly bracket",
            "Query": "Name eq '{{name}}'",
            "Category": "PFD",
            "Type": "Profiles"
        }

-> It returns 201 Created
2. Open Insight > Segment > press the Create a segment button
3. Choose the newly created filter definition in step 1 > choose Scope value > press Preview

• Actual: Display the Error message: Oops... Error: Request failed with status code 500
  Please see an attached image.

You can delete an event or all events by specified TrackId. The deleted event is no longer available through the API or UI (until a new event with this TrackId is tracked).

After deleting the event by specific TrackId, you can track a new event using the same TrackId. You also should use newly tracked events in segments.

You can delete a profile and all related events. The deleted profile events are not available anymore through API or UI.

After deleting the profile and related events, you can track a new event from the same devices. You should create a new profile when processing these new events. You also should use newly tracked events in segments.

The product name Insight was updated to Visitor Intelligence in the user interface.

Precondition: Create some event filter definitions with some type of parameters: bool, guid, double and timespan (Query in Payload)
(ex: Create an event filter definition like this one:

{
   
    "Name": "Payload_Boolean_Event",
    "Description": "Payload Boolean Event",
    "Query": "Events|where Payload.testbool == {{value}}",
    "Parameters": {
        "value": "bool"
    },
    "Category": "Events",
    "Type": "Events"
}

1. Open Visitor Intelligence > Segments > click on Create a Segment button
2. Choose the filter definition with parameters in the precondition, input proper value in param, click on Preview.

• Expected: Return the proper profiles
• Actual: Return: Error: Request failed with status code 500

Note that: When I check creating segment by event filter definition using API:

• It creates segment successfully with parameters types bool and guid
• It returns 400 Bad Request with parameter types double and timespan

Profile phone number validation probably doesn't cover all possible valid cases.

Instead, invalid value (or valid phone number that we do not accept as valid) blocks storing profile data. It is also quite hard to describe clearly and maintain the documentation for this validation in case it is updated.

We should consider removing phone number validation or making it much more relaxed since the product functionality doesn't rely on correct phone numbers. Storing data as is may be more important than validating phone numbers.

Updated: Validation has been relaxed. Valid phone number characters: + - . whitespace and alphanumeric characters.

1.Create a profile without DeviceIds
2. Using API to delete profile based on DeviceId:

DELETE: /api/v1.0/profiles/{{scope}}/{{profileId}}

-> It returns 200 OK with message: Successfully removed data for profile item profileId
3. Get profile in the previous step

• Expected: The profile is deleted
• Actual: The profile is not deleted, it is displayed in the list
  Note that: The bug doesn't occur when I add email of the profile in blacklist, then clear user data of the profile.

1. Navigate to Profile Store API in your region.
2. Observe that you are redirected to Swagger UI page
3. Note that Blacklist endpoints are listed for v1.0
4. Switch to v2.0 in top left corner

Expected: Blacklist endpoints are listed for v2.0
Observed: Blacklist endpoints are not listed.

Using API to post a new profile more than 1024 deviceIds:

{
            "Name": "user6789",
            "Info": {
                "Email": "user6789@example.com"
            },
            "DeviceIds": [
                "0", ... , "1025"
            ],
            "Scope": "default"
        }

• Expected: Return 201 Created with new profile in body
• Actual: Return 500 Internal Server Error

Several customers have reported that they want to be able to ignore the products in their catalog and export all variants as separate items instead.

To do this, use the abstractions and structure map interceptor pattern. Partners need to write their own implementation of an interface method whose default implementation is ~500 lines of code with private sub-methods. The source code is provided to the partners for this purpose.