Ogledujete si pomoč za različico :

Experience Manager Sites

See a full list of changes in Sites, see Full list of changes in AEM Sites and Add-ons below.

AEM Site Feature Highlights

Here are some of the highlights for AEM Sites for the AEM 6.2 Release.

Template Editor & Policies

rlns1

Creating a template out of existing components has so far been a JCR based configuration. With AEM 6.2, we introduce an UI to compose and configure the templates visually. The Template Editor introduces a few new concepts that makes it easier to create a template in the 1st place, and allow components to be reused more often.

  • First, instead of using Sling includes in the components to nested them to a template, the nesting is stored in a new way - and while rendering the page merged with the content structure.
  • Second, with the introduction of the Policies it's possible to have component design configuration being reused.
  • Third, while technically not new, an easy way to manage the initial content that should appear when a new page is created with the template.

The Template Editor UI works very much like the Page Editor, with the difference that it starts with a blank canvas.

Content Fragments

rlns2

The ability to manage text-based content and it's associated assets as it evolves from draft to variations used in various experiences is at heart of Content Fragments (CF). With the introduction of Content Fragments in AEM 6.2, editorial staff gets an UI that is focused on curation and writing of copy.

  • Content Fragments are:
  • typed (based CF templates)
  • they can have various elements (think of recipes - with a list of ingredients, instructions and summary)
  • and variations (same content with different length or audience)
  • and associated content (a set of images or videos that shall be used in the same experience)

The Page Editor has been extended to support Content Fragments. Once a CF is used in an experience - the associated assets are made available to quickly compose.

Integration with Adobe Marketing Cloud

With AEM 6.1 - a new wizard approach was introduced to manage targeted and tested content powered by Adobe Target. With 6.2, the capabilities got extended to cover:

  • Audience Creation
  • Visual A/B Test configuration 
  • Extended goal definiton for Targeting Activities
  • Reports
  • Support Analytics as reporting source (A4T)
  • Ability to select the winning experience
  • Globalization

Multi-site Management Add-on

With AEM 6.2, offers and campaign activities are gaining their own inheritance model for multi-site deployments. The new 'Area' concept allows companies to define a scope of responsibility and assign branches of their sites into areas. This allows local teams to overlay and adapt campaign activities for their local markets, without losing central control.

Commerce Add-on

The Commerce Integrations were extended with support for Demandware and IBM Commerce

Screens Add-on

AEM Screens Add-on allows managing personalized experiences delivered in physical places. This could be retail locations, public places, vending machines etc. AEM Screens is ideal for customers that want to repurpose and expose existing content and experiences - and deliver them in a location optimized way.

Note: With AEM 6.2, Adobe is selectively working with customers on interactive signage projects. Please get in touch with your Adobe Account Manager to learn more.

Using AEM Screens for production use requires the AEM Screens Add-on License.

Full list of changes in AEM Sites and Add-ons

This section lists the full list of changes made to AEM Sites and Add-ons for AEM 6.2.

Component & Template Development

  • AEM 6.2 includes HTML Template Language V1.2
    • Allow data-sly-resource to include key-value map objects as resources (aka synthetic resources)
    • Allow OSGi services to be loaded through the Use-API
    • Performance improvements for Java Use-API
    • Performance improvements for WCMUsePojo helper methods
    • Completed variables available in server-side JS logic
    • Completed helper methods available in WCMUsePojo
    • Spec https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.2/SPECIFICATION.md
  • AEM 6.2 includes Sling Models V1.2
    https://sling.apache.org/documentation/bundles/models.html
  • Foundation Components
    • New account management components (Reset PW, Account Request and Update). The older versions are now deprecated. We recommend customers to revisit their usage of the actions and switch to the new versions.
    • Remove usage of loginAdministrative Sling API in various Foundation Components. We recommend customers that have overlayed the Foundation Component code might want to leverage the changes made for 6.2 in thier code.
    • Responsive Parsys: Add support for cq:cssClass property (CQ-49195)
    • Tables: Add support for 'Hidden Header' for better accessibility
    • List: Fixed an issue that the Descendant Pages wasn't working (CQ-60791)
    • Image Button: Fixed issue that image might not show if server is hosted on context path
    • Text Field: Fixed issue that might cause an JS error when validating length
    • Image: When a GIF has to be resized - a PNG is generated.
    • Flash: Support multiple flash elements on the page (CQ-61468)
    • Search components: Changes to the default search scope (CQ-68628)
      • by default the Platform search (com.day.cq.search.SimpleSearch) searches for pages and assets
      • by default the Foundation Search (com.day.cq.wcm.foundation.Search) searches for pages and assets
      • Foundation Search component: the searched node types are configurable through the dialog
      • JCR queries based on nt:hierarchyNode should be avoided
  • Installable package with tool to help converting Component Dialogs created for Classic UI to Touch-optimized UI dialogs. Is on PackageShare. (CQ-4857)

Page Authoring

  • Removed the 'slow double-click' action on in-place editors Text and Image. Use the action icon to enter in-place editing.
  • Content Finder (side-bar in Page Authoring) allows access to associated content as soon as one or more Content Fragment is used on the page
  • Support for in-place editing for statically included components that use RTE - that's when RTE is used not within paragraph system - but hard-coded into the component (CQ-42676)
  • The Content Finder (side-bar in Page Authoring) stays open when you have a large enough screen resolution
  • Changes to the Link creation process - now using the Path Browser UI
  • Allow multiple RTE and file update widgets in a component dialog
  • Allow RTE source editing in component dialog
  • Design Importer template and component now show proper action bar after import
  • Switching from Edit to Preview doesn't do a page reload anymore. There is a new option to see the page as published.
  • The 'Testing' tab in the Developer mode has been removed and replaced with a new Testing Console: /libs/granite/testing/hobbes.html

Content Fragment Authoring

This is an all new feature that allows creating and curating editorial content (text) in AEM Assets for easy reuse across channels. 

  • Content Fragment Editor with support for plain text, RTE and Markdown. Use Create button in Assets to create new Content Fragment.
  • Content Fragment templates to define the structure of a fragment. 
  • Ability to create variations within a Content Fragment that represent flavors of the same text for editorial or delivery purposes
  • Assign Collections of Assets to Content Fragment to associate and curate media content with editorial relevancy. 
  • Manage Content Fragment rendition in AEM pages with new Content Fragment component that allows full control over fragment structure during page authoring.

Site Administration

  • Changed default view from "Card View" to "Column View" - to make it quicker to reach the area the practitioner wants to work on.
  • New Template Editor that introduces a new way to create and manage templates and component policies - learn more on this page
  • Component Console that lists all the components and allow access to policies.
  • CSV export has dialog to define what should be exported
  • Search UI has been resigned. Either use the global search or open the 'Filter' rail to access search.
  • Deleting a large quantity of pages will cause an extra confirmation dialog to appear
  • Start workflow and create version actions are accessible directly from the in-context create action after selecting a page

Launches

  • A launch can contain multiple roots from different parts of a site. Before it was only possible to have one root node and it's children
  • It is now possible to add/remove pages to/from an existing launch. This allows using launches for use cases where content creation requires creating new pages. 
  • The promote function was optimized to be able to only promote the pages that in fact had changes (improves the speed to promote a large Launch)
  • New Launches Admin UI: /libs/launches/content/launches.html

Content Translation

  • Initial translation and re-translation of content in AEM Assets, including Content Fragments
  • Add content to a translation job with intelligent search filters, including modification status, translation status and analytics data. 
  • Add i18n dictionary content and tags to translation jobs. 
  • Send only modified pages to update translation, rather than entire translation job. 
  • Define do-not-translate configs that can be attached to pages in a translation job that should be excluded from translation. 
  • Machine translation widget as out-of-the-box component to easily configure pages for user-generated machine translation. 
  • Extended Translation API to allow approve and deny of individual translations that provides feedback back to translation provider
  • Translation preview API to enable translation technology partners to implement wysiwyg previews of translated content. 
  • Support for XLIFF 1.2 and 2.0 as output format for AEM translation jobs. 
  • Translation of AEM Forms.

Content Targeting & Simulation

  • Multisite support for targeted content, including the ability to inherit global activity experiences while adding local experiences where necessary.  
  • Ability to break inheritance of globally inherited targeted content on activity level. 
  • Support for inherited targeted content with server-side (AEM) or client-side (Adobe Target) targeting rules. 
  • New client-side JS segment engine (that repaces the Cleint-side Rules from Client Context)
  • New segment definition for Context Hub (that replaces Client Context)

Classic UI

  • Fixed an issue that prevented from reseting the language property in the Page Properites
  • Fixed an issue that might cause a JS error when handling images in properties with Internet Explorer 9
  • Fixed a regression that resources in the Reference Dialog were not click-able

Leverage Adobe Target with AEM

  • Reintroduced of A/B testing with a simplified workflow in the Page Authoring UI.
  • Define goals for Targeting campaign with UI parity to Adobe Target Standard
  • Result Report with deeplink into Target
  • Support Adobe Target running in A4T mode
  • Manage imported Audience from Adobe Target and ability to create new Audiences
  • The built-in mbox.js is version 46. We recommend customers to use DTM to leverage the latest version.

Leverage Adobe Analytics with AEM

  • Add support for "Ad-Hoc Link Tracking" in RTE Link creation with new plug-in (CQ-40099)
  • The built-in s_code.js is version H.27.4. We recommend customers to use DTM to leveage the latest version.
  • The built-in AppMeasurement.js version 1.4.1. We recommend customers to use DTM to leverage the latest version.

Leverage Adobe Campaign with AEM

  • E-mail authoring in Touch-UI Page Editor that are connected to Adobe Campaign (ACS and 6.1)

Multi-Site Manager Add-on

  • Starting AEM 6.2, reverting inheritance does not anymore automatically trigger a rollout. The modified behavior after reverting inheritance now allows to review changes in a blueprint before rolling them out to live copies. (CQ-64894)
  • Support for MSM/Livecopy in Scaffolding. Allow break inheritance when editing a livecopy via a scaffolding form.
  • Rollout performance improvements by streamlining read-operations during rollout.

Commerce Add-on

  • Implementation of the Commerce Integration Framework for IBM WebSphere Commerce
  • Implementation of Commerce integration with Demandware
  • Commerce Integration Framework supports wish-list functionality. Reference components with jcr implementation that leverages Communities UGC back-end
  • Collection and query-based product collections

Screens Add-on

Note: With AEM 6.2, Adobe is selectively working with customers on interactive signage projects. Please get in touch with your Adobe Account Manager to learn more.

Using AEM Screens for production use requires the AEM Screens Add-on License.

Device Control Center (Documentation)

  • Location Management: organize display deployments in hierarchy
  • Display Management:
    • define display deployment configurations (set of players and screens)
    • Zone-2-Player mapping, used for Player-fallback on 2nd screen
    • Channel Linking: dayparting/schedule rules, idle vs interactive mode with fallback, instant channel switching
  • Channel Management: manage content to be assigned to players
  • App Management: manage interactive screen apps
  • Device Management:
    • register new players and assign to display
    • Device Dashboard to see status and set configuration
    • Request log file from Player
    • Clear the player offline cache

Channel Editor (Documentation)

  • Linear Sequence Channel
  • Transitions between sequence items
  • App Channel
  • Leverage ContextHub to location/viewer personalization

Player

  • Support Player Platforms: Android, iOS, macOS. Download Site - Install Documentation
  • Leverages GPU for accelerated rendering (on macOS per default, on Android if GPU is supported)
  • Supported touch overlays/displays
    • PQ Labs 
    • MultiTaction
    • HID compatible
  • Player-2-Server authentication via setup registration sequence
  • Heartbeat: Player pings server in regular interval, allows remote monitoring in DCC
  • Remote-Screenshot: Request current visible content via DCC as Screenshot
  • Remote Inspection: Ability to debug player runtime from remote (Android only)
  • Over-the-air Firmware Update: Player-side and remote DCC requested firmware update.
  • On-demand Caching: Leverage the 'browser' cache of the player
  • Offline-Mode with pre-loading: use AEM ContentSync to download complete channels to Player storage
  • Channel Switcher UI (press lower left corner):
    • Switch channels
    • Reload Player
  • Admin UI (press upper left corner):
    • Registration status
    • System Info & Show free Storage
    • Channel Status
    • Settings
    • Ability to disable Adobe UI & Channel Switcher
    • Clean offline cache
    • Built-in channel to test touch input
    • Reload Player
    • Update Firmware
  • Attention Visual: for idle mode to indicate that there is an interactive on the screen
  • Channel-Switch Rules Engine with Offline support
  • Time-synced Play: Using the player clock to sync channel among multiple players
  • Sequence visibility API for components
  • Built-in support for ContextHub
  • Built-in support for Adobe Mobile SDK for Analytics

Za ta izdelek je bila izdana neprenosljiva licenca za priznanje avtorstva, nekomercialno uporabo in skupno rabo pod enakimi pogoji 3.0  Objav v storitvah Twitter™ in Facebook ne urejajo pogoji pogodbe Creative Commons.

Pravna obvestila   |   Pravilnik o zasebnosti v spletu