AEM CaaS to expose content with Absolute URL or Externalized Links in Model Json

Avatar

Avatar

ManojSj

Avatar

ManojSj

ManojSj

02-12-2020

Description -

Currently offered CaaS feature allows content to be available as a Json for consumer systems. But there is no feature to either transform or update the DAM and Content links with the Absolute URL[Fully Qualified URL, Externalized URL with server details etc..] for either Content/Experience Fragments or  Custom Components with a single pattern/approach.


Why is this feature important to you -

It helps onboard the consumers system for readily consuming the content

Eliminates custom logic at individual component level or customization for core components/exporter logic [For content/experience fragments]

Leverage the recommended OOTB logic and have single pattern for content/experience fragment and custom components 

 

How would you like the feature to work -
Feature should have a enable/disable logic with configuration associated with it

Feature should have a logic to allow transformation for specific patterns for links and configuration associated with it


Current Behaviour -

All the content links are exposed as /content/* or /content/dam/* which cannot be used readily by the consumer system accessing model json via API

CAAS exporter Sling Model
3 Comments

Avatar

Avatar

Nirmal_Jose

MVP

Avatar

Nirmal_Jose

MVP

Nirmal_Jose
MVP

17-12-2020

This seems to be really good feature. A OOTB setup to externalise a pathfield using externaliser or sling mapping configuration on the page model exporter

Avatar

Avatar

hamidk92094312

Employee

Avatar

hamidk92094312

Employee

hamidk92094312
Employee

25-12-2020

Hi @ManojSj 

Thanks for submitting this feature request. We are further looking into the feasibility of the request and update this thread when an update becomes available.

Status changed to: Investigating

Avatar

Avatar

hamidk92094312

Employee

Avatar

hamidk92094312

Employee

hamidk92094312
Employee

28-01-2021

@ManojSj 

This request has been raised to the product team via the Jira CQ-4314771. The product team will triage this request to verify feasibility based on prioritization model. This post will be updated according to the Jira request status.

Status changed to: Investigating