Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

rampai
rampaiNew Participant

Content Fragments HTML tags accessibility improvementsInvestigating

Request for Feature Enhancement (RFE) Summary: Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. Use-case: Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. The OOTB content fragment js should have logic to retain <strong> and <em> tags and not replace them with <b> and <i> tags. This is possible in the OOTB RTE component and is an issue only with multi-edit resource type for CF. Current/Experienced Behavior: We are facing an issue with OOTB Content Fragments multiedit resource type wherein all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. This is causing accessibility issues and based on our analysis, we have to override the StyledTextEditor.js file (located at /libs/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.js) to modify this default behavior.  Improved/Expected Behavior: The OOTB content fragment multiedit js should have logic to retain <strong> and <em> tags and not replace them with <b> and <i> tags. This is possible in the OOTB RTE component and is an issue only with multi-edit resource type for CF. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Abbott Screenshot (if applicable):   Code package (if applicable):  

Adilos-Cantuerk
Adilos-CantuerkNew Participant

Brandportal search rail - mimetype pathInvestigating

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): It is possible to go within brandportal into the admin-search-rail and edit the mimetype path for - filetypes.But it is not possible to create mimetypes a mimetype predicate folder that includes only the relevant options.Currently the mimetype within /libs/dam/options/predicates/mimetypes includes so many useless options that it is not useful. Make it possible to create a filetype search that includes only relevant filetypes. Anwendungsfall: Currently the filetype lists the following options: imagesweb -jpg-gif-png-pjpegbitmap-tiff (X)-photoshop-xcf-x-bmp-icon-bmp-ppm-pbm-pnmvector-illustrator-odg-svg-raw-dng-crw-cr2-nrwdocuments-wordpressing-word-ole2-word-ooxml-odt-pdf-html-rtf-text-docxspreadsheets-ods-excelexcel ole2excel ooxmlpresentation-odp-powerpoint-powerpoint-ole2-powerpoint-ooxml-print-indesign-postscript-pdf-quark multimediaaudio-aac-midi-3gpp-mp3-mp4-mpeg-ogg-vorbis-realaudio-wav-wmavideo-dvi-flv-mp4-mpeg-ogg-quicktime-wmv-webm-other-flash-airarchives-tgz-jar-rar-tar-zip Aktuelles/erlebtes Verhalten: User are searching way to long to find the correct option in there and on top there they find many interesting checkboxes that gave them the impression we use quark files, and rtfs but 90% of the options in here do not give them any results. To many irrelevant options are not good and they confuse the users. Verbessertes/erwartetes Verhalten: Make this already existing option field into something that can be used. There are way to many useless options in here. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): Currently AEMaaCS 2023.7.12549.20230704T084019Z Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend):   Code-Paket (sofern zutreffend):  

skyehansen
skyehansenNew Participant

Parity needed on the User Landing Page (please return to prior functionality)New

Description - Prior to Workfront's "New Experience" we had a lot of functionality, flexibility and customizability with a user landing page. (For those of you who are new to Workfront, the user landing page is the page you are taken to when you click on a user name, that currently shows you their updates, org chart, PTO, and a few details about them. The previous incarnation of this page used to show a lot more than this)   This previous functionality was primarily used by team leads as a way to quickly monitor their direct reports, and by admins as a way to quickly take in a user's particulars and footprint in the system. Some of the functionality and areas that was lost in transitioning over to the New Experience include the achievements tab, the ability to see what a user was working on, the ability to put custom tabs (aka sections) on a user object, and the ability to rearrange tabs and specify a hierarchy of what is seen first. Many of these features are what is currently available on other objects such as Projects, Tasks and Issues. We dutifully registered a lot of feedback prior to transition, none of which landed.   Current Behaviour - The user landing page currently is a place we go to in order to check their org chart, or the few fields we put on a custom form to indicate their particulars. However, we're unable to move these tabs in order to have them appear "first" -- so this always costs us a few extra mouseclicks. We're also unable to customize and place more comprehensive dashboards that would give us a better indication of the user's footprint in the system, such as what they are working on or items they own, and must instead rely on creating or editing dashboards to indicate this on a per user basis. (this latter costs us a lot more than a few mouseclicks)    How would you like the feature to work - I would like an exact return to the functionality from what is known as "Workfront Classic". This would include the ability to place a custom dashboard on the user landing page and re-order the sections on the landing page in order to produce a more efficient default view of each user. It also mirrors the functionality in the majority of other objects in Workfront such as Projects, Portfolios, Programs, Tasks and Issues.   Why is this feature important to you - a large part of our admin's work centers around understanding specific elements of a user, that are not currently covered by the user landing page, and must be created/recreated through extensive reporting (the recent post about Blueprint for a departing user is a good example -- 13 reports which we would have to customize with each user's name, vs the ability to add a custom section that would incorporate this on a user object and require no further customization). Similarly, this is something team leads would find useful, either in a similar situation (one of their team members departing) or even just as a regular check of what this team mate is working on, without a need to compose separate reports for each team member, fight through report prompt functionality, or view team members in aggregate. Lastly, there are reasons you provided this functionality for the majority of objects in Workfront, and we want to leverage the benefits around those reasons as well.   Reference link to blueprint: https://experienceleaguecommunities.adobe.com/t5/workfront-discussions/blueprint-released-offboarding-departing-user-dashboard/td-p/604145   -------------------------------- If you liked this idea, please like my other ideas at https://experienceleaguecommunities.adobe.com/t5/user/viewprofilepage/user-id/17528599/contributions/ideas?filter=authored --------------------------------