Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

UnjiBaAdobe Employee

Enable Partial Search for Metadata Containing Dot and Hyphen in AEM Assets SearchInvestigating

Request for Feature Enhancement (RFE) Summary: Enhance the AEM Assets Search to support partial and full-text search functionality for metadata properties containing special characters, such as dot (.) and hyphen (-), as part of their values. Use-case: The customer has integrated a custom property (jcr:content/metadata/dc:suffix) into the filter search form and enabled partial search for this property. This property stores metadata values, such as product SKUs, which frequently include dots (.) and hyphens (-) as part of their structure (e.g., OLED48B46LA.AEUQLHX or OLED48B46-LA-AEUQLHX). However, the current search functionality treats these special characters as delimiters, breaking the search query into tokens and failing to retrieve relevant assets. For example, search for OLED48B46-LA.AEU* is not working where property value is OLED48B46-LA.AEUQLHX. This issue significantly impacts the customer’s ability to locate assets efficiently, disrupting workflows that depend on precise and reliable search capabilities. The requested enhancement is critical to ensure accurate partial and full-text search for SKUs and other metadata properties containing dots and hyphens, which are key identifiers for assets in the customer's repository.   Customer Impact:The inability to perform searches with strings containing dots (.) and hyphens (-) limits the customer’s ability to retrieve assets effectively. This impacts search efficiency and accuracy, resulting in significant delays in workflows and operational inefficiencies. Since LG Electronics' SKUs often include these special characters, the current behavior does not meet their requirements, hindering productivity and disrupting processes dependent on seamless asset retrieval. Current/Experienced Behavior: When querying for strings containing a dot (.) or dash (-), the search functionality does not return the expected results. These characters are currently treated as delimiters, splitting the query into separate tokens. This disrupts partial search capabilities. For example, searching for OLED48B46LA.AEUQLHX fails to retrieve the correct asset. This behavior prevents accurate retrieval of assets when metadata properties, such as SKUs, include dots and dashes, which are commonly used in their structure. Improved/Expected Behavior: Dot (.) and hyphen (-) should not be treated as delimiters during indexing or querying. Metadata values containing these characters should be indexed as a single token to fully support partial and full-text searches. Users should be able to retrieve assets by searching for SKUs or other metadata values containing dots and dashes without any issues. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud (2024.8.17569.20240822T203847Z)) Customer-name/Organization name: LG Electronics Screenshot (if applicable):   Code package (if applicable):  

lutzULevel 4

Translation Project | Maintain user by the one who creates the projectInvestigating

Request for Feature Enhancement (RFE) Summary: Please improve the way how a creator of an translation project can add users to the project. Currently only an administrator can do that which is NOT feasible at all under real live scenarios. There this option is currently totally USELESS! The creator should be able to add users and there roles by himself. Use-case: As an editor which has the task to create translation projects, I need to be able to add other users to the translation project so that they can see and maintain it WITHOUT the help of an administrator. Current/Experienced Behavior: As a member of the 'project-administrators' can only add myself and the anonymous user to the project. I got the confirmation from Adobe Support that this by design and only members of the administrators group can see all users in the dropdown. With this the option to add users to the project with different rules is USELESS under normal circumstances! Normal users can not turn to administrators groups and ask for adding users each time a new project is created. And, also normal user can not be in the administrators group. Improved/Expected Behavior: The editor who creates the translation project should be able to add other users or at least user groups to the project. This is essential in an enterprise environment where you have a lot of people starting translations and need to see which projects are running. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

Hemang35
Hemang35Level 5

Product Idea: Adobe Analytics AI AssistantNew

Introduce an AI-powered virtual assistant within Adobe Analytics to help users navigate the platform, create segments, set up reports, and analyze data more efficiently. The AI assistant would understand natural language queries, allowing users to ask questions and receive insights or recommendations based on their data.Key Features:Natural language processing: Understand user queries in everyday language, making it easier for users to interact with the platform without needing deep technical knowledge of Adobe Analytics.Personalized recommendations: Provide users with tailored suggestions for segments, reports, and visualizations based on their data and previous activities.Automated data analysis: Perform complex data analysis tasks and provide actionable insights, helping users identify trends, anomalies, and opportunities within their data.Voice or text input: Enable users to interact with the AI assistant through voice or text input, depending on their preference and context.Integration with Adobe Experience Cloud: Seamlessly connect with other Adobe Experience Cloud products, allowing users to leverage insights from the AI assistant across their marketing, advertising, and customer experience efforts.Why is this feature important? The Adobe Analytics AI Assistant would make the platform more accessible and user-friendly, particularly for users who are new to Adobe Analytics or have limited technical expertise. It would also help users save time and improve decision-making by automating data analysis tasks and providing personalized recommendations based on their data.How would the feature work? Users would interact with the AI assistant through a chat interface or voice commands within the Adobe Analytics platform. The AI assistant would process user queries, analyze data, and return insights or recommendations in a conversational manner. Users could also ask the AI assistant to create segments, set up reports, or generate visualizations based on their questions.

Ability to mail in a ProofNew

Description - We would like to be able to mail proofs into workfront, without having to log into the platform. Why is this feature important to you - We work with a lot of freelancers for artwork who are not users on Workfront. Pulling in their work into workfront involves a lot of time and effort that could be saved, instead of switching between apps, and checking in for updates, when all the other work is done in workfront. How would you like the feature to work - Something like ProofHQs now defunct functionality of being able to mail in proofs to a holding area or DropZone. Mailing to a specific person's DropZone url should provide the documents ready to be allocated to the right project in workfront. Each artwork manager can have their own separate DropZone, or even a central DropZone for the company with access restricted. The specific url for this landing page should be able to be emailed with the documents as an attachment in the email. The proof owner is the person who's DropZone is the target landing, and they can decide what to do with this proof within workfront. Current Behaviour - Once the job is completed, the process now involves these freelancers emailing the documents to the respective manager, who then uploads them into workfront. Which is very cumbersome. We are open to other alternatives, and haven't used the emailing feature in ProofHQ either, so any similar ideas that help bring in external work into workfront would be appreaciated.