since ‎02-01-2020
‎13-04-2021
mikeetiuPH
Level 1
Re: Descriptions for smart crops and renditions
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
@hamidk92094312 - we just need a way to indicate where the different smart crops should be used. Like for example, there are multiple smart crops and each of those smart crops is used for specific channels and modules. Without an information description, it's hard for our users to know where they should be used unless they use a cheat sheet. It will be good if we can display descriptions for the smart crops

Views

45

Likes

0

Replies

0
Re: Granular control of access to a specific fields/group of fields by users/groups (i.e. not all or nothing to edit metadata)
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
@hamidk92094312 - we can't. Coz it's always all or nothing. We cannot target a specific metadata field in the ACL

Views

39

Likes

0

Replies

0
Re: Ability to hide Publish to AEM option
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Hi @hamidk92094312 - It covers use cases where AEM assets will be used as an enterprise DAM wherein the DAM and Sites are two different instances. For enterprise DAMs, the publishing of assets should be done in the Sites instance, not in the DAM. Dynamic Media though makes sense but the publishing action to a publish server is not given that the website will be in another instance.

Views

59

Likes

0

Replies

0
Re: Smart crops export to multiple format
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Hey @hamidk92094312  - where should I log Dynamic media reuqests? 

Views

39

Likes

0

Replies

0
Re: Smart tag keyword exclusion list
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Thank you! 

Views

48

Likes

0

Replies

0
Re: Ability to hide Publish to AEM option
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Hi -I am referring to AEM Assets. Here are the screengrabs of the items I would like to get turned off:

Views

136

Likes

0

Replies

0
Ability to hide Publish to AEM option
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: Publish to AEM option cannot be hidden Use-case: Even if we don’t have a publish server, we cannot unhide the publish to AEM button Current/Experienced Behavior: Publish to AEM option cannot be hidden Improved/Expected Behavior: Have the ability to hide the publish to AEM button Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicab...

Views

171

Likes

0

Replies

4
Smart tag keyword exclusion list
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: There is no exclusion or blocked keywords list that can be configured for Smart tags Use-case: Currently, there is no way to prevent Sensei from adding some keywords via smart tags. This is important since in our organization, we cannot simply tag assets with race, gender and ethnicity tags without approval or consent Current/Experienced Behavior: There's no exclusion list Improved/Expected Behavior: Have a keyword exclusion list Environment Details...

Views

114

Likes

0

Replies

3
Capacity for more smart crops
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: We were advised to only create 5 smart crops since there will be performance implications if there are more. THere's no limit in the UI but what Adobe said, we should not exceed 5 Use-case: Our organization needs a lot of smart crops since the assets in DAM are being used on different channels. Having a limit of 5 will make it difficult for us to support our customers;' needs Current/Experienced Behavior: Only 5 smart crops are requested to be creat...

Views

81

Likes

0

Replies

1
Smart crops export to multiple format
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: Currently, we cannot export smart crops to PNG or any other format. The only supported format is JPG. This is quite tricky since in our org, the recommended image format is PNG Use-case: See above Current/Experienced Behavior: See above Improved/Expected Behavior: Be able to select the format output for smart croups Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if ...

Views

95

Likes

0

Replies

2
Granular control of access to a specific fields/group of fields by users/groups (i.e. not all or nothing to edit metadata)
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: No granular control of access to a specific fields/group of fields by users/groups (i.e. not all or nothing to edit metadata) Use-case: Currently, we cannot prevent users from updating a certain field only or groups of fields in the properties. It’s either the user gets to edit all or none. This impacts creative rating and commenting. Ideally, we would want to allow asset consumers to be able to post comments or reviews, rate assets but not edit any...

Views

91

Likes

0

Replies

2
Descriptions for smart crops and renditions
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: Only titles can be added to smart crops and renditions which can make it hard for consumers to know when to use a rendition and what is it for (e.g. page components, channels, pages) Use-case: If the renditions list is long, it's confusing for users to know what reset to use for a certain use case Current/Experienced Behavior: Descriptions cannot be added to renditions Improved/Expected Behavior: Add the ability to add renditions Environment Details...

Views

110

Likes

0

Replies

2
Have a better control over cookies in Adobe
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Experience Cloud
Currently, in the experience cloud extension, we cannot prevent everest cookies from dropping without blocking ECID. We are not 100% sure how they are tied up to each other. Since there are a lot of data privacy regulations now, I think it will be best to have controls over all Adobe cookies individually.

Views

1.0K

Likes

0

Replies

0
Adobe Launch - Quick view Indicator to easily see latest code version in prod and staging
Avatar

mikeetiuPH

mikeetiuPH
- Adobe Analytics
To find the last version that was in production or in a library, you can go into the Publishing tab, open a library or create a new one, then in the Add Resource drawer you find the object in question and manually click through the versions until you see an indicator that it is in prod or in a library that you know has been tested.

Views

518

Likes

0

Replies

0