Product Communities

when importing a list I want an option where I am able to only import new contacts without updating the existing contacts in the database. The current default setup and "skip new people and updates" doesn't let you only import new. I should be able to control whether I want to import new only, update existing only or both.

In Classic I was able to print a dashboard to PDF using native browser printing. In the new experience, it only prints the first page. This is the most fundamental usage of Workfront for me. I cannot migrate to the new experience until this capability exists in some form.

Today when a user makes an update, it only displays a time date stamp after a few days. This means that at times, it is ambiguous when the update was posted. For example. I made an update on a ticket on Wednesday January 26th and on Friday January 28th the details for the update just say "Last Wednesday at 1:38 PM". Some people may interpret this as the Wednesday of the previous week which leads to confusion. The Date should always be displayed whether that is in place of the "last day" type nomenclature or in addition to it.

Group admins have the ability to add manage access for themselves for projects created by their users on templates. This allows the group admins to have control over the projects their groups create which is especially helpful when users change jobs or leave the organization (allows them to change the status on projects,). For projects their users create from scratch there is no way for them to have manage access unless the user grants it for them every time or if a system admin grants it after the fact. A project preference or permission on the access level to allow for group admins to have manage access to projects created from scratch would be helpful in giving our group admins full autonomy/control over their own group.

We would like the ability to have alloted/assigned hours (even better, hours remaining) specific to that user display in the timesheet, per task.This would provide a visual indicator/reminder that if they are over-hours there needs to be a discussion.The fact that users are allowed to enter time over their assigned hoursis bad enough, this might help mitigate the issue somewhat.

Functionality to be able to bulk edit scheduled project and report dates would be a useful tool. Currently we're communicating over 500 reports monthly so the ability to bulk edit dates, rather than manually updates these at the end of the 12 month expiry would be valuable.

Description -Within the Report Suite Manager, we're given an option to add a Description to Traffic Variables, Conversion Variables, and Success Events. These descriptions can help users understand what a variable is tracking.Unlike with s.eVars and s.events, s.props have Entry and Exit versions. For example, if s.prop1 is capturing the URL, users may see Page URL (s.prop1), Entry Page URL (s.prop1), and Exit Page URL (s.prop1) when they are looking at dimensions in Workspace.  Why is this feature important to you -Users can be confused by what "Entry" and "Exit" versions of an s.prop mean. Often, they think that these s.props are set when someone lands on or exits a page, which is not necessarily the case.  Current Behaviour -s.props have a single Description that applies to the standard, Entry, and Exit versions of the dimension. Having a single Description cover all versions of the s.prop can lead to long definitions, which can be hard for a user to read through

Currently in the webhook response mapping, we see an option of selecting the program member custom fields from the field dropdown - but in-practice we encounter an exception (RuntimeException:: 877 -- <PMCF field name> not found, to be precise) when the webhook tries to update the response in the PMCF fields. It would be great to be able to write the webhook response data to the PMCFs as this'll allow us to directly map and store the data for the use-cases involving webhook and PMCF.

Allow users to select multiple team assignments in their Work list to Start. Currently users must select each team assignment one by one.

I would LOVE the ability to assign certain tasks to the "Project Owner" on project templates. This would avoid us having to use our "Project Manager" job role and having to replace with the Project Owner's name for each assignment. I noticed that you can assign Project Owner's to a request approval process so I feel like the functionality should be there! :)

Hi,   I wonder if many people will benefit by having the form fill date added to the export from UI when we try to create a smart list for form fills for a specific form.   Thanks, vineela.

Description:Connect to SFTP source and read a GPG encrypted file to ingest into Adobe Experience Platform Why is this feature important to you:Clients averse to using cloud data storage for PII data force data transmission via SFTP with encrypted data files.  These processes may be legacy applications that are hoard to change.  Data privacy and security policies are hard to change.  This seems like such a basic capability - that is available in Campaign - why not AEP? How would you like the feature to work :UI/API to connect to sourceUI/API to open encrypted file with key pair with option to translate csv to JSONRead the data stream from the opened fileReturn a JSON object with decrypted data Current Behaviour -None.  Feature available in campaign is not available in AEP. Current process would be to decrypt the file on the SFTP server then ingest into AEP, which is not compliant with security policies.

On the New Proof page, it shows the project title, but the New Proof Version screen doesn't show the project title. It would be helpful to the designers if project titles can be displayed consistently throughout the proofing process.

Currently, there is no way to regulate the creation of document folders. If there is a user who has access to edit a document, they can then add document folders.There should be a way to limit the number of folders that users can create as well as which users are allowed to create those document folders.

The component definitions tend to be vague or nonexistent. Here's an example: It would be really helpful if there were brief definitions when you click on the (i) icon and a link to the more extensive definition in the documentation.  It would save countless hours running over the same ground helping users getting to the right dimension or metric.

Just how you can bulk edit shared fields in a task, user, project, etc. report, I want this ability for shared fields within reports in a dashboard, or selected reports within a dashboard that have the same field to edit. A lot of our dashboards have reports that share common filters (like a date range, category ID, etc) and when we need to modify the dashboard, I have to go into each report within the dashboard to change the same thing. It would save me SO MUCH time to be able to do this in bulk in a dashboard.

hello,    I'd like to suggest to add a redirect rule scheduler to the Adobe Marketo Engage roadmap.  I saw several threads around this topic or about a landing page scheduler in the Community.    Alternatively,  it may be interesting to create a redirection rule to a non-Marketo landing page and keep both URLs (like for Marketo landing page in Marketing Activities > Landing Page > URL settings), so that whenever the Marketo landing page URL is obsolete (unapproved/unpublished), the other non-Marketo landing page URL automatically takes over.   Kind regards,   Aurélie  

The current newly redesigned Timesheet page top right filter shortcut button only applies to the OOTB filters which is "My Timesheet Approvals" and "My Timesheets".It would be great having ability customize the shortcut button and apply it with our custom filter.

When you attach multiple templates to a project allow users to change the template listed under project association in project overview. Currently, it defaults to the first template attached to a project and this can be confusing when creating a report based on the project template.

It would be helpful to have a "No End Date" option when setting recurring tasks like Outlook. Currently, there's a 100 occurrence max, so I have to create a task in Outlook to remind me to recreate it in Workfront after the 100. (Updated 06.22.203)Aside from the "No End Date" feature, it would be beneficial to add an option that prevents the creation of recurring tasks until the current one is complete. For example, having the August 2023 Update task not be generated until the July 2023 Update task is finished would help keep the Work List uncluttered. It would be helpful to have a visual indication, such as a tick mark in the corner of the task name, to show that a task recurs. It would be beneficial to include Year as a selectable option. At present, only Day, Working Day, Week, and Month are available choices. Thanks!

"Metrics view on Programs" - Enhancing program view. How about having a dynamic "Program Metrics" like the one we have for "Project Metrics". This view would be helpful, as program owners get full visibility without having a chart dashboard built, which would not be as dynamic as project metrics view. thank you.

Starting a new thread since the previous one here fizzled out.Fellow Adobe users and adobe product team.  Here is a suggestion that stemmed from an embarrassing situation that cropped up today!   For context - we have broad Adobe instrumentation in at Chegg - however we are still in the process of driving adoption of Analysis Workspace - since for so many things it is a really quick tool and avoid the need for complex data processes and things like Tableau dashboards - which end up being a source of technical debt.  My team have been working hard with business partners to move them over to a new Analysis Workspace report from a legacy Tableau report that runs off legacy web logs.  I cannot understate how the adoption of this report would have been a huge step forward as we try and drive deeper adoption of Adobe in my organization.  So what happened?  Well unfortunately they were tripped up on a very minor detail - that seems like a huge gap in the Ana

Marketo landing pages are often seen by enterprises as one part of a larger web presence, and one that needs to have a unified user experience and interface regardless of where a web property is served.   In order to accommodate this, a common solution is to implement the use of Web Components for their brand. This provides a consistent look and feel across multiple tech platforms, including AEM and Marketo. However, while AEM can support web components, Marketo cannot support the custom element structure needed to work with web components. This results in a major pain point where Web Component-generated templates must be rendered back into flat HTML/CSS/JS—which is not always possible to do.   To use Adobe's own web components system as an example: if someone were to generate a landing page template using the <sp-button> tag, the markup would be stripped to just <sp>. This renders the custom web component elements unusable.   Would it be possible t

In NWE, user can see maximum of 3 rows at any given point of time under Master Job Tracking Report. Please expand the grid vertically to see maximum number of entries / rows similar to Classic UI.

Add explainatory text after the "Filter View Group" dropdown list items to help users know what exactly the Filter, View or Group is doing and differciate the Workfront standard/built-in dropdown list and the 'customized' one. Our users felt that there're too overwhelming selections, but not sure which ones is trustworthy.it would be great If we could have something like in the dropdown list: "Standard - Workfront Built In View, list the most common used fields like xxx, xxx, xxx and xxx.".