Release Notes 1-89

About the development of new requirements and optimizations of the Content Management System.

New Features and Enhancements

Implement new navigation concept

New Main Nav

As many of you already know a new main and meta navigation is in the planing and wil go live with the release of 1.91.  The new navigation will be implemented for all markets at the same time and replaces the old one. 

 

Since this project involves a lot of changes, we would like to present the most important changes here at an early stage.

 

  • The main and meta navigation is placed horizontally on the desktop

 

 

  • Meta navigation is placed above the main navigation and contains three references and a new component (on the left) where three editorial sentences can be configurated which will be displayed in rotation 

 

 

  • Main navigation will contain 6 categories (with icnos) and the megalayer showing the sub-navigation will open also horizontally and beneath the main navigation

 

 

  • The megalayer will have 4 columns with a maximum of 20 rows each

 

 

  • Not all page refernces will be displayed on the megalayer, the rest of the page references will be displayed as "more..."

 

  • Order of the categories in the megalayer can be determined by the author
    • Default order of the categories and sub-categories is sorted based on the backend structure (previous behavior)

 

  • Up to 4 promotional pages can be activated
    • These promotional pages are displayed in the first column of the megalayer (without subcategories)

 

Important Information

The Go live of the new navigation is planned for Release 1.91

However a few changes need to be fullfilled beforehand already. Please see more details on this in the Important Information section.

Migration of Newsletter Feedback into AEM Dialog

Newsletter Feedback Component

All components from the frontend service are now played out as internal dialogues. The previous components still use external React dialogs so in order to uniform the dialogs all React components were adapted and migrated accordingly.

Following adaption will be made with this change:

 

  • Migrating existing dialogs for newsletter feedback components 

 

 

  • In all places where this component is already in use, it will be replaced via internal dialogues

 

  • The newsletter feedback component is available as an internal dialog

In conclusion the Newsletter Feedback Component will be an AEM Component fully after the Deployment (instead of a REACT component) 

Important Information

The Newsletter Feedback Component needs to be re-inserted into the Newsletter Unsubscribed Page after Deplyoment 

Sticky pop-up for marketing purposes

Sticky pop up settings

As a result of an A / B test, we were able to generate a 50 percent increase in newsletter registrations via a sticky pop-up. Therefore, it was decided to further develop this sticky pop-up and make it configurable as a multi-purpose sticky pop-up which can help to draw the customers' attention to newsletters, promotions, contests or similar advertising measures.

 

Following list contains the settings and configurations of the Sticky pop up:

  • The pop-up will be displayed at the bottom right for desktop version and centered at the bottom for mobile

 

  • The pop-up overlays the move-to-top button

 

 

  • Only the CTA is clickable, not the entire popup  (desktop & mobile)

 

 

  • Content of the popup are maintained on the language page
    • CTA Text
    • CTA Link
    • Image
    • Headline and Copytext (both are optional and the pop up will adjust its size depending on the content)
    • Period in which it should appear
    • After which time (in seconds) the pop-up should be displayed, the default is 60 seconds

 

 

  • In the page properties of all content pages you can specify whether the popup is displayed
    • For main pages there are two options to chose from:  show and don´t show
    • For subpages there are three options to choose from: Inherit behavior from parent page, show and don´t show

 

 

  • If an interaction (CTA / Close) has been made via the pop-up, it will not be displayed again until the LocalStorage expires after 14 days

 

  • Only one pop up per market can be displayed
  • Following paramenters will be tracked by analytics
    • How often is the popup displayed
    • How often is the popup closed
    • How often is the CTA clicked
Sticky pop up settings

Data processing agreement for CRM

ContactConsent folder in AEM

There are two options for the users to get in touch with their ALDI local market: 1. through the contact form on the ALDI homepage and 2. directly via email (e.g info@aldi-nord.de).  In both possible ways, the consent of processing personal data of the customer must be handled differently. 

  1. Contact form: The customer reaches out to ALDI through contact form via the homepage. On the homepage he confirms the processing and forwarding of his data.
  2. E-mail: The customerreach out to ALDI via e-mail, e.g. impressum@aldi-nord.de. The e-mail will be forwarded to info@aldi-nord.de and will be forwarded directly to the CRM system

A data processing agreement process for the second option has been prepared. The process will work as following:

  1. Customer sends email 
  2. Email will be forwarded to CRM system 
  3. Customer will be forwarded to an Data Agreement Page (an AEM page with a button) 
  4. If the customer agrees to data processing then he will be directed to an thankyou page 
  5. If the customer does not click the button the agreement will be counted as not accepted

To ensure that customers are directed to the correct page where the consent button can be clicked, a redirect page will be created for you on the same level as your Language Page. Please ensure to intergrate the link to the page with the Consent button right after the deployment. 

Important Information

For this proceed each market needs to create 3 Pages for data agreement: 

  1. Data Agreement Page with button (please choose the component Contact Consent SFSC)
  2. Data Agreement Success Page
  3. Data Agreement Failed Page

To ensure that customers are directed to the correct page where the consent button can be clicked, a redirect page will be created for you on the same level as your Language Page. Please ensure to intergrate the link to the page with the Consent button right after the deployment. 

Sitemap Cache duration to 12 Hours

Until now the sitemap was updated once every 24 hours at around 2:00 p.m. in Cloudfront. Some markets requested a shorter update time, therefore it has been decided to shorten the updating time to 12 hours. 

This change will not have any impact on load or performance.

Update icons on FAQ pages

The icons on the theme tiles on the new FAQ page are currently hardcoded, From an editor perspective it woul be better if the icons in the FAQ theme tiles could be freely selectable and changeable, so that they fit the content chosen by the editor. 

Therefore, it is possible now to change and edit the icons. Following icons are possible to add after next deployment:

  • App
  • Career
  • Contact
  • Date
  • Info
  • Location
  • Magazine
  • Mail
  • Map
  • Newsletter
  • Offer
  • Pacifer
  • Recipe
  • Search
  • Services
  • Settings
  • Store finder
  • Tag
  • Themes
  • Warning 
  • Worth knowing
  • Award
  • All offerings
  • Van 

Change InfoBox component background color

The InfoBox component (tip variant) received a new the color (from grey to light grey-blue).

Bugfixes

  • FR - No Search Results for published articles -There were no search results for published articles. This has been fixed.
  • iOS - Too long article tiles and button alignment incorrect - For IOS 12-14 there was an issue where the article tiles and the position of the buttons were incorrect - this is fixed
  • Newsletter Feedbacks - cleanup inconsistent feedback reasons -Due to an error in the NewsletterFeedback Web Service SST, incorrect data records were written to the mongoDB - this is fixed.
  • SFMC: articles are not transfered due to code snippets in brand name - Articles were not submitted to SFMC due to the HTML code in the brand name - this is fixed
  • Adjustments - Implementation Design System - Typography - An Adjustment for the H1 headline has been made, the H1 primary (in Condensed) has been replaced with a new version (heading-h1)
  • Contact Form: customer survey request is active when survey is disabled - Despite the deactivated Customer Survey, a request could be still called that leads to a blank page - this has been fixed 
  • Tile Group is missing in Newsletter Thank You Component - A single content tile could be added into the Newsletter Thank You Component, which is then displayed as wide as a page - this is fixed
  • Category Slider - Category tagline is not shortened - Category tagline was not shortened with dots after 2 lines - this is fixed

Important Information:

New Navigation concept:

In terms of the new Main Navigation concept it is neccessary for some markets to reorganize their main navigation since the new main navigation will only contain 6 navigation points.  

If you are currently displaying more than 6 navigation points in the first level navigation, the navigation needs to be restructured and redirects need to be implemented.

Therefore, we are preparing a SUPP Ticket with detailed information about how to restructure the navigation in the best way and what may need to be considered.

One info ahead: The reorganisation of the Main Navigation should be completed before release 1.91 and needed redirects should be handed in until 18th of August by the latest in order to able to implement the redirects with the release of 1.91.

Safe Areas for article images:

Since the display of the article tile has changed, some safe areas had to be adjusted as well, especially when it comes to the 1x1 Primary image where the price tile is now displayed differently.

Please find the information in the images here and also in the corresponding CAG chapter: Image Safe Areas

 

Safe Area
Safe Area

Contact data

Company

ALDI Einkauf SE & Co. oHG

   
Contact

Department ATS | Digital / IT

 

Equal Treatment Law

The use of the male form when referring to persons or functionaries in the following text does not mean a gender-specific definition. Members of both sexes should be addressed on an equal footing.

General Notes

The release integrates new functionalities, optimizations and bug fixes into the software.

Please read these release notes to be up-to-date concerning the new program version and to get important information on handling new functions.

If you have any questions about this update, please contact MRM / McCANN external support at aldi-support@mrm-mccann.de

Erinnerung für
Fehler Es ist ein Fehler aufgetreten. Bitte versuchen Sie es später erneut.

Sollen wir Sie benachrichtigen wenn der Artikel verfügbar ist?

hh

Tag der Erinnerung
Zwei Tage vorher
Einen Tag vorher
Am Angebotstag
Uhrzeit
00:00
01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
Hinweise
  • line 1
  • line 2
  • ...

Eine Erinnerung ist nicht mehr möglich

Die Erinnerungszeiten für diesem Artikel sind bereits abgelaufen.

Erinnerung aktiv!

hh

Sie erhalten Ihre Erinnerung am ${date} um ${time} Uhr.

hh

Wir senden Ihnen noch eine Nachricht per E-Mail, um ihre E-Mail Adresse zu bestätigen. Bitte klicken Sie auf den Link in der Nachricht.

regions.regionSwitchHeadline

regions.regionSwitchText
regions.regionSwitchTextExplicitSwitch