Product Communities

I recently had the experience of a guest user gaining unauthorized access to my account when I inadvertently forwarded an internal proof notification. Support explained the following: "From what you are saying it sounds like those users are getting your routing link through a forwarded email, and they aren't noticing that it's logging them in as you. The URL attached to those emails is linked to your credentials for that proof, so anyone who follows the link will be entered into the proof as you. There is a setting on each proof to change that behavior by requiring users to log in to the proof, that will prevent people who ended up with your personalized link from making changes as you. This will, however, prevent unlicensed users from accessing the proof. If all of your work is done internally and you don't have to have guest users, and external users access the proof then this would be the best route. If you do need external users to have access then it would be best

Currently, the X-Unsubscribe (the unsubscribe text link that many inbox providers display next to the email sender information) is set to use a "mailto" instruction. Often, the unsubscribe option is one of the first pieces of content subscribers will see when opening your message and the "mailto" setting means that, when clicked, an automatically generated email notice is sent to Marketo and the reader is unsubscribed from ALL future content.   I'd like to suggest that the option be given for programming X-Unsubscribe URL instruction. With this method, when the reader clicks the unsubscribe text they'll be taken to a landing page to process the unsubscribe request. Namely, a Marketo landing page like our Preference Center so the reader can choose to be removed from one or more categories. This would help with attrition rates by allowing an option beyond all or nothing.   Many other email service providers already offer this option and I feel stro

Description - Currently, we cannot use h2 and h3 in forms and have them appear on Generated Documents of Record. We have to use panel descriptions for blocks of form inputs, and cannot use in Static Text - they simply do not show and will block out the entire text block. To enable accessible scanning of form, we need to do a workaround of a panel descriptions for the DoR, but then put in the h2 and h3 for the Adaptive Form. Why is this feature important to you - Accessibility! Screenreaders scan by header levelsHow would you like the feature to work - support for <h2> and <h3> codes and other text formatting in static text that will show on DoR so we don't have to generate XDPs for legal static text. Current Behaviour -

Description - While uploading new assets from external system, those assets might contains some metadata properties. While uploading it to AEM, it's auto generating namespace and preserving those metadata. Which we would like to prevent using this feature request if possible, Only registered namespace metadata should preserve.Why is this feature important to you - It's creating issues while doing full text search and also impacting search speed. It certainly improve the system performance.How would you like the feature to work - Post implementation of these restriction that only registered namespace metadata will AEM allow , when we upload any asset from any external system, it will not create unnecessary namespaces automatically into system and also no unknown properties will be part of asset metadata and full text search will work fine.Current Behaviour - Currently if we upload assets from external system , if that assets have any metadata properties, while uploading on AEM , it's cr

Description - Any component that has a link field, edit dialog and click on the path finder. Search using search term or paste in a path in left rail path field to get to search results. Instead of only pages getting non-page "nodes" in the search resultsHow would you like the feature to work - When searched only pages should appear.Current Behaviour - Instead of only pages, showing non page nodes also. Thanks

Description - When a person is given Developer access they can pull and push to the Adobe Git instance for the program. There should be an option to prevent people with the Developer access to push when there is a customer Git repository that syncs to the Adobe GitWhy is this feature important to you - To prevent a customer Git repo becoming out of sync with the Adobe Git repo, there should be an option to not let people in the Developer role from pushing to the Adobe Git repo. How would you like the feature to work - Add an option to the Developer role to prevent pushing to the Adobe Git repo.Current Behaviour -

Description - We would like to create meta tags (not limited to keywords) on pages through page properties. We would also like to have meta keywords (tags currently in page properties) inherit to child pages or be able to set default tags.Why is this feature important to you - This feature would make tag management simpler and more manageable out of the box.How would you like the feature to work - Add tags through page properties in 2 sections, one for keywords and one for miscellaneous with an option to inherit to prepopulate and customize from there.  For example, if a user selects to inherit tags, it would prepopulate with the parent page's mete tags.  The user can then add tags or remove tags from their page as needed.Current Behaviour - Custom page properties and Java needs to be developed for this implementation of tag management

Please can you consider adding hour as as an option in the date range builder? (so it is possible to do "start of current hour" minus 1 "hour" etc.) Every other time period is available (e.g. day, week) so it is rather frustrating that we can't use hour - there are so many great things this would allow us to do! :-) 

I'd like the ability to "bulk delete" Announcements and Notifications from my "View All Announcements" and "View All Notifications" screens.

When uploading a document, you can request a document approval. This is great! But, you can't assign a deadline to the document approval. We have some projects in which we just want a user to approve a document, without assigning them a formal request. Workfront allows this, but without a due date, there's no way to indicate to the user by when their approval is needed. The workaround is to indicate that detail in a directed update, but this results in the user receiving two email notifcations (one soliciting approval, and another with the directed update.) Document approvals should have deadlines just as request approvals do.

On custom forms, is there any way to create rules around an open field? Meaning using Fusion or some other technology, whatever is written in the field must follow a certain format (i.e. AA-1234)? If they don’t follow the format, it won’t push the request forward.

Description - As per current behaviour, as long as the Virtual Report Suite is Data Warehouse compatible, you would be able to run the request. However, if it is not compatible you will still be able to create the request with this VRS, with failed status and no prior warning.There should be a warning or an error message on selection of Virtual reports which are not DWH compatible. Why is this feature important to you - It is quite misleading as there are several VRS and we won't remember which all are DWH compatible and which are not. How would you like the feature to work - The VRS which are not compatible should either do not appear in the DWH interface OR there should be a warning on selection of the VRS. 

We would like all the existing Adobe Analytics dimensions (eVars[1-200], props[1-75], and events[1-1000], list[1-3]) to be automatically mapped using a supported or new schema mixin. In addition, this would be needed for product syntax eVars and events. This is important for existing implementations with a significant number of custom dimensions. It will ensure customers will not have to manually map every single custom dimension via processing rules. In addition, it will allow customers that leverage the raw data feed to use the AEP SDK.  At this time, only specific dimensions are automatically supported.https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/manually-mapping-variables.html?lang=en#context-data This is already supported for standard dimensions like products, commerce, and page details. https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/automatically-mapped-v

In Email Insights and anywhere else applicable, there should be an option to display the date in the International Date Format (ISO) standard format i.e. DD/MM/YY. This is in line with W3 and general usability guidelines. See here: https://www.w3.org/QA/Tips/iso-date    Marketo users only have the option to use the Americanised MM/DD/YY, which is a counter-intuitive format to all users outside of the U.S. and aren't to usability and accessibility standards.   Currently, the Date format showing in Marketo's UI is hard-coded in the software and cannot be changed based on one's region/instance.

As of now ACS provides ability connect to only one report suite on analytics side when you configure the ACS -> Analytics integration. If it's provided to configure more than one report suites, it will help for business using multiple BU's from ACS send data to adobe analytics for further business processes.

Description - Make the Schedule Renewal page use the Analytics page template. Currently, the page design looks like an afterthought.Why is this feature important to you - It allows users to navigate to other parts of Analytics immediately.How would you like the feature to work -E.g. include the top main menu, shortcuts to other parts of Analytics, etc.Current Behaviour - The Schedule Renewal just shows a message to renew the schedule and whether the renewal is successful or not. There are not other calls-to-action. 

As a Sys Admin, we often have to clean up QTs attached to projects/templates. You currently can bulk delete routing rules and queue topics, but there is no bulk delete for Topic Groups. I understand why it was designed that way, but if a) you limit this ability to Sys Admins and b) only allow bulk delete on Topic Groups that have 0 QTs - I think that would be safe! And amazing.

workload balancer: Anyone with a Plan License should be able to see and edit all objects/projects right away, without having first to share each individual project/portfolio with a person/team.

Our team has the desire to send multiple proofs from different projects at a campaign (program) level. To explain further, we understand the ability to send multiple proofs in one workflow is possible, but our teams would benefit from an automatic system to pull proofs from several projects into one workflow for a campaign. The concern is that there isn't a clear way to see all pieces in a campaign in one place and we think something like this would be beneficial.

In Classic you could select the proof details on a document and the now 'proofing workflow' would open in a pop-up window. Now 'Proofing Workflow' takes users to a new page. This has caused confusion and frustration on part of our users. If the proofing workflow opened in a pop up window, or was available in the quick summary it would save us time and effort!

When adding a URL for proofing a website, it would be beneficial if we could specify a background color. There are times that there's transparency on blocks, which results in just showing the dark gray UI from Proof HQ. It would be great if we could specify a color to be used as the background.

Description - "Enhanced Security - just in time user provisioning access to Adobe tools".  When an employee from a customer company connects to Adobe via SSO, Adobe uses the authentication and authorization information from the customer company to create a secured session with just those permissions the user has been granted, user does their work, then at time of user exiting Adobe tools, the secured session is destroyed.  No individual user account information would be stored on Adobe end, only group permission information.  Customer company sends the user's group information in SSO handshake.Why is this feature important to you - Financial Services clients are always needing more and  better user authentication and authorization methods to reduce risk of cyber crime from external sources.  Removing Financial Services employee information from Adobe servers reduces risk exposure.How would you like the feature to work - When an employee from a customer com

We're testing out the Adobe Extension for our Inhouse group and realized that PDF is not included as one of the export options. We use Illustrator for a lot of our artwork - print ads and event deliverables especially so this is definitely an important feature need for us. Please add as an upcoming feature release!! Current list of supported exported file formats here: https://support.workfront.com/hc/en-us/articles/218196847-Using-the-Workfront-Extension-for-Adobe-Creative-Cloud#supported-exported-file-formats

I would like to see the custom form fields have functionality to set character limits for both minimums and maximums. That way if I make a field required, it would not allow submission if they don't enter enough characters or would cut off if they tried to write too many.

It would be great if we were able to allow Project Statuses to be set to open on specific statuses by Groups and not just one option for all projects as set under the main set-up Preferences. For example - some groups projects need to always open as Planning while others need to open as Active.