Request for Feature Enhancement (RFE) Summary: Have the option to disable auto-unpublishing of assets when they expire in AEM Use-case: We don't want assets to get unpublished when they expire because it will cause broken images appearing in our website Current/Experienced Behavior: When the out-of-the-box expiration field in AEM is used, an expired asset gets automatically published Improved/Expected Behavior: Have the option to disable auto-unpublishing of assets when they expire in AEM Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Adobe AEM Assets allows user to email the download to another user. The email creates a link to a zip file, sends it from a no-reply address and looks suspicious, like a security breach. No sender information is included in the email. Here are the steps to reproduce: Select 1 or more Assets Click “Download” In the Download dialog, choose “Email” and enter the user’s email address AEM will generate a ZIP file of the asset(s) and email the user. Use-case: Current/Experienced Behavior: The email feature creates a link to a zip file, sends it from a no-reply address and looks suspicious, like a security breach. Improved/Expected Behavior: The email body should include sender's username or email address, so the email can be verified and authenticated by the recipient. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.8 Customer-name/Organization name: Wakefern Food Corp Screenshot (if applicable): Sample email that AEM Assets sends - you can see how suspicious this looks: Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Feature Enhancement - Manage tags in Collections. Currently, in order to manage tags of assets included in a collection, the user needs to open the assets through the folder taxonomy Use-case: We have users of Assets (DAM) who want to manage tags without leaving the collections UI Current/Experienced Behavior: Smart tags can not be managed through the collection UI Improved/Expected Behavior: There is an ability to manage smart tags in the collections UI Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCs Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In the reprocess function, add an option to just process certain items like presets, metadata, etc Use-case: Select an asset or folder and then hit reprocess. In the reprocessing dialog, the only option is "Full process". It will be good if there is an option to reprocess --- metadata, presets, smart crops Current/Experienced Behavior: Select an asset or folder and then hit reprocess. In the reprocessing dialog, the only option is "Full process". Improved/Expected Behavior: Have an option to select --- metadata, presets, smart crops Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The existing aem-event-proxy-skyline source code distribution enforces assumptions that are incompatible with many potential use cases, and future development in this direction should relax these constraints on AEM's role as an Adobe I/O event producer. Use-case: * Developers should be empowered to fire custom Adobe I/O events from publishers, directly from custom servlet code. For example, POST requests from customers containing PII that must be sent to an Adobe I/O runtime for correlation with anonymized aggregate metrics from Analytics. * In a a multisite hosting scenario, it is plausible that a Firefly App would be deployed to the organization that is only interested in consuming events originating from a particular regional site, without having to introspect the event payload to determine if the associated request resource actually maps to the appropriate domain. Of course, this is an established pattern for Analytics and Target cloud service integrations in AEM already.* AEM developers working on site functionality should be able to iterate together with Project Firefly developers to evolve event payload formats without being forced to conform to XDM activity stream types. Current/Experienced Behavior: * IMS Configurations cannot be replicated to publishers, even though system user nodes and keystores are replicable.* (Aem-event-proxy) Workspace configuration is not runtime configurable.* (Aem-event-proxy) Adobe I/O integration in publish environment is not supported and not enabled with distributed sources.* (Aem-event-proxy) Only one adobe I/O configuration is supported for the environment* (Aem-event-proxy) For custom events, API client code must flatten complex event payloads to the OSGi event structure, with no synchronous feedback. Improved/Expected Behavior: * All Adobe I/O Configuration and IMS Configuration active in the publish environment should be modifiable at runtime by users authorized to use the Configuration Browser and IMS Technical Accounts consoles, respectively, in the author environment. * AEM should allow users to create multiple Adobe I/O Configurations (and their associated IMS Configurations and CSM registrations) and should support context-aware association to zero-or-more content trees. * CSM registration should be a deterministic activity occurring on the author environment, with the registration status of an Adobe I/O Configuration made visible to the user, and with reasonable ability to change labels and descriptions of the registration to support better management of integrations across the organization.* Due to the synchronous nature of a servlet execution, the API provided by the native integration should support synchronous feedback to the servlet for the backend submission to eventsingress, in case the the request should be reattempted by the client. In other words, the AEM integration should not add an asynchronous layer like Sling Jobs, unless this behavior in the context of AEM is specifically desired by the client. * XDM Schema Event mapping should be a feature available in the API, but not required by the fundamental postEvent method signature. Environment Details (AEM version/service pack, any other specifics if applicable): Skyline Customer-name/Organization name: Bounteous Screenshot (if applicable): Code package (if applicable):
Many customers today need the AEM Versions to be kept and not purge due to legal requirements.At any given point of time , customers may want to restore to any previous versions, can view differences, go in timewarp mode with all the previous versions of a page. Over a period of time , the jcr:VersionStorage can grow to more than 100 million nodes which makes indexing , Inplace Upgrade and overall system performances slow. We need ability in AEM where jcr versions can be offloaded to an offloaded instance / shared mount and all the OOTB functionalities like Restore, TimeWarp, Version history / difference should work AS IS without the need of custom code/ implementation.
Hello,our client is using the Multi-Site Management (MSM) features a lot.In a live copy, only a full page can be synchronized with the source.As rolling out a component to the live copies is possible already, they would like to have a feature for synchronizing a page in the live copy on component level as well.Business Value: This will reduce risks of publishing non-approved content and also will reduce communication effort within the editorial team.Can this be added to AEM?Thanks & Many regardsHendrik
Request for Feature Enhancement (RFE) Summary: Is it possible to increase the selection or clickable area on an asset or folder rather than enabling the selection only on the thumbnail area? Use-case: Current/Experienced Behavior: Selection allowed only on thumbnails Improved/Expected Behavior: Clicking anywhere on the folder or file name should select the same Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.4 service pack 7 Customer-name/Organization name: Oxford Properties Screenshot (if applicable): Code package (if applicable):
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 (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
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 metadata. Due to this existing restriction, only our group librarians can do that. Current/Experienced Behavior: No flexibility to set-up granular permissions Improved/Expected Behavior: Be able to set-up granular permissions Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
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 applicable):
{{SP_Send_Alert_Info}}のトークンのリンクから顧客のアクティビティログにアクセスすると、英語で表示されてしまいます。 マイアカウントの言語設定と同じ言語（日本語）で表示したいのですが、アドビカスタマーサポートに伺った所、まだ日本語に変更する機能はないとのこと。 良い機能ですので、是非マイアカウントの言語設定と同じ言語（日本語）で表示出来るよう今後改善検討いただけると幸いです。
We have requestors who create updates to many preexisting jobs. They would like the ability to look at past requests, Duplicate, edit and submit as a new request. This will save them from have to enter all of the information again when only a few fields change every time.
It would be great if we could get some kind of "Are you sure you want to delete?" pop-up when we are deleting pinned pages in the navigation bar.On multiple occasions, I've accidentally clicked on the "X" and deleted one of my pinned tabs.
Users in our instance would like the ability to display projects that are shared with them in their projects screen or in a dashboard. I'm told by Support there is currently no way to do this. This would give greater visibility since any project that have involvement in would display in the view for them.
It’d be helpful if a user could flag or mark a notification as urgent (similar to marking an email as urgent). Whether we manage our notifications by email or within the program, we’re flooded with dozens, sometimes more than a hundred in a day, so knowing which ones require immediate attention would be a big help.
Our business users have requested for the ability to set the below option as default while creating a new proof in Workfront:Select "Combine all compatible files into single proof" as true by default.Majority of the users upload multiple files, it would be good to turn this option as true by default.
It would be great if the new type ahead custom fields also supported other major record types such as projects, tasks, and issues (in addition to users). This would grant the ability to effectively create a clickable link from record to another thus enhancing the user experience. Also, this would help simplify the creation of Fusion FLOs that automate conditional data propagation from one object to another.
After connecting LinkedIn Lead Generation forms in LaunchPoint you will start seeing Lead Gen form fills in your Marketo instance. There is information when you double click on the "Filled out LinkedIn Lead Gen Form" activity in the activity log, that shows which Linkedin Campaign, the name of the form, etc drove the form fill. These should be available as tokens!
Currently, when a user is created you can send an invitation. This is OK, but doesn't give enough information for most new users. It would be great to be able to create a custom email in the EMAIL NOTIFICATIONS area that could be used there. This could provide information such as training links (internal as well as WF), who/how to contact for support, and single sign-on information that may be needed (adding WF to OKTA, for example). This would be a huge time save. Many admins need to send a separate email currently with all that info.
Description - Can we have the capability to sort drop-down segment lists from A-ZWhy is this feature important to you - Due to the size of stakeholders we serve. We can end up with very long segment drop down lists. It can make for a confusing user experience to go through a list which is not sorted A-Z. Not all users will know what they are exactly 'searching' for in the list. Sorting A-Z would solve both issuesHow would you like the feature to work - Similar to excel, just an icon that appears in the drop down header which allows you to sort A-ZCurrent Behaviour - Currently the segments are ranked in the order that they are added to the drop down menu
Please create a section in the Proof where you can type a description. The only option currently is to put that in the email message of the proof, however, we do not utilize the email notification/custom message. It would be nice if there was a description field that was attached to the proof that anyone on the proof could see when they open it.
Create a tool that is associated with the Type tool that shows you the character count for highlighted test.
I have created a fairly detailed custom form for our Digital Updates team. As he form has many fields to complete, some containing a lot of copy, requesters sometimes do not have time to fully complete the form. If a requester has to leave a 'semi-complete' form, they are forced to try and keep that window open and/or lose everything they started and tart again.
The way the currency field is displayed in a custom form is causing confusion. See example below. We have a drop-down field to select the currency, and CAD is selected here. Then, we are asking the user to enter price, but this currency field is displaying "USD" by default. This is causing confusion and frustration. It shouldn't show "USD". It should show nothing or "$" to make it generic. I hope this can be a quick fix rather than waiting for the required amount of votes to implement it.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
