The article delves into publishing image presets, metadata schemas, and custom search facets from AEM Author instance to Brand Portal. Publishing capability enables organizations to reuse the image presets, metadata schemas, and search facets created/modified at AEM Author instance thereby reducing duplicate efforts.
The capability to publish image presets, metadata schema, and search facets from AEM Author instance to Brand Portal is available AEM 6.2 SP1-CFP7 and AEM 6.3 SP 1-CFP 1 (184.108.40.206) onwards.
Image presets are a set of sizing and formatting commands that are applied to the image at the time of image delivery. Image presets can be created and modified at Brand Portal. Alternatively, if AEM Author instance is running in dynamic media mode then users can create presets at the AEM Author and publish them to AEM Assets Brand Portal, and avoid re-creating the same presets at Brand Portal.
Once the preset is created, it is listed as dynamic rendition on asset detail renditions rail and download dialogue.
If AEM Author instance is not running in Dynamic Media Mode (customer has not purchased Dynamic Media), then the ptiff rendition of the assets are not created at the time of upload. Image presets/ dynamic renditions work on ptiff of an asset, so if ptiff is not available on AEM Author then it is not available on the Brand Portal as well. As a result for this, no dynamic renditions are present in renditions rail of asset details page and download dialogue.
When users click Publish to Brand Portal the image presets are queued for publishing. Users are advised to monitor the log of the replication agents to confirm if the publish was successful.
Metadata schema describes the layout and properties that are displayed on the properties page of asset/ collections.
If users have edited the default schema on AEM Author instance and are willing to use the same schema as default schema on the Brand Portal, they can simply publish the metadata schema forms to Brand Portal. In such a scenario, the default schema at Brand Portal is over-ridden by the default schemas published from AEM Author instance.
If users have created a custom schema on AEM Author instance, they can publish the custom schema to Brand Portal instead of re-creating the same custom schema there. Users can then apply this custom schema to any folder/ collection in Brand Portal.
Default schemas cannot be published to the Brand Portal if they are locked at the AEM instance (that is they are unedited).
If a folder has a schema applied on AEM Author instance, the same schema must also exist on the Brand Portal to maintain the consistency in the asset properties page on AEM Author and Brand portal.
When users click Publish to Brand Portal, the metadata schemas are queued for publishing. Users are advised to monitor the log of the replication agents to confirm if the publish was successful.
If you are willing to use custom search form Assets Admin Search Rail from AEM Author, then instead of re-creating the same form on Brand Portal you can publish the customized search form from AEM Author instance to Brand Portal.
Locked search form Assets Admin Search Rail on AEM Assets cannot be published to Brand Portal unless it is edited. Once edited and published to Brand Portal, this search form overrides the search form on Brand Portal.
The Unpublish from Brand Portal action leaves the default search form on Brand Portal, and does not restore to the last search form used before publishing.
- Few search predicates are not applicable to search filters on the Brand Portal. When these search predicates are published as part of the search form from AEM Author instance to Brand Portal, they are filtered out. Users, therefore, see less number of predicates in the published form at the Brand Portal. See search predicates applicable to filters on Brand Portal.
- For Options predicate, if a user is using any custom path to read options at AEM Author instance, it won't work at the Brand Portal. These additional paths and options are not published to Brand Portal with the search form. In this case, users can select the Manual option in Add Options within Options Predicate to add these options manually at Brand Portal.