Similar to the team page where we can now use Kanban, can we have a Kanban view for a single persons workload with work requests going into the backlog and then the various statuses running along the top allowing them to drag and drop tasks. Also can we set the % complete for each status so we can get a more accurate reading on progress? Thanks
Managing custom forms and fields is a custom report is no longer possible in NWE as it is in Classic. NWE:Classic:Classic: (clickable link opens form directly)
Support unicode emojis in all user input fields to keep pace with other chat and communication platforms. This support should carry over to report/form exporting.Possibly configure whether these characters could be entered or not based on group settings. (what works for a creative agency may not be appropriate for a more "formal" business, for example).Example:https://unicode.org/emoji/charts/full-emoji-list.html
Description - The ability to create custom index(es) on AEP datasets for better query service performance. Not sure if Azure Data Lake Service accomodates the encoding, but it looks like there could be serious performance gains by defining a ColumnIndex and OffsetIndex, reference.Why is this feature important to you - Many users are interested in using Query Service, but the current UI can't conveniently handle larger requests, and even directly using ODBCs can be time consuming for larger datasets. Though there is native partition elimination and other benefits of using column-oriented storage, it would be extremely useful if clients could define a custom index improving performance. Even if only a single index per dataset, it could be a very helpful feature.How would you like the feature to work - It could be added to the UI of the data set with a simple checkbox/numbering selection for composite indexes with a specific order. Maybe a dialogue pop-up warning of any extra storage-related costs to hosting an index and an etimated time for building the index.Current Behaviour - There is only partition elimination, but no indexing.
Request for Feature Enhancement (RFE) Summary: As a general user, I'd like to be able to set a tagging profile to assets with common tags/consistent tag list rather than adding tags to each individual asset Use-case: User is adding a number of different assets to the same project or folder Current/Experienced Behavior: User has to apply each tag manually Improved/Expected Behavior: A set of tags can be saved and recalled so that all of the tags will be applied at once rather than applying them individually. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Mark Edelstein/Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable DRM feature on DAM Shared links Use-case: Sales and engineers have access to assets only from Brand Portal: they share licensed assets, or not licensed assets with external users without any issue (exernal users have to access licenses when downloading licensed assets) Brand manager and marketing people are working daily in the DAM. They prepare the assets, manage their publishing to the Brand Portal They aslo share assets with external users like journalists, vendors or other potential assets consumers These external users do not have access to BP nor DAM cause their need is very limited in time (once or twice a year maybe) Brand Manager are working all day long in the DAM and they never or almost never go onto the Brand Portal (they might not even have an account) They use the Share link feature with these external users to provide them assets collections, assets and/or folders directly. Some categories of assets that they share are under license agreement and external users must not use the assets without confirming they accepted the licence agreement text. This missing feature forces power dam user to have a Brand Portal access, switch between two platforms depending on certain tasks they have to do daily which is clearly not efficient nor productive. Current/Experienced Behavior: Current issue (bug or missing feature) is that license feature (DRM - https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/drm.html?lang=en#downloading-drm-assets) works perfectly when downloading assets directly from the DAM and the Brand Portal and also from a Share link created from Brand Portal. Improved/Expected Behavior: We expect the Share link feature from DAM would benefit from the same license/DRM feature as the Brand Portal Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
It would be great to customize the statuses for Risks/Issues/Scope Changes.
I connected to support to make sure we dont have this ability yet. hence an idea here. Scenario: I have a department that manages multiple groups. I have a main GROUP created for my department, where I can pull all my projects and tasks reports for quick review. But, I am unable to view those for my subgroups. Please note--I can add this field at project custom form to add into report. But, I would recommend to have this field (taxonomy) added under Project Setting section, where we add our portfolio, programs, Project managers, sponsors etc. I am system admin, and i dont see this option to add by myself.
I want a better experience when locking a document (reportability, notifications, reminders, configuration around allowed actions re: documents)
We have several users who assign document approval tasks to individual approvers, approvers who often aren't familiar with Workfront. When those approvers are notified via email that a document requires their approval the notification link will take them to the task they are assigned, but when the document lives at the project level those approvers get lost trying to navigate WF and sometimes won't even have access to the higher level project itself.We propose finding a solution that allows approvers assigned to a task to have quick/easy access to project level documents (either through the initial notification itself, or via the task they are assigned) without giving them full access to the rest of the project, and without requiring a complicated click path.Current impact report on this Issue over the past year:23 Groups affected~3,000 users affected~16,000 projects affected266 hours annually of impact (approves clicking around lost, or seeking help/additional access as a result of this issue)
Hello, This feature is/will be important for all type of works and it will make Adobe more powerful in terms of Innovation. Thank You.-Ayush Shah
I am trying to identify contacts that do not belong to a SFDC Campaign who have filled in a certain form. The only option I have is to select if they are 'In' a Campaign or 'Not in' and list all the campaigns they should be in. Both options do not work for me. I need to be able to select 'No in any' as a value from the Person menu or 'Any' from the Campaign menu.
Let's add the Summary view as the default section within a task and issue object.The summary view is customized as part of the Home & Summary activity and compiles background and current information in to one screen. This includes information like the description, relevant documents, updates, and custom fields.Using this as the default when opening an object enables a user to quickly orient themselves to the context and jump into work as opposed to needing to click between multiple tabs after receiving a notice via email, slack, or notification.
Can a number be added to the subtask tab that shows the number of open subtask (basically the way the issues tabs functions)? This would save time to show why parent tasks are open or to quickly differentiate tasks with and without subtasks.
Description: Currently it is possible to change the visitor lifetime profile for new target profiles. However for existing profiles the new visitor lifetime profile length will only be applicable when the initial profile expired. An example: the current lifetime of a target profile is 14 days. We want to shorten this period to 2 days. All new users will automatically have an expiration of 2 days of inactivity. For existing users, it will remain 14 days unless the user is inactive for 14 days, then it will be 2 days.Why is this feature important to you: for companies that rely a lot on returning customers (for example B2B) this mismatch between new users and returning users isn't ideal since different profile scripts will behave differently across different profiles (new and returning).How would you like the feature to work: when the visitor profile length is changed, it would be good to have the option to apply it immediately to all profiles regardless if they existed before or not.Current Behaviour: it only applies to new profiles
With our organisation my team is managing/curating a large number of Workspaces that are shared throughout our business.Over time we are finding we need to make changes/updates to our Workspace projects. We are finding that it is difficult to keep track of:what changes have been madewhen changes were madewhy changes have been madewho made changesIt would be fantastic if Workspace supported some kind of version history for projects which included things such as:an incremental version number, and record of the user amendingan ability to add a comment/notes when saving a new versionan ability to roll back to/view previous versions of a workspace
The updates to version control in the New Experience is causing a lot of confusion and the updates have defeated the purpose of having true version control with one document link to the latest version. This should not be an 'innovation lab' request, but I was told to submit it. The appending of the version number to the URL is not true version control. If the initial uploader passes along the full document URL, it remains that initial first version and that is what anyone else will download, even if a newer version of the document has been uploaded. My team realized this after two major issues happened as we pass doc links along through tasks in comments and if the first version URL is what is being passed along, the next team member or client can be downloading an old version. This is a major problem and again, defeats the purpose of version control. This needs to be updated to be similar to the Classic version where a user could download an older version in the 'Versions' list to get a specific version URL, and it not be appended to the browser URL.
Request for Feature Enhancement (RFE) Summary: Upgrade the Tags (Taxonomy) component with OOTB features that should of been addressed in 6.5. The 6.5 experience greatly reduced my ability to work efficiently. It removed functionality available in Classic UI rather than improve upon the Classic UI functionality and features. Pay attention to the Tags as much as you do to DAM, AI/ML. See current experience for details. Use-case: Taxonomy tag manager Current/Experienced Behavior: Degraded experience for tag management and findability in 6.5 OOTB features. Tag functionality was ignored in 6.5. The Touch UI experience is clunky, requires multiple clicks to do anything, unable to search for tags unless applying page properties. The Touch UI experience removed the ability to view tags in a tree or list, unable to easily scan the list of references applied to a tag, unable to sort, view tag status (published, deactivated, unpublished) modified by whom and when. I work 90% of my time in Tags in AEM. The 6.5 upgrade greatly degraded the functionality and usability of tags. Tags are not alphabetical OOTB, it takes multiple clicks to see the status of a tag (published, deactivated, unpublished), unable to view a clean list of references or export a list of references where tag was applied, unable to view tags in a tree or list, unable to search tags in omnisearch unless in page properties applying tags. I have to manage them in Excel and then upload. I have to conduct a querybuilder to create an export to create custom views of the tags. It's a huge headache and incredibly manual. Improved/Expected Behavior: Why were Tags ignored in the 6.5 upgrade, is there a planned upgrade to bring back the functionality that was available in Classic UI for Tags? Highly suggested: Omnisearch ability within tags - I need to be able to search the tags and only the tags to find duplicates, available options, whether or not something is in the tags within the namespaces. Add Tree and List views, ability to view references and published status, modified date, published date for multiple tags at once, not one at a time! Also create a References List export, not only have i lost the ability to scan the list of references applied to a tag, but i cannot pull the list. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
It would be extremely helpful to be able to make choices able to be hidden per form, so you don't have to make an entirely new field when you want to adapt existing fields to different forms. This would allow us to create fewer fields and reuse the ones we have.
A text mode book would be appreciated. Having a physical book to navigate through and look up pre-written codes, example uses, how to, troubleshooting tips, etc. would be helpful. I learned a lot about text mode and how to use the API Explorer table in the bootcamp classes; However, having a physical book to flip through will improve my experience of trying to learn text mode. I am a sticky note guru, so being able to use sticky notes and highlight text in the book would be helpful. And as updates are made to text mode, a new book could be released yearly including the changes, or a downloadable pdf on Workfront One.
After I shadow a user with the Log In As function, when I click Logout, I almost always need to return to Setup. Dump me there, specifically the Log In As section, rather than Home.
The Home and End keyboard keys do not work properly in the search box in the New Experience. In the classic interface, you can use those keys to move the keyboard cursor inside the search box. In the New Experience, the Home and End keys actually navigate the results preview drop-down list. It is less useful and less intuitive now, because the Home and End keys behave differently in the search box compared to any other field in Workfront.For comparison, try using the search box on the home page of Google. You can use the up/down arrow keys to navigate the results preview drop-down list, but the home/end keys move the keyboard cursor to the front/end of the search text. This is the standard behavior for most applications, and it would improve the user experience in Workfront if it was the same.
It would save SO much time if we were able to bulk edit reports. Sometimes there are instances where I have multiple reports that need to be edited in the same way (i.e. add the same column or filter to 5 different reports or edit the 'view as' access), and currently to make these changes it has to be done individually which can be painstaking when you have to work across a lot of reports that need to change frequently.
The new filtering option that allows you to search and filter within a report has been great, however this option isnt available when viewing reports within a dashboard. Users have to click into the report to use this feature, or if users arent WF pros, they won't even know this feature is available if they only view dashboards that were built for them. Having it available within a dashboard would make it way easier.
Now that Workfront has delivered on exporting custom forms, make this action possible to call from the API. We want to perform this action as part of an automation, but cannot because it can only be performed directly in the web interface, one record at a time.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
