Application integration

To avoid problems with future AEM upgrades, all special solutions need to be approved and system compatibility verified by SWS. In addition, the look and feel of all special solutions have to follow ETH corporate design guidelines and meet legal accessibility guidelines (external page WCAG 2.1 AA, external page eCH-0059 Accessibility-Standard Version 3.0 in German).

Possible types of application requests:

1. Iframe to display external web application/website content on a webpage. (must comply with copyright and be approved for admitted content, as Iframes are not considered best practice).
   
2. JSON/Script Node to pull data from an external database and display information on a webpage (website owner responsible for programming). 
3. Special application development or JSON/Script Node programming to be done by Software Services (cost borne by website owner). This category includes change requests to existing solutions for units developed by Software Services.
   

Because special applications are the responsibility of the website owner and may need to be maintained and updated with any release in the system, we require that all requests be accompanied by a Download signed agreement (PDF, 100 KB) with this understanding.

Important: Many new standard components have been integrated into the AEM environment that draw information from ETH databases: news feeds, event feeds, publications, academic calendars, event calendars, course catalogs, contact information, and person lists, to name a few. It is preferred to use existing solutions in the system instead of creating multiple individual solutions. If a particular solution does not meet your needs, we would like to know why so that it could be determined whether we should implement an overall change to an existing component in AEM instead of investing time in an individual solution. The goal is have a system which meets the needs of the majority of ETH members.