Product Communities

Description - Enable / Disable Event Notifications on Subgroups Why is this feature important to you - This will help group admins to customize Event Notifications for all groups they manage, not just the top-level groups. How would you like the feature to work - When the Email Notification is unlocked at the Setup level, the Subgroup level Event Notification would be unlocked as it functions for top-level groups. Current Behaviour - The Event Notification remains locked for subgroups.  

Description - Log actual hours on an editable column view from the project level.Why is this feature important to you - Users could make all edits to a task and log time from the project level view all at once.How would you like the feature to work - Log time for "Actual Hours" column in project view.Current Behaviour - N/A

Description - First post so please forgive me if this has already been addressed! My thought is that Workfront could benefit UX functionality to take already existing documents/proofs (separately attached in a project or different project) and combine them into one document record.Why is this feature important to you - Numerous times I see users upload multiple versions of a document that contain their own proof and accompanying edits. The ability to seamlessly combine these files into one document record will help cross-comparing proofs and provide one single reference point for auditing purposes. 

Description - On the homepage, the widget names are hard-coded, but different things mean different things to different people. From organization to organization, from role to role, and from functionality. It would be great to be able to customize it and enhance the user experience.Why is this feature important to you - This creates a higher adoptability as the user will be able to understand the views as it relates to their job role and function, My Work, for example, could be priorities. How would you like the feature to work - To be able to customize the naming widget to whatever the user wants to name it, but the ability in settings to be able to see what the original Widget applied (for troubleshooting).Current Behaviour - The name of the widget is hard coded to what has been established by Workfront which doesn't translate as well for all users. We need the ability to customize.

Description:We recently faced an issue with the request conversion to template. After conversion, the relationship was removed either as human error mistakenly or on own. The same was fixed by restoring the relationship. We were wondering if there were any log system to keep notice of changes made in the details section of the project or task. This issue has been repeated twice the last week.Why is this feature important to you:This will prevent accidental changes to requests and projects as well.How would you like the feature to work:Either the changes made by person's name to be shown in the current system activity or separate log for the same.Current Behaviour: There is audit log and system activities for changes. But it does not work on the details section.

Description - OAuth authentication to Adobe Experience Cloud applicationsWhy is this feature important to you - Use OAuth to connect to AEC applications. A JWT private key has an expiration date and needs to be refreshed.How would you like the feature to work - A connection within Workfront to an AEC product (AJO/Target) should us OAuth instead of a private key.  OAuth does not use a private key to exchange for a bearer tokenCurrent Behaviour - To obtain a bearer token a private key is required.

Description: Presently, the Data Science services section only accommodates Customer AI, primarily utilized for generating propensity scores for diverse profiles. However, it falls short in empowering customers to deploy their personalized machine learning models. This limitation necessitates a reliance on alternative tools, hindering the full utilization of data resources.Why is this feature important to you: The integration of this feature is crucial as it opens avenues for deriving tailored insights from data, aligning precisely with the unique requirements of each customer. The absence of the ability to deploy individual machine learning models constrains the potential utility of the available data, impeding the generation of valuable, customer-specific insights.How would you like the feature to work: We propose the enhancement of the RT-CDP (Real-Time Customer Data Platform) by incorporating the capability for users to deploy their personalized machine learning models within the D

Request for Feature Enhancement (RFE) Summary: Cache ContentPolicy lookup in WCMBindingsValuesProvider Use-case: Currently the implementation of WCMBindingsValuesProvider performs a lookup of the policies, but does not store the result. This leads to unnecessary load as this is executed again for every script execution. Current/Experienced Behavior: Lookup is not cached Improved/Expected Behavior: Cache the lookup (same as it is done for Designs) Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18 Customer-name/Organization name: - Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ensure AEM Maintenance Update releases respective code artifacts to Stage and Production Environments  Use-case: We currently do Stage deployments on a weekly basis and Production deployments on bi-weekly basis. However, the AEM Maintenance Update pushes back the baseline code to last successful deployment for Production to Stage as well. This then requires another Stage.Ideally as the pipeline is able to pick up the last commit id of the deployment to Production, it should also be able to pick up the Commit Id of Stage and deploy the necessary artifacts. This deviates from the usual principle of deploying same artifacts on Stage and Production but helps to keep the system in as-is state before and after Maintenance Updates. Current/Experienced Behavior: The custom code that was only available on Stage gets lost and has to be deployed again. Improved/Expected Behavior: The Production instance should have the last known produc

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Better differenciation between Asset-Is-Expired and SubAsset-is-ExpiredVisual by not having a red flag for both - and for the filter. Anwendungsfall: The red flag icon on the thumbnail warns that an Asset is expired. This red flag indicates that a file can not be downloaded. BUT this warning is used by the system for two different occasions.AssetExpired and SubAssetExpired.An InDesign file might contain an expired picture.Now that InDesign file will be displayed with a red flag.But the InDesign file itself is not expired and can be downloaded.Therefore i suggest that there needs to be a better differenciation.Visualy as well as for the expiry search filter. Aktuelles/erlebtes Verhalten: If a picture expires that is built into 1000 documents, the expiry filter now lists 1001 expired assets - even there is only a single expired asset and a 1000 assets in which this picture is a dependency.There is no visual differenciation b

Once an update is posted, we currently don't have the ability to go back and amend anything in that update and resave. This feature would be really handy to avoid any spelling errors, typos, incorrect mentions etc. 

Description - We are using the profile API to enhance a users profile with a CDP solution. Currently when we generate a token (In Adobe Target), which is then inserted into the CDP solution, it needs to be regenerated and replaced every 90 days in order for the functionality to continue undisturbed. Why is this feature important to you - The implications of someone not remembering to do this very manual task is large and in an age where personalisation is at the front of most strategies surely this is a small enhancement that would be deemed necessary for implementation in order to minimise risk for customers How would you like the feature to work - Where Profile tokens are being generated for implementation purposes it would be great to have the ability to choose the timeframe you want the token to expire (i.e. 6,12,24 months) or make it possible to set it as never Current Behaviour - Currently the profile API token expires after 90days, a new token must be generated and replace the

Request: Improve the documentation currently available under https://support.workfront.com/hc/en-us/articles/217196767-Understanding-Calculated-Data-Expressions. Informations at the level of e.g. - Are CASES zero-based? - Is DIV an integer divide? The current situation requires a lot of try-and-error till the expression is working like expected.

Description - Before the upgrade to the Adobe Admin Console, we could create users via the API. It now creates them in a pending approval state and we have to manually approve them. Why is this feature important to you - This is causing a bottleneck in quickly on-boarding users to Workfront.How would you like the feature to work - I'd like it to work as it did before :), or allow an option to be set to pre-approve the users. Or even a separate API call to approve the user.Current Behaviour - Account is created, but requires manual approval, once approved the account is made in the Adobe Admin Console. 

Description: While the new Data Warehouse UI is a much-welcomed step, I think it is missing some features that would make it more user friendly and efficient.These would be: 1. Add calculated metrics.2. Add custom date ranges.3. Add segments to individual dimensions. This is a Workspace staple, it is so necessary.4. Ability to edit/delete created accounts and locations. People make mistakes.5. Requesting an account name, description and hostname seems unnecessary.6. Ability to save notification emails.7. The "Save request" button unshaded seems weird and is unhelpful as you navigate the tabs. A Next button until the last tab (Notification email) would be more helpful. Why is this feature important to you1. Calculated metrics is an integral part of Adobe Analytics, and the success of content/campaigns cannot be fully measured without it.2. Custom date ranges. In addition to previous point, several campaigns and timeframes don't align with a standard calendar measurement (for e

When creating a custom object in Marketo, 3 fields are automatically created: Marketo GUID, Created At and Updated At. These fields are not available in the contraints when using a filter to which this new custom object is linked. These could be extremely useful if you are planning on using these to track custom activities in CRM so you can leverage the "before" or "after" in your date ranges based on the Created or Updated at values.

Description -One feature of the Segment Builder is the ability to use existing segments when building out a new segment. I'll refer to this as a "reference segment".Once the reference segment is dragged into the Segment Builder it becomes "disconnected", and is more like a snapshot of what the reference segment looked like at the time. If an update is made to the reference segment this will not be reflected in any other segments that use it. It would be nice to have an option to "anchor" the reference segment so that any updates made to it are also reflected in other segments. This would preclude the Adobe Analytics user from having to find and update every segment that used the reference segment, and would ensure that changes to the reference segment are immediately reflected across all reports. This feature can be limited to only public segments. There are several risks associated with this idea.Uers may not be aware of how many segments use a particular reference segment a

Existing Option: When am trying to scroll down for adding the location when my browser option is 100%, am not able to see scroll bar options below. (Refer the image attached below.) Every time, I have to reduce my web browser size to 80% and then select the options further. Additional Option:So, I would like to add the point as to optimize the page in a way that even when I see it in 150% zoomed option it has to get modified according to that.   

Description - Add View Option to Group Members and Subgroup Members ListWhy is this feature important to you - Allow to see details about the users within the group similar to every other user list within the UI of Workfront.How would you like the feature to work - Same as all other Filter, View, Groupings setup in WorkfrontCurrent Behaviour - The Filter and Grouping option is present the View option is not. @kaliape @ewanh @moniqueevans 

Once a status update is posted on a task, there are often slight edits to the update that are needed to communicate the update appropriately. Having the ability for the person that posted teh update to edit the post would be extrememly useful and save us tons of time. Currently employees are copying the update and then posting a new one, then deleting the old.

Description - Need a way to stop a running scenario from outside of the scenario itself.   Why is this feature important to you - If a scenario is running on a schedule and I need it to stop, I have no way of doing so.  If I open the scenario while it is already running, it is hit or miss as to whether or not it will even display a Stop button.  Even if it does display the Stop button, it never works.  I have literally a 0% success rate of that button ever having stopped a scenario under these conditions.   Additionally, if I have started a Scenario by clicking the Run Once button and the scenario decides to freeze up in my browser (this happens a lot and is becoming more and more frequent), then there is no way to stop it.  I have to wait the full 45 mins for it to time out before I can continue working on it because the stop button won't work after the freeze up and if I refresh the page, I just get a view of the diagram, not the progress of the cu

Description -Why is this feature important to you - We are looking to inform our reporting system to fetch the latest 360 view of the customer as soon as the profile changes. However, due to the limitation of platform notification , we currently have to do a workaroundHow would you like the feature to work - Data ingestion platform notification should be triggered as soon as something changes on a profile, irrespective of whether the evaluation method is batch or streamingCurrent Behaviour - Data ingestion platform notification is only triggered when profile data changes via batch ingestion , however when data changes via streaming ingestion the notification is not triggered.

Description -In order to see all the Setup menu options below Expense Types (e.g. all the System setup items), you need to be able to scroll vertically. How would you like the feature to work -I would like the scroll bar that is visible at 90% and 80% (and lower %) to be visible at 100% zoom.  (note: that scroll bar used to be there, just a few months ago - not sure when it went away)Current Behaviour -There is no vertical scroll bar on the Workfront Setup menu when you have your browser set to 100% zoom.  It is visible in lower zoom %. 

Description - The Microsoft Teams Plugin does not have the option to like an update. It is also missing a "see it in workfront" button.   Why is this feature important to you - We utilize like to acknowledge a message was read but does not need a response. Without the feature, I am forced to open the object in Workfront, search for the update (comment) and then click like. It adds extra clicks and time.   How would you like the feature to work - Ideally there would be a button next to "reply" called "like" similar to the features within Workfront itself. If that's not possible I would like to see a "see it in Workfront" button similar to the link within email notifications   Current Behaviour - Click the link to the object. Go to the browser, navigate to the updates tab, scroll down to find the specific update (sometimes I have to use "edit > find", and click the like button.

Description -Why is this feature important to you - save timeHow would you like the feature to work - the user who creates a task to be assigned to it automaticallyCurrent Behaviour -  manually assign tasks to users