Release Notes 1-98

A specific smart app banner has been created which will be displayed only on the mobile view of the website to promote the app and lead the customer to download the app. 

The app banner follows the following criteria:

• The traffic is excluded from the app so that the banner is not displayed to those users who already have the app
• If the banner is closed within a session, it will not be displayed again (if it was closed the action will be saved for 15 day and for click on cta 90 days)
• It tracks how many users click on the CTA in order to measure the success of the banner
• Depending on the device, either the PlayStore or the AppStore is linked
• Lables can be edited in properties of Language Page, TAB Lables
• The app links are maintained in the country page
  • Links are maintained for Play Store
  • The App Store ID is maintained for iOs
  • The Smart App Banner can be activated per store - Default is active

• The banner is only displayed in the consumer content area
• Footer links remain untouched

It has been decided that it should be possible to enter alternative image dimensions that are less high than the current Big Slider format. 

Therefore follwing dimensions (Heights of Stage Theme) will be allowed for the Big Slider:

1. 1440px x 590px (large)
2. 1440px x 490px (medium)
3. 1440px x 300px (small)

The dimensions are also work for mobile and Tablets.

Until now all fields and subjects on the contact form are the same for all countries. Therefore it has been decied to adapt the contact form the needs of each market. 

Following requirements have been implemented into the dynamic contact form: 

• Topics need to be defined in SFSC and will be then stored in the CMS via configuration
• It will be possible to assign existing input fields from the template to each topic flexibly
• Only the Salesforce service cloud is supported as an interface. Sending by email (postcode RG-specific) is not supported
• It should continue to respond to the maintenance window which is already set up via OSGI-Config and in this case the requests should be sent to a defined fallback email
• If only one topic is stored, the selection box will be not displayed, but the topic is still transmitted when submitting the contact form
• The subtopics for the category "HomeDelivery" are permanently stored in SFSC and may not be used dynamically. The subtopics here are a special solution that must continue to be treated in such a way that the correct assignment of HD requests can be guaranteed.

Configuration:

1. Insert the new component called "Contact form dynamic" into a form page
2. Open settings of the component and config everything needed in the tabs
   1. TAB CONTENT SETTINGS - here you can configurate all the Sender Data lables as wished for example for Name, Address, zip code, error message, footer etc.
   2. TAB TOPICS OVERVIEW - here you can insert a lable, placeholder and error message for topics which you will add by your own. Under the section TOPICS there is a button "add field" here you can create your own topic (detail steps in the next chapter below). Same steps are doable for Category of Home Delivery in this TAB
   3. TAB TOPIC FIELDS - here you can Topic relates lables for example the lable for EAN Number in the Topic Articles or Street name for the topic Stores
   4. TAB FALLBACK EMAIL - here you can insert an addess, subject and body text for a fallback email which will be sent out in case of downtime

How to set up a new Topic:

1. Open settings of Dynamic Contact Form and go to TAB TOPICS OVERVIEW 
2. Click on button "ADD FIELD" in the section Topics and a new empty topic will be created
3. Give the Topic a name → this name will be displayed for the customer on the form later
4. Choose a topic type from the dropdown
   1. The dropdown comes from the Salesforce and describes the type of the topic for example if it is about data protection, quality, questions about products etc..
   2. This dropdown list can be adjusted (removing not needed topics or adding new ones) by the market within the OSGI console
5. From a list of available topic fields you can decide which ones you want to active for your new topic (for example flieds like data upload field or article based fields)
6. Save and publish

If you want to remove or add topics into the OSGI console in order make them useable in the AEM please reach out to us if support is needed.

Currently, YellowMaps is used as a store locator on all websites. This outdated solution is to be replaced in the future by a new state-of-the-art store locator from Uberall. In order to be able to give the customer significantly more information about our stores and also to simplify the search for a store for the customer.

With the new Uberall solution, we will provide the customer a better search and value-added information on the website for our stores, as well as the possibility to see the nearest markets directly on a map. In addition, through better information and structured data, we push our Google My Business results to become more visible to our customers on Google.

Therefore a rollout is planned and performed for Germany, the Netherlands and Denmark. For this purpose, the Uberall script of the store locator for these countries has been integrated on the store locator pages in DE, NL & DK.

Other markets will keep using the Yellowmap until Uberall has been rolled out for them.