Hi Sandeep,Also it is worth to check the MAC os version, the PDF rasterizer is not supported for Mac OS. See belowTechnical Requirements Thanks,Ashutosh

Re: Centralized AEM DAM / Enterprise DAM ashu4pma - Adobe Experience Manager

-> Would Brand Portal would be integrated with Dynamic Media as well?yes, see [0]Also, see other integration options[1][2] available with the AEM.Thanks,Ashutosh[0] Overview of AEM Assets Brand Portal [1]Asset link sharing [2] Configuring AEM Assets integration with Marketing Cloud and Creative Cloud

Re: AEM pdf Raterization for pdf subassets ashu4pma - Adobe Experience Manager

Hi Sandeep,Can you confirm if the following path exists and can be executed through terminal?"/opt/aem/crx-quickstart/launchpad/felix/bundle539/data/binaries/PDFRasterizer, -d, -p, *, -s, 1280 "If yes, please check how many AEM processes running at your instance. And also confirm your environment (Linux or Mac)?Thanks,Ashutosh

Re: Assets list view orderable fields ashu4pma - Adobe Experience Manager

The sort option on Name column is not supported in AEM 6.3 & AEm 6.4.Toggling property sortable(Boolean)=True at node /libs/dam/gui/content/commons/availablecolumns/ is not the right solution, it doesn't work when there are more than 40 asset/fodler(s) at the same level.For less than 40 asset/folder(s) - Client Side sorting usedFor greater than 40 asset/folder(s) - Server Side sorting usedSo above workaround doesn't work in Server Side sorting case.To achieve this at the project level, you have ...

Re: Can metadata schema form auto adjust to contents? ashu4pma - Adobe Experience Manager Assets

there is no OOTB filed predicate to cater this use case offered by Assets Metadata Schema Editor. There is text area componen[0] offered by the Granite's platform which can be used to add a custom field predicate. All field predicates at Metadata Schema Editor are the wrapper of Granite platform's form elements, be it textfield, sectionheader, dropdown etc.Moreover [0] takes rows, cols and max-length as an input parameter to control the textarea height/width on rendering, these configurations sh...

Re: Crop renditions ashu4pma - Adobe Experience Manager Assets

The non-destructive image renditions (through image modifiers) is a key feature of Image Server (part of Dynamic Media SKU). DM license is needed for the extensive support around this.Just in case if you need to generate image renditions of different dimensions on the fly, there is a OOTB servlet "com.day.cq.wcm.core.impl.servlets.ThumbnailServlet" which use Layer API and generate the expected thumbnail on the fly.For e.g. if user navigates to /content/dam/test/image1.jpg.thumb.319.319.png then ...

Re: AEM 6.3: Need to implement auto search suggestions for DAM Asset collection ashu4pma - Adobe Experience Manager

No, AFAIU the Search Suggestion for Collections needs to be achieved at project level through custom implementation. No OOTB feature having this kind of support or close to this requirement.You could use OmniSearch API to integrate the suggestions with OmniSearch result page.https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/reference-materials/javadoc/com/adobe/granite/omnisearch/api/core/OmniSearchService.html#getSuggestions(org.apache.sling.api.resource.ResourceResolver,%20...

Re: dam:size is not added to metadata of Asset ashu4pma - Adobe Experience Manager

I am not able to reproduce this in AEM 6.2 (latest SP + CFP), I can see dam:sha1, dam:size and dam:extracted are getting saved on metadata node for all type of files including mp3/mp4. Is there any customization around asset processing/handling done in your case? Can you please check if there is any error in logs (error.log) logged during asset processing (dam_update_asset) workflow? Share the same to understand the issue better.Thanks,Ashutosh

Re: AEM 6.4 Assets:Expose Content Fragment as Json (Without associating to pages) ashu4pma - Adobe Experience Manager

I don't think there is an option of exporting JSON without using Sites (Pages).Thanks,Ashutosh

Re: External DAM integration with AEM 6.x ashu4pma - Adobe Experience Manager

The central DAM should be configured similar to cloud service configuration (like Marketing Cloud, Brand Portal etc.) at AEM. Then replication sync (on demand or cache) is something consider to get all assets from central DAM to AEM. Then rest of the flow/experience works same since assets are now duplicated and works as local in AEM. But keeping the local copy in sync with central DAM would be a challenge and you can check if that is the use case or not.Please share the exact use case to talk m...

Re: Preventing SVG Renditions ashu4pma - Adobe Experience Manager

It is a regex match, so please escape the metacharacter '+'. Please try with following: "skip:image/svg\+xml" at "Thumbnail Process" step.Thanks,Ashutosh

Re: Asset direct link is downloading not open asset on new tab ashu4pma - Adobe Experience Manager Assets

I didn't get this, What update exactly you are looking for? As I have mentioned in first reply, it is a security request filter at sling level responsible for this, uncheck the option (Enable Content Disposition for all paths) at filter takes you to the old behavior. It is a not a bug rather security improvement.

Re: Assets Search: ashu4pma - Adobe Experience Manager

Can you share the search GET request parameters being generated post your changes? It is very comprehensive to figure out what query is going to trigger by looking at GET request parameters.The request I am looking is for following URL:http://:/mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html

Re: Auto-populate asset metadata schema ashu4pma - Adobe Experience Manager

Make use of cq:lastReplicationAction Property. You can use Cascading Metadata OOTB[0] in 6.4 to set the visibility rule dynamically (i.e. when cq:lastReplicationAction=Activate). For previous releases, customize the same visibility rule using custom validator.Thanks[0]Adobe Experience Manager Help | Using Cascading Metadata in AEM Assets

Re: Assets Search: ashu4pma - Adobe Experience Manager

Add property predicate to add following:property=jcr:content/metadata/dc:titleBut look at the form and grouping once you added the Property Predicate. Since grouping support is not available for authoring, it will be auto populated. So in the final form, say this custom property comes as 22_property=jcr:content/metadata/dc:title, then you should use hidden predicate to add following:"22_property.operation=like" Inspect the Search GET request parameters at browser's console to diagnose it better.

Re: Auto-populate asset metadata schema ashu4pma - Adobe Experience Manager

When asset gets replicated, the replication status properties[0] are already set on Asset's metadata by the platform and same (precisely cq:lastReplicated ) should be used. No need to use Processing Profile for this use case, you are right it is only applicable to static values (like Tags, Description etc.)[0] Custom Node Types

Re: Auto-populate asset metadata schema ashu4pma - Adobe Experience Manager

Yes that is expected. Asset's metadata doesn't have any value and that was the first point in my previous reply "how asset is going to get the values".Applying Metadata Schema AA to Folder BB means, assets under the folder BB would use this schema AA when open through metadata editor. The values on assets under BB can be set using metadata editor.For auto population of metadata values on assets under BB can be achieved through Processing Profile (different feature).You have to use both Processin...

Re: Assets Search: ashu4pma - Adobe Experience Manager

You can use wildcard with Property Predicate or with any other predicate. Say following works well for Property Predicate:# LIKEproperty=propertyNameproperty.operation=likeproperty.value=%value%API: Query Builder API Use "Hidden Predicate" to add "property.operation=like" at Asset's search form editor.

Re: Error Message when changed optional field to mandatory for metadata schema. ashu4pma - Adobe Experience Manager

Replied, both questions are bit open ended, expecting more details to converge. Thanks

Re: Auto-populate asset metadata schema ashu4pma - Adobe Experience Manager

-> it should update the date field to current date.Do you mean asset's metadata should update "Publication Date" as when this schema got applied to parent folder. I am not sure if I have understood use case mentioned here, but this can be achieved using Processing Profile[1]. Once you get the "Publication Date" field auto populated (through [1]) on asset's metadata, then it should be mapped in metadata schema.Out of Two metadata fields (type Date) which needs to be displayed at metadata editor, ...

Re: Assets Search: ashu4pma - Adobe Experience Manager

Please elaborate which predicate you have added. "Fulltext Predicate" may not work as it becomes obsolete after OmniSearch introduced in 6.2 and removed in subsequent release.If you have used "Property Predicate" then it should work. If it is not working even after using "Property Predicate" then share following details:1. Values provided to this predicate (property name, placeholder etc.)2. The search GET request parameters (open browser's debugger and trigger search)

Re: Error Message when changed optional field to mandatory for metadata schema. ashu4pma - Adobe Experience Manager

Yes it may not work as I can see card's path is hardcoded to /libs at [1]. The "/libs/" should be removed from [1] to allow overlaying. You can log a product's enhancement request to get it done. Thanks[1]/libs/granite/omnisearch/content/metadata/asset

Re: Error Message when changed optional field to mandatory for metadata schema. ashu4pma - Adobe Experience Manager

Fine it will be Line #52 if AEM 6.2 + latest CFP./libs/dam/gui/coral/components/admin/contentrenderer/card/assetomnisearch/assetomnisearch.jsp#L52

Re: Error Message when changed optional field to mandatory for metadata schema. ashu4pma - Adobe Experience Manager

The cards rendered on Search Page has different code and including CardBanner using absolute URL. Please check the component at [2] Line no. 54You should overlay this as well, and refer to /card-banner.jsp overlaid in /apps. Considering you are asking this for AEM 6.3, since this has been fixed in 6.4.[2]/libs/dam/gui/coral/components/admin/contentrenderer/card/assetomnisearch/assetomnisearch.jsp#L54

Re: Crop renditions ashu4pma - Adobe Experience Manager Assets

Can you confirm if the Dynamic Media is enabled? if not use [0] to enable it.In Assets (when Dynamic Media is disabled), the image edit operations (cop, rotation etc.) results into destructive binary edit. Where as in case of Dynamic Media enabled, the image edit operations are performed using modifiers and doesn't modify the binary. Refer[1] for more details on DM.[0] Configuring Dynamic Media with Feature Packs 14410 and 18912 [1] Adding Dynamic Media Assets to Pages

Re: Asset direct link is downloading not open asset on new tab ashu4pma - Adobe Experience Manager Assets

Yes uncheck the checkbox(Enable Content Disposition for all paths).

Re: Asset direct link is downloading not open asset on new tab ashu4pma - Adobe Experience Manager Assets

This was a security fix at Sling level, the disposition filter has been added to force this behavior. See [0].To undo this behavior (not recommended), you can disable the component[1].Thanks[0] SLING-4883Extend content disposition filter protection to jcr:data[1] org.apache.sling.security.impl.ContentDispositionFilter[2] http://10.42.36.65:4502/system/console/components/org.apache.sling.security.impl.ContentDispositionFilter

Re: Error Message when changed optional field to mandatory for metadata schema. ashu4pma - Adobe Experience Manager

Hi,Not sure which AEM version you are talking about here, my reply assumes it is for 6.4 (though most of it will be applicable even for previous versions too).-> expectation was it gives an error if any those mandatory fields are is not authored for new assets . For this definition of "new assets" needs to be shape out first, to keep it simple, I am considering assets which are ingested in last 24 hours are new assets.-> Is there a way to not to display such error for the already existing assets...

Re: Remove Insights tab in DAM Asset Meta Data ashu4pma - Adobe Experience Manager

Then I would consider this as a product bug and overlay extension should work.The form under /libs goes to /conf when extended at the project level (Administrator role). All customizations needed at a project level for OOTB forms /libs go to /apps. (Solution Integrator role)Say at the project level, it is decided to hide Insight Tab so that any user admin can't see when metadata schema is being defined under /conf for the project. Then OOTB form offered from location /libs should be extensible t...

Re: Remove Insights tab in DAM Asset Meta Data ashu4pma - Adobe Experience Manager

The Insights form exist at location [0]. Try overlay the form using [1] and hide. If it doesn't work then log a hotfix request to get fix from Product.Thanks[0] /libs/dam/content/schemaeditors/forms/insights[1]Apache Sling :: Resource Merger (org.apache.sling.resourcemerger)

Likes from

User

Count

Guidelines

Cookie preferences