--- canonical: https://amplience.com/developers/docs/release-notes/2019/ title: Amplience release notes 2019 description: Summary list of the releases performed during 2019 for Amplience products, describing the new features, enhancements and updates that have been implemented. audience: Business User date_published: 2026-06-25 date_modified: 2026-06-18 unlisted: true --- # Amplience release notes 2019 A summary of product releases for 2019, covering new features, enhancements, and updates across Dynamic Content, Content Hub, and Dynamic Media. > **Note:** For all release notes, see [release notes by year](https://amplience.com/developers/docs/release-notes/#earlier-release-notes). ## Extensions *6 November 2019:* Introduced **Extensions** - small web apps that let developers customise the content editing form in Dynamic Content. Extensions replace the standard rendering for a property (e.g. a slider instead of a text input, a map picker, an enhanced rich text editor) and can call third-party services. Built using the Extensions SDK (JavaScript/TypeScript), extensions can be hosted anywhere and registered once per hub for reuse across schemas. Also included: a revamped Management API reference with improved navigation and OpenAPI spec download. ## Content item properties pane *9 October 2019:* Added a **properties pane** to content items in Dynamic Content, surfacing key metadata (content ID, schema, status, dates) without needing to open the item. Makes it easier to inspect and copy item details directly from the content library. ## JSON schema draft 7 support *25 September 2019:* Dynamic Content content type schemas now support **JSON Schema draft 7**, enabling use of newer validation keywords such as `if`/`then`/`else`, `readOnly`, `writeOnly`, and `$comment`. Existing draft 4 schemas continue to work unchanged. ## JPEG 2000 support *21 August 2019:* Dynamic Media now supports **JPEG 2000 (JP2)** as an output format. JP2 delivers significantly smaller file sizes than standard JPEG at equivalent quality, particularly beneficial for high-resolution images. Requested via `fmt=jp2` in the image URL. ## Renaming assets in Content Hub *31 July 2019:* Assets in Content Hub can now be **renamed** directly from the asset panel, without needing to re-upload. The rename updates both the display name and the underlying asset filename. ## Content Hub and Dynamic Content UI enhancements *31 July:* Assets in Content Hub can now be renamed from the contextual menu or properties pane, with published assets automatically republished under their new name. New publish status icons make it clearer when an asset has changed and needs republishing. Also included: improved SFCC webhook error codes and an updated integrations home page. ## Content type browser enhancements *24 July 2019:* The **content type browser** (used when linking content items or choosing a type to create) was updated with improved search, filtering, and visual layout, making it faster to locate and select the right content type in large hubs. ## Webhook UI enhancements *17 July 2019:* Improved error responses in the webhook activity log to make failures easier to diagnose, and broader **UI enhancements** including clearer status indicators, easier navigation between webhook configurations, and better handling of webhook event history. ## Schema editor - sample JSON output and content references *10 July 2019:* The **Schema Editor** now shows a **live sample JSON output** preview as the schema is built, so developers can see the exact structure of the content that will be returned by the API. Also added: first-class support for **content references** as a property type, with a dedicated snippet in the editor. ## Schema editor - schema versioning *12 June 2019:* Introduced **schema versioning** in the Schema Editor. Developers can now create new versions of a content type schema while preserving the previous version, allowing existing content to remain valid and enabling a controlled migration path for schema changes. ## Schema editor enhancements *17 April 2019:* Several usability improvements to the **Schema Editor**: auto-complete suggestions for property names and types, inline validation feedback, and faster navigation between schema sections. Reduces the time needed to build and iterate on schemas. ## Salesforce Marketing Cloud integration *10 April 2019:* Introduced an integration with **Salesforce Marketing Cloud**, enabling content in Dynamic Content to be surfaced in email and journey campaigns. Content items can be referenced and previewed within Marketing Cloud, supporting personalised content delivery through email channels. ## Image recognition facets in Dynamic Content media browser *3 April 2019:* Image recognition metadata (objects, faces, text - introduced in the February release) is now exposed as **searchable facets in the Dynamic Content media browser**. Authors can filter images by detected labels (e.g. "handbag", "outdoor") when adding assets to content items, without needing to switch to Content Hub. ## Schema editor and SFCC configuration UI *13 March 2019:* Two developer-focused improvements: further **Schema Editor** enhancements including richer property type snippets, and a new in-app **configuration UI for the Salesforce Commerce Cloud (SFCC) integration**, replacing manual setup steps with a guided form for entering storefront and API credentials. ## Content item status enhancements *6 March 2019:* Extended the **content item status** system with additional states and clearer visual indicators. Authors can now see at a glance whether content is in draft, in review, published, or archived, improving workflow visibility across teams. ## Content item status and repository settings *13 February 2019:* Introduced the initial **content item status** feature, allowing content items to be marked with workflow states. Also added: **Repository Settings**, giving hub administrators control over repository-level configuration such as available locales and content types. ## Setting event locales and filtering *6 February 2019:* Events in the planning/scheduling view can now be **assigned locales**, and the timeline, calendar, and list views can be **filtered by locale**. This makes it easier for multilingual teams to manage localised editions and campaigns independently. ## Image recognition *5 February 2019:* Introduced an **Image Recognition service** for Content Hub (available as an account add-on). When enabled, images uploaded to Content Hub are automatically analysed using machine learning to detect objects, faces, text, and unsafe content. The results are stored as searchable metadata labels, enabling filtering by detected content (e.g. "bag", "female", "20-40") directly in Content Hub. ## Locale UI enhancements *30 January 2019:* Updated the **planning and production interfaces** to better surface locale context. Locale selectors were added to the production view and scheduling calendar, making it clearer which locale variant of content is being worked on or scheduled. ## Salesforce Commerce Cloud integration - localisation *9 January 2019:* The **Salesforce Commerce Cloud integration** was updated to support **localisation**, allowing locale-specific content variants to be mapped to SFCC storefront locales. This enables different language and regional content to be delivered to the correct storefront without additional middleware.