Possibility to create and maintain configurations for contact centre forms, including access to content element "contact form" and related plugin options
Access to specific tree / folder to edit and revise global configs for Content HUB categories, Colour Tool configuration, Global Content HUB Content maintenance
Possibility to integrate job offerings in the same way like news / blog articles but in dedicated content modules. (e.g. used in ZG NL: https://www.zehnder.nl/nl/vacatures) But in general, job offerings should be integrated on Group level and dedicated platform (https://career.zehndergroup.com)
Possibility to access and integrate RAD selektor plugin on pages, option to pre-filter operation modes and also to access the plugin pre-filtered product listing strictly connected to PIM based RAD products which have been imported to related tree
Access and possibility to create and maintain URL redirects, not on root level, e.g. for PDF documents which aren't typo3 pages, but for all kinds of URL paths
Access and possibility to maintain the "sidebar" tab and to configure contents and manage Azure B2C Login integration as well as linking to contact centre
https://sandbox.zehnder.avenit-prod.de/en/sidebar
CMS Specialist
Redakteur - Module Mongo
Access and possibility to check values and data directly based on MongoDB database which contains plain PIM based attributes and data. In addition more detailed information present on PIM based product detail pages.
Possibility to access storage folders of each imported PIM based product to check related imported data not only in frontend but also in backend look & feel and to e.g. delete Hash value in order to trigger new import of already activated products on the website.
Possibility to access edit mode of Plugin "ComfQuick", available for German Tree only. Related data required for the tool has to be shared / assigned to avenit for Upload and update
possibility to create global content hub page types and access to storage section global hub
CMS Specialist
Redakteur - MountPoints
Access to content / config element "mounting points" in order to configure tree sections that are maintained in a tree section a) but should also appear in a tree section b) but keeping the navigational menu of b). Without "mounting points" the menu would switch to the structure a) where the mounted cotent is maintained in the typo3 structure
Access and possibility to update URL paths in bulk mode. But will only update paths along tree structure an page titles. I case there have be differing custom cofigurations differing from tree structure and page title, this would be overwritten. In this case paths need to be updated per page and not in bulk mode.
Access to footer section of each page and possibility to maintain contents in this section. Differs from section of Footer Seperator in the tree where shortcuts for meta menu can be maintained.
Based on basic typo3 in combination with Zehnder specific custom developments there exist different roles, access and config options within the system setup. This overview will be filled along onboarding process with Market related CMS specialists.
Possibility to access the footer section of each page and maintain content(s)
Inheritance logic available, means in case footer is maintained on highest tree position (homepage) then the contents are inherited to all pages below. If a footer on a page within the structure is maintained seperately, it overwrites the contents maintained on higher level.
In case Azure B2C is activated on a tree, for each user who logs in a logfile entry is created giving information which tokens were present in the string and which user-groups for the website are connect to related access.
entries are deleted per process each week because no manual changes possible
no real time-stamp is set
relevant information is connected to user groups in dependence to Azure B2C login-token
Possibility to bulk update more than one URL slug of a page by just one click
Attention! Only recommended if your URL structure fits to your tree structure and page titles because Slug Updater would update the page Paths along these structure and information. It can't consider any custom changes to URL paths
3 different options available with different impacts and considerations
Use only very carefully, normally only during relaunch processes or first implementations of a tree.
We use a third party service that may collect data about your activity to embed this content. Please
review the details and accept the service to access it.
Consent to Data Processing
In order to use our “MyZehnder Solution Finder” service your consent to the use of the chatbot service “Zendesk Chat” and to the associated processing and storage of your inputs is required. The data you provide will be stored in a cloud infrastructure and used exclusively to process your inputs and to improve our service. Please note that without your consent the use of our “MyZehnder Solution Finder” service is not possible. Your data will be treated confidentially and will not be disclosed to unauthorized third parties. Further information on the processing of your personal data can be found in our privacy policy.
