Product Communities

Using AEM along with Translation project to send pages/assets for translation, We can configure Translation rules to exclude/Include paths with /content/dam/ path allowed. Ex:- My DAM structure is "/content/dam/XYZ/global", "/content/dam/XYZ/us", "/content/dam/XYZ/uk" "/content/dam/XYZ/de" etc.. I have image component which will be used by authors in different sections of the page and browse images from the above paths. Here I want to exclude images from "/content/dam/XYZ/global" but take images from other locales for translation while they submit pages for translation. I have posted similar question earlier to questions section and was asked to submit the "support ticket", hope this is the right place to submit this. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/skip-assets-from-asset-translation-job/qaq-p/377318  

Description - Monthly we run capacity reports based on Planner in attempt to determine if we have enough in-house capacity for Creative job roles. No matter how we filter, we still see projects listed even if a job role isn't associated with the project.Why is this feature important to you - Without the ability to filter out these projects that aren't relevant to the job role, we run into the row limit outrageously fast. Ultimately we're stuck with exporting over a dozen permutations of our filters each time we want to run our capacity planning protocol. I confirmed with Support that there is no good filter to ignore rows of 0s.How would you like the feature to work - Offer a toggle switch to include/exclude rows of 0 data.Current Behaviour - After exporting data to Excel, we have to manually exclude rows of 0 planned hours.

Description - When creating/ updating a custom form, it would be great if it was possible to be able to change a field type (for instance, from a Drop-down field to a Checkbox or Radio Button field). This would be so helpful because you wouldn't have to reenter all the information again and rebuild all the logic/ loig dependencies that might be associated with the fieldWhy is this feature important to you - Time saver, wouldn't have to duplicate work, allow for custom forms/ custom fields to be more easily updated How would you like the feature to work - Ability to change type of custom field to another type without have to reenter data and reset logicCurrent Behavior - Currently, when you change a field type you have to start from scratch and rebuild the entire field and reenter all the logic associated with that custom field

In some instances, work from a timeline task on a project with a default schedule set to exclude weekends shows up in WLB with time assigned to over the weekend.  This causes a discrepancy between the project schedule and the WLB resourcing.  I understand that for some reason this is intentionally set up this way, but there should then at least be a setting in the WLB to exclude scheduling work over the weekend.

Description: Would like to be able to take a card on a board and convert into a project similar to the way we convert a request to a project with a template. It seems like this would have already been a feature.Why is this feature important to you - Create efficiencies and decrease manual processes. How would you like the feature to work - The same way a request gets converted into a project. Current Behavior - If there is a card on a board and it is determined it should be its own project, you have to manually create a project and then close the card. @suzyf @rudyha1 @hollyse @annapu 

In a Workfront Kanban board, the API calls for 50 items to be displayed when the board loads. In order for more items to display, a person needs to select "Show more work items" each time that the page is reloaded. I would like the API to call for a higher number of items (potentially 100) each time the board loads. This will help team members using the board from needing to click "Show more items" each time the board loads.

Ability to Change primary assignments on objects

Description - Provide an ability to move issues to ProjectsWhy is this feature important to you - It provides an adiditonal way to keep work movingHow would you like the feature to work - Exact same functionality available on webCurrent Behaviour - Functionality not available

Integrate Planned Hours and Actual Hours fields with the task/issue percentage complete bar and iteration burn down chart.  This is important because it would show meaningful data metrics as opposed to hypothetical, relative, manually-set percentages complete. When the Planned Hours and Actual Hours fields are added to the task and issue cards, as the task and issue owners update the actual hours spent, the percentage complete bar is automatically updated based on the initial Planned Hours. Optimally, there would be 3 standard Agile task and issue fields to accurately show the effort against the work and to capacity plan:Planned HoursActual Hours SpentHours Remaining The current behavior relies on the task or issue owner to calculate the percentage complete based on what they think or feel.

Hi, it would be great if we could pull a similar report as the Email Link Click report, but for landing pages. so we could see the # of clicks on each link on our landing pages. We can currently pull one-by-one using smartlists, but it only shows the people we have in our Marketo system, not the gross # of clicks like we could see in an Email Link Click report.   

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): The expired assets predicate in the search filter currently only has one feature. Asset is already expired.Yet there are much more interesting things related to the expiry, that could be shown.Here are some examples for more interesting search filter regarding the expiry: Expired: The asset itself is expired(Ignore Dependencies) Has expired dependencies: The asset contains expired assets (Don't show expired assets, but instead those assets that contain an expired asset) Will expire: The asset will expire till (dateselect)+ usefull quickoptions: within the next 1 week, 1 month, 1year etc.)Be careful using those on sites / print projects that will be used for a longer period of time, since the printed media can't be "unpublished" but have to be destroyed, removed etc.) Will not expire: Show only assets that are free of an expiry restrictionI call it the "care free" option. Assetts can be used without having any f

Request for Feature Enhancement (RFE) Summary: Support for multiple SMTP configurations Use-case: Many client work in multi-tenant set-up. Very often they need different SMTP configurations to send emails. Current/Experienced Behavior: Only one SMTP server can be configured by Day CQ mail service Improved/Expected Behavior: A factory configuration is available for SMTP configs. One can pick one dynamically and send emails Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Brillio Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Use-case: Developers needs the replication behavior similar to that of a server for validating caching use cases. Current/Experienced Behavior: An (enabled) Dispatcher flush agent is not trigger on receive events. Thus, .stat files are not touched and the caching behavior cannot be mimicked for entire flow Improved/Expected Behavior: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Environment Details (AEM version/service pack, any other specifics if applicable): AaaCS local SDK Customer-name/Organization name: Brillio Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Extend Core components to display content from a linked CF Use-case: Many clients want to reuse content across multiple channels. Often recommendation is to use content fragments for authoring. However, being form-based, it cannot readily be used on a website. It would be good if we could extend core components such that they can display content from a linked CF Current/Experienced Behavior: CF being form-based cannot readily be used on web-pages  Improved/Expected Behavior: Components should be able to pull content from a linked CF to display Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.x & AaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Rollback feature for Production Deployment Use-case: Feature request for Cloud manager, where a process in place where we click on one button and confirm to roll back the code which was deployed to production. Current/Experienced Behavior: No efficient process to rollback in AEM production environment  Improved/Expected Behavior: Functionality that allows AEM users to roll back to a previous version in production environments Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Providing advance notifications and implementing a code validation pipeline for upcoming CM rule updates would be highly beneficial, as it can help mitigate unexpected pipeline failures, such as the one mentioned in the provided link. Use-case: Failed pipelines due to sudden CM rule updates Current/Experienced Behavior: Pipelines suddenly start failing if they don't comply to CM rules Improved/Expected Behavior: A prior notification and separate pipeline to validate code against upcoming updates Environment Details (AEM version/service pack, any other specifics if applicable): AEM instances using Cloud manager Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Should have leverage to provide required permissions like (Read, Modify and Delete) from touch UI for Experience fragments folder. Use-case:   Current/Experienced Behavior: In order to get inherit Edit permission Adode team has suggest to provide jcr:all permissions for the Experience fragment folder. Improved/Expected Behavior: We need to leverage in such a way that we can provide required permissions like (Read, Modify and Delete) from touch UI.   Environment Details (AEM version/service pack, any other specifics if applicable): Version : Adobe Experience Manager (6.5.14.0) Customer-name/Organization name: American Express.  Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Extend Adobe Sensei capabilities in AEM Sites to extend capabilties of content creation and smart tagging Use-case: 1. Auto/smart tag webpages 2. Add description/title (for SEO) 3. Content curation Current/Experienced Behavior: Currently only content summary for CF using Sensei is supported Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Description - With the new functionality for "Enable faster Workfront release cycles," it would be ideal to have the ability to opt into the fast release in lower environment(s), but keep the quarterly release in your Production environment.Why is this feature important to you - For new feature testing purposes, to offer feedback to Workfront, and more time for planning of communications to end users.How would you like the feature to work - Similar to how it works for Production; if the checkbox for the "Enable fast release process" is checked, in a lower environment then it should allow for the install of the new release functionality to be installed during the next release in that respective lower environment. If not checked, then the quarterly cadence of release would follow.Current Behaviour - There is no way to opt in to the fast release cycle in SB01 or SB02, but keep the Production environment in the Quarterly Release cycle.

アンケート回答や問い合わせ内容を格納する際にPMCFをフォームで使用する機会は皆様多いかと思います。 便利なPMCFですが、プログラムのメンバタブでしか確認できません。 Marketoにはスマートリストの定期配信という素敵な機能があります。しかしPMCFはスマートリストの表示項目として選べません。 問い合わせ内容を関係者に定期配信で連絡できれば、省力化にもなりリードへのフォロー漏れを防止できます。   Marketoの仕様としてすぐに実現は難しいかもしれませんが、 将来のアップデートでこの機能がサポートされることを強く希望します。

The Campaign Queue can be an important indicator of system health.  Since excessive volume in the queue can be an indicator of critical issues such as long delays in Syncing or processes completing out of the expected order, timely awareness is important.  However, it is not always convenient or possible to view/refresh the Campaign Queue at all times of the day. It would be great if there were Notifications for the Campaign Queue for excessive volume or delays. This could be the number of campaigns, number of leads in a campaign or total number of leads currently backlogged. To deal with the different needs and activity levels of various clients, the notifiction could be based on user set thresholds.In general, it's always a good idea to keep an eye on the Campaign Queue when testing and activating new campaigns.  However, sometimes an excessive backlog can develop due to things out of your control and knowledge. An automated alert would be good for those cases.We recently had an expe

Often we need to import a series of different lists, we would like a view with the following to the lead database.1. List of all imports with the name of the file, date and time, and results (leads updated and new leads).2. For in process imports, a status (i.e. in process, importing, completed).Some imports don't work, so it would be ideal to get a status message back on what is the cause (i.e field format, etc).

At the moment it is only possible to manage Person records in the Marketo UI and to some degree also Company records. That means that anything else needs to be handled via CRM or the (especially with custom integrations) via the API. I am fully onboard with not allowing any marketing user to freely make any more changes to the database. There is however a use case for managing some data via the Admin screen of the UI, so the need for development resources becomes less. Some topics where this would be interesting: Deleting Company records that are orphaned (no contacts, opportunities, custom objects associated anymore). Deleting Opportunity records that are orphaned (no opportunity role or company links anymore). Deleting historical data in Custom Objects. Any other use cases you can see?

When building a template it would be nice if there was a way to lock/unlock mktoList values. Our templates are coded so our marketers have all the tools needed to build an email or landing page, stay on brand and not need to know code.  A great feature we use to do this is mktoList values. We enter values so they have a set list to choose from. Recently we discovered that even with a set list, someone can still change the value using the input field. For example, adding something like the image size lock to the mktoList would be a nice option as it would help avoid possible human error or a missed QA and could be turned on or off.Something like: mktoLockList="true/false"

Currently, when multiple records are merged, the most recent date of the New Person activity is presented as the Created date for the newly merged record. This gives an inaccuarte "age" for the record, and implies that the email address has not existed within Marketo as long as it has. The shared history of the merged record can be seen - with both New Person activities - but should not the Created match the date the email was originally created in the database?  The issue can best be seen when pulling a SmartList based on the "Person was created" filter and either the "On or before"/"On or after" conditions. Sort the Created column, and notice values outside the given condition.