Build better products with our product team
Next to the request of having a WYSIWG Description in the Task, one of our main pain points is, that we cannot setup Parent & Child projects. Already in 2017 someone has brought that up (https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/parent-child-projects/idi-p/520427) but nothing happened although the idea had over 500 likes. Let me shortly describe why this would be so important. We have several customers that work with a year-to-year development budget. Means it is too much for only having one project in Workfront. But it is also no solution to have several projects with no connection as we need the summary of hours, budgets etc. and additionally to that a Gantt that shows all relevant tasks of the different projects. Thinking one step further, this Gantt should then also be able to be shared with the customer. I am really curious if something like that is on the roadmap otherwise I am confronted with 20 project managers who all look for additional software in order to map this. And at the end of the day, it becomes inevitable to ask the question about the right overall solution.
Request for Feature Enhancement (RFE) Summary: We observed that the ON/OFF Time OOTB- feature is not getting horned on dynamic media-enabled assets. Use-case: Current/Experienced Behavior: Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.12 AMS Customer-name/Organization name: Intel Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: OTB Workflow triggering Email service as assets are pushed from Brand Portal to AEM are incorrect. Use-case: The default workflow when pushing assets from Brand Portal to AEM has the following status - 1. The contribution folder asset-sourcing-test is queued for publish to AEM.2. The contribution folder asset-sourcing-test is successfully published to AEM.The 2nd mail comes even if the Asset Contribution Status in Brand Portal is marked as "Failed" in Status. This is incorrect as it gives user the perception that the push from Brand Portal to AEM is successful. Current/Experienced Behavior: Current mail states " The contribution folder asset-sourcing-test is successfully published to AEM." Improved/Expected Behavior: The mail should state that " The contribution folder asset-sourcing-test failed in publishing to AEM. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS - 2023.11.14227.20231108T162349Z Customer-name/Organization name: TA Digital Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: There was an update a while back which changed the functionality of content sets copy tool to continue and succeed even if there is an issue with a given path. This is not an ideal change as we rely on Content Copy statuses to do certain things like notify our users when a path fails and we are now receiving false positives. We would like the option to return the functionality to how it was before which is to give a status of fail and cancel the copy if there is an issue with the path or the path does not exist Use-case: Routine Content Copy Current/Experienced Behavior: Copy succeeds even if path does not exist Improved/Expected Behavior: Copy should fail if path does not exist or issue with a given path Environment Details (AEM version/service pack, any other specifics if applicable): AEMCS Customer-name/Organization name: Chipotle Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Be able to bulk edit smart cropping of images Current/Experienced Behavior: Users need to select each image one by one and then enter the smart crop editor to adjust. Doing this for 100 images one after the other is time-consuming. Improved/Expected Behavior: User selects 50 assets in bulk --> Smart crop --> Adjust the smart cropping on all assets --> Save All Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets Cloud service (latest version) Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Case Insensitive Asset Upload in AEM Use-case: Currently, if we upload assets - abc.pdf and ABC.PDF - They are treated as different assets in AEM (Your local machine's storage parses it in case insensitive manner)The JCR stores the nodes abc.pdf and ABC.PDF as 2 distinct nodes. Most storage systems even in different OS (Mac | Windows) store files by default in case insensitive manner. Current/Experienced Behavior: The assets are treated as different due to their case difference. Improved/Expected Behavior: The assets should be treated as similar and versioning popup should be displayed. Environment Details (AEM version/service pack, any other specifics if applicable): 2023.11.14227.20231108T162349Z Customer-name/Organization name: TA Digital Screenshot (if applicable): N.A Code package (if applicable): N.A
Description - Updates Section in the Project and Task Level to have option to Add Table in Rows and Column wiseWhy is this feature important to you - We receive lot of data in tabular from from Internal teams on email and while we want to share that with someone through Workfront , we have to convert that table into image and upload in document , which is double taskHow would you like the feature to work - we will copy the table with data from email and paste it in the update sections Current Behaviour - We are making screenshot of table cells from email and adding it in document section , which is creating multiple images and not acting as a chain Description - Program name to appear at "Issue" FormWhy is this feature important to you - We have a form created at Issue level , there is a field called Program name and we want that field to auto populate with the program that project associated with currently Program name can be only pulled at project level by adding custom form and not at issue level , at the backend we tried with adding the formula , but the object it was taking is only Project How would you like the feature to work - Program name to auto populate at Issue form Current Behaviour -
Description - It would be absolutely great to have a possibility to trigger Adobe Fusion directly from within Workfront. Why is this feature important to you - This would give Fusion users more flexibility on how to start a scenario and provide the end user to run custom actions on tasks, projects, documents, ... How would you like the feature to work - As most objects have the "three-dots"-button to initiate misc. operations like edit, convert, move, share, ..., it would be nice to setup an additional entry here, which just calls a specific webhook in Fusion passing the ID of the object to start a scenario in Fusion on this object id.Another approach could be, to have a button as new field type for custom forms, which can call such a webhook. Current Behaviour - Currently a scenario can include a "watcher" module to monitor field changes which trigger a scenario. This uses the Event Subscription API.
I would like to know how to configure the debugger so that when inspecting event objects, I do not need to manually expand the payload.How do I do that?
Description - To use the request queue as a serious alternative for a helpdesk system, it would be helpful to be able to define, which user group can see a queue topic / topic group Why is this feature important to you - This would allow us to create a request queue as our IT helpdesk system with the ability to control, who can send requests like hardware orders, or send on and offboarding request for user accounts How would you like the feature to work - The ability to decide for each queue topic / topic group, if it is visible for all users who have access to the request queue, or only for specific groups Current Behaviour - As far as I understand currently it would be necessary to create several request queues, which leads to the fact, that the first dropdown can get confusing very fast
Description -I am working on internal sites that are built for our organization. All these internal sites are being tracked using Adobe Analytics under same Account name but have different report suites. Therefore, we have mutliple report suites under one Account. I want manage users for each of the report suites using APIs as I can then automate/schedule the managing user list. As of now I have to go to individual report suites and manage the users or go to indivisual users and manage their permissions. Why is this feature important to you -This will help me in automating and adding or deleting users from the whitelist created for each of the report suites under singly account. How would you like the feature to work -I should be able to write a python script that will pull list of users with their permission from a CSV or tab delimited and add to the desired report suite. Current Behaviour -Right now we use Admin console and not APIs. Managing users happen at group level, account level but not at report suite level.
Description - Workfront's API does not use the default standard for OAuth2 Authorization Code Flow. Using out-of-the-box tools available in Integration Platforms or Microsoft Power Platform or other web frameworks is not possible because these solutions expect OAuth2 Authorization Code Flow to use access_token as a Bearer token returned via the and not as sessionID.Why is this feature important to you - There is an increase in development cost and maintenance when creating or connecting third-party apps to Workfront via the Workfront API because of the non-standard OAuth implementation. Limits or even prevents our ability to continue orchestrating and automating work by placing Workfront at the center of our operations.How would you like the feature to work - Ultimately, we would like to be able to use the access_token as part of the Authorization Header as a Bearer token described in the OAuth and standards documentation. This would mean that the token_type be set to Bearer (default, industry standard) and not sessionID (custom Workfront, non-standard) and for subsequent API calls to handle this appropriately.OAuth 2.0 Bearer Token UsageRFC 6750 - The OAuth 2.0 Authorization Framework: Bearer Token Usage (ietf.org)Current Behaviour - Workfront’s OAuth API implementation is non-standard, in that once you’ve gone through the usual Authorization Code Flow, the access_token needs to go in the Request Header “sessionID” in each API call. This non-standard approach makes it very difficult and sometimes impossible to integrate with other third-party and custom built applications unless significant time is invested into workaround. In other cases we are left to use a fixed API Key, which isn’t ideal from a security perspective.
Description -While conducting our first real-life implementation case for data collection via the AEP Web SDK and the Edge Network, we wanted to rely on the out-of-the-box customer consent preferences:https://experienceleague.adobe.com/docs/experience-platform/edge/consent/supporting-consent.html?lang=en However, while experimenting with the different options available, we were facing major limitations with regards to the flexibility of handling the consent - in particular with the current consent object: consent: [{ standard: "Adobe", version: "2.0", value: { collect: { val: "y" }, metadata: { time: "2021-03-17T15:48:42-07:00" } } }] Mainly, I'm referring to these two limitations stated in the official documentation:#1 No granular consent handling:"Currently, the SDK supports only a single all or nothing purpose." #2 No overwriting of the collected consent:"After a user has opted out, the SDK will not allow you to set the users collect consent to y." Why is this feature important to you -RE#1: Modern consent management solutions such as OneTrust offer great flexibility and granularity for the user to decide which type of cookies and tracking solutions he/she is opting-in or not (e.g., first- vs. third-party). However, this can't be reflected with the current AEP consent object as it only takes binary inputs. This can result in fewer opt-in rates and/or data coverage because few users decide to go "all-in" and respectively the consent object has to be set to "n" which prevents any tracking to happen. Since data is key to the measurement of all kinds of marketing activities, the amount of data points captured is key, less coverage means less meaningful insights which ultimately can make client-side tracking solutions redundant. RE#2: As the user can opt-out this value of "n" will be irreversible written onto the AMCV, meaning in reality, for this particular user we will never ever be able to track any kind of data (unless they empty the browser's cache, switch devices etc.). This is even more severe as it drastically limits the potentially tracked users and can even have a disastrous impact when for instance, the value has been set to "n" by mistake. How would you like the feature to work -RE#1: Instead of just offering "y" or "n", give the flexibility to set different tracking categories within the consent object which correspond to different cookies/technologies (e.g., functional, first-party, third-party): consent: [{ standard: "Adobe", version: "2.0", value: { collect: { functional: "y", tracking: "y", marketing: "y" }, metadata: { time: "2021-03-17T15:48:42-07:00" } } }] RE #2: Just add the capability to either reset and/or update the value that has been previously submitted as the consent object would tremendously help in overcoming the initially described limitation. Current Behaviour -As explained above.
Description - The new "Boards" column in reporting displays a "Show" button that must be clicked to show the data. Why I gotta click Show? Seriously, if a have a list of 200 tasks, why do I have to click "Show" 200 times? I'm curious about the thought process regarding this "feature".Why is this feature important to you - I don't want to have to click show over and over to find what I'm looking for.How would you like the feature to work? - Just show the data!!Current Behaviour - User must click "Show" to see the data.
Description - wouldn't it be great to have workfront actively inform you if a resource is over allocated at the task level? Why is this feature important to you - resource leveling works great, but is on a seprate screen, and when using shared resources the resource's hours changes as other PM's book projects. it would be great to see at the task level that a resource assigned to that task is over allocated so you can adjust on the fly. How would you like the feature to work - at the task level, pull in the current user(s) hours for the duration of the task's assigned to them with the same behavior as resource manager, highlighting that a user is over or under allocated. Current Behavior - Currently there is no way to know a user is over allocated unless you actively check the resource manager. if a task is late there is no telling how that task pushed is going to effect the resources timeline without actively going to another window to check.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK