Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Nilesh_Mali
Nilesh_MaliNew Participant

Enhancement in AEM instance notifications areaInvestigating

Request for Feature Enhancement (RFE) Summary: Additional customisations are needed in the AEM notification section to receive specific notifications via email or display few of them in the notification box. It would also be beneficial to have support for third-party applications like Slack, enabling notifications for particular events. Enhancing the notification system with more options such as 'Acknowledged' or 'Read' statuses could further improve the user experience Use-case: Consider the following scenario: If duplicate asset detection is enabled and an author uploads a duplicate asset, a notification is triggered, indicating that a duplicate asset has been uploaded to the DAM. It might be more effective to send an email exclusively for this notification, or alternatively, to send a message to the designated Slack group. Current/Experienced Behavior: Notifications can either be sent via email for each instance or displayed in the notification area, depending on the chosen configuration. Improved/Expected Behavior: It would be beneficial to offer comprehensive customization options for notifications. This could involve the ability to receive certain notifications via email, integrating with Slack for specific types of notifications, and providing features such as 'acknowledge' and 'read' options. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name:   Screenshot (if applicable): Code package (if applicable):  

Meghan_Powers
Meghan_PowersNew Participant

Data Warehouse - different format option than just CSV filesNew

One suggestion that I would love to make to the Adobe team is - can we ask them to offer other data format options other than just CSV files?    If the file format could be a modern file format like parquet, then that would also make our processing much more efficient.   When we get the Adobe files, the first thing we have to do is pre-process them to format the files, because of the way they are structured.  This slows down the entire process by a lot, and is also expensive.In brief:   The format of the CSV files that are provided are not "splittable" to be able to be processed by a big data tool like Spark or Databricks.  The reason is that there are new-line characters embedded in some of fields, and CSV files have to be processed serially when that is the case.  This is an inherent limitation of the design of the CSV format.   As a result, these huge files, which are multiple GB in size, have to be processed initially using a single machine, instead of leveraging the power of parallel machine design such as Spark.   This limits our ability to quickly process the data. Switching to a format such as parquet, would mean that the data would not only be able to be processed in parallel, but would also mean that it would automatically be compressed, saving on both storage and compute costs to process the files.

JeremyNe
JeremyNeNew Participant

Projects + Boards: child tasks as check list items **should** pull into parent task cards IN task orderNew

Description: We are looking to expand our use of the Boards feature but keep hitting road blocks based on limitations in functionality. We were recently told that parent tasks can be pulled in as cards and child tasks would make up the checklist items on on the subsequent cards. However, we were told that the child tasks often pull in to the check list out of the order they appear on the project even if linked as predecessors. Furthermore, when we asked how/when this would be resolved, we were told that this was not ON the roadmap to address...That doesn't make sense to me or my team.  Why is this feature important to you: Two reasons. Without have child tasks appropriately relating to check list items introduces confusion and risk into what should be a value add feature. In my view it's a blocker to expanding the use of boards and will inhibit my ability to scale this feature more broadly in my organization.  How would you like the feature to work: project is created with a parent task, that has child tasks linked via predecessors. based on template task ID, that parent task pulls into a card (representative of a project) and the subsequent child tasks pull in as check list items that function the same as tasks on a project AND are in the same order they appear in on the project. If subsequent changes are made on the project, they become reflected in the card (acting as a child of the project.).  Current Behaviour: A parent task can get pulled into a card, but the child tasks get pulled in completely out of order. 

bnc-delphine-dusabeNew Participant

Feature request: Adobe Launch should remove the empty or undefined object from the XDM Object before sending the Web SDK HitNew

DescriptionWe just migrated from Adobe Analytics to the Web SDK, we are using the XDM Object Data Element to do the Mapping with the existing Data Elements. To decrease the amount of work required for that migration we found out that the best option was to do the Mapping at the value level for both eVars, pros & events.  Current BehaviourWe noticed that the Web SDK hits were sending empty string and empty object, what Adobe Analytics hits were eliminated by default. We did not have to worry about this before the Web SDK migration. How would you like the feature to workWe would like that the Web SDK just work the same way the Adobe Analytics was working, just discard all the variables that are empty or undefined.Why is this feature important to you Until now we were looking at the data only in Adobe Analytics and the reporting was working fine even without the non-optimized Web SDK hits, but now that we are trying to work with the Adobe Experience Platform, we noticed that all the Web SDK hits are failing because of syntax errors on at least a single field. For example: The message cannot be validated because a required property is missing: #/_experience/analytics/event1to100/event3: required key [value] not found.The current XDM Object structure around events is not ideal, we need to handle them at the "hundred parent level" 😥 Why the structure is not like the eVars & props? If we just had one "events" parent object, we could make sure that we always have at least one event set and set each event on its own without handling a bigger object of 100 events.  The number of fields ingested through the Adobe Experience Platform has a direct impact on our Profile Richness Overage (we already reach out the limit 😑)

martinkastler
martinkastlerNew Participant

Page sharing among websitesInvestigating

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Let authors unlock webpages to be used by authors of another website of the same AEM instance. (aka Page Sharing) Anwendungsfall: We run multiple websites in our AEM instance. Those websites have cooperations going on. One say that they can take over news from each other.   Authors had to copy and paste the news text and create and rebuild a totally separate page for it on their own website.   We did an attempt by telling them to store the news text in content fragments. Content fragments can be embedded by all websites on the instance. That works. However, the content fragements only the text without any components a news page may also contain (quotes, images, videos -etc.). So authors must replicate the components each time anyway. Aktuelles/erlebtes Verhalten: We do content fragment sharing, but authors are unhappy, because of the missing components. Verbessertes/erwartetes Verhalten: Authors of webpages can check a checkbox in the Page Properties to unlock them for Page Sharing. The shared webpages appear all authors as a dedicated tile on the AEM welcoming page. There they click a button named "Create shared page", which creates a live copy - literally like the already available live copy feature. The system shows all the content from the source page, but set the correct template in the background so the look and feel of the target website is applied. The system sets the canonical tag URL to the original webpage. The system "links" the components to the components of the original webpage, so as soon as the original component gets updated, the linked one also gets updated. Authors may "unlink" components to customize them, thereby losing the synchronization. Authors may set Page Properties and then publish the webpage in their own content tree, as usual.      Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): AEM as a Cloud Service Name des Kunden/der Organisation: VERLAG DES OSTERREICHISCHEN GEWERKSCHAFTSBUNDES GMBH Screenshot (sofern zutreffend):   Code-Paket (sofern zutreffend):  

AbisheikMeNew Participant

Enabling CMYK color codes for proofingNew

Description:Enabling CMYK color code for docs uploading in Proofing environment.Why is this feature important to you:We at Disney use Workfront for request and approval process of both digital and physical designs. We recently noticed the difference in colors in the PDF or JPEG uploaded to WorkFront so we created ticket to Adobe experience league. The issue was identified that we use CMYK color code for our proofs whereas Workfront only supports RGB. The common solution provided to this was to embed the RGB color code to the proof, but we cannot to do that in our case. As mentioned, the documents are used for both digital and physical printing purposes and the print media team only accept CMYK color coded designs.How would you like the feature to work:Our request would be to add the color code to Workfront Proof environment and deviate the color differences. As a developer, I know this is a big ask, but this issue stops the utmost necessity of using Workfront in our company with around more than 1000 users.Current Behaviour:Noticeable color variation in proofsAlternate Solutions:We are happy to hear any other solution for this issue.Timeline:Also, we would love to know if this request is being taken into consideration and the timeline for the change if approved.Attachements:We have attached some samples for reference. Case#00381284 Thanks,Abisheik MS,FileMaker and WorkFront Support,Disney Music Groups.

JeremyNe
JeremyNeNew Participant

New Workfront Home: Greater customization and control for system adminsNew

Description - As a system admin, my team and I really like the look of the new home screen. However we have been reluctant to roll it out because we don't have control over which widgets can appear and the filters and views we use in our dashbord reporting don't translate to the widgets. Giving the group admin greater granular control over the home screen and how it appears (through the use of layout templates) would allow us to lean in and scale this for our users.  Why is this feature important to you - As a system admin we need to be able to efficiently support our users. The ability to control what individual users or use cases see allow us to effectively and efficiently target our support. If end users are able to configure their home screen any which way, support becomes very challenging over a large number of users. Consistency of experience is key.  How would you like the feature to work - I would like the new home screen to be a function of the layout template functionality. I would like to be able to control what widgets our different use cases can pull into their home screen and provide default selections, and leverage existing views and filters. This is not currently the case.  Current Behaviour - You get what you get and you don't get up set. Currently, there is no control over what widgets end users have access to, and the majority of filters and views created and shared are not available. There is also no current functionality for the new home at the layout template level. Additionally, the new home is an enterprise instance level feature. It would be helpful to be able to turn this on and off at the group level.