Build better products with our product team
Our organization aims to determine the most common times of day when users open messages from specific campaigns. We want to know whether they tend to open them in the morning, early afternoon, late afternoon, or other times.When creating a report, we have Time dimensions available for Day, Hour, Minute, Month, and Quarter. However, the Hour dimension currently only specifies the hour of a particular day (such as 9:00 AM on April 1, 2023), not the hour of a general day (such as 8:00 AM - 8:59 AM)
Right now, if we are on a Task, and we convert that task into a Project, as soon as we do that, the original task is deleted. The request is the following:We are in Project A, and we have Task number 1.We are in Task Number 1 and convert that Task into Project B.The Task number 1 will remain in Project A.User will update the progress/status of the Project B.Automatically update the progress/status of task 1 in Project A. Regards.
Checked off/actioned comments should be removed from the comment count#. Only new comments on the newest version of a proof should be counted.
DescriptionWhile our users try to adhere to standard naming conventions for Target activities, the names are not fixed and may be adjusted throughout the lifecycle of the activity (Development, QA, Production, Completion). The only permanent identifier seems to be the Activity ID, however it is also useless because you cannot search by it.Why is this feature important to youBeing able to search by Activity ID would also give us a permanent way to refer to activities in other documentation where it would be impractical to keep updating the name.Please note that changing the name of the activity based on the status of the activity before and after launch was a recommended approach from our Adobe consultants. How would you like the feature to workEnter the activity ID in the Target UI activity search box and return the specified activity.Current BehaviourThe search tool only works with activity names at the moment.
Make instances an available metric for data warehouse reporting. If it's in the regular UI it should be in DW too.
Request for Feature Enhancement (RFE) Summary: Page unlock feature to product admin Use-case: When a page is locked by user and goes on a vacation or out of shift. Other authors need to wait until the user is back or need to create a ticket with adobe which is taking lot of time time. Current/Experienced Behavior: Even product admins not able to unlock the page and impersonate as that user also not helping to unlock. Only adobe admin users are able to unlock the page as of today. Improved/Expected Behavior: Product admin should able to unlock the page directly or by impersonating as page locked user. Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Organization name: Bread Financial Screenshot (if applicable): NA Code package (if applicable): NA
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 Data Science framework. This can be facilitated by introducing a new, user-friendly interface for the data science workspace, akin to existing solutions like Treasure Data. Enabling seamless integration and deployment of custom models would empower users to extract more meaningful and targeted insights from their data.Current Behaviour: At present, the platform is limited to the out-of-the-box (OOTB) Customer AI Intelligent services. While these services provide valuable functionalities, the absence of an option to incorporate individual machine learning models into the platform confines users to the predefined capabilities. This creates a gap where users cannot fully leverage their data for more specific and nuanced analyses. The current system lacks the flexibility required to accommodate the diverse machine learning models that users may want to deploy.
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 production deployment artifacts while the Stage instance should similarly have its last deployed artifacts to ensure continuity. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS (AEM Release - 2023.12.14538.20231205T165334Z) Customer-name/Organization name: TA Digital Screenshot (if applicable): AEM Version Updates | Adobe Experience Manager Code package (if applicable): N.A
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 between an expired InDesign and an InDesign that simply contains an expired asset. Users see the red flag and get the impression that the file can not even be downloaded. Verbessertes/erwartetes Verhalten: For the Thumbnails, this can easily be done by having a small change in /libs//dam/gui/coral/components/admin/contentrenderer/card/asset/propertyList.jspThis already checks between the two states:if ((isContextCollection || properties.contains(VIEW_PN_IS_ASSETEXPIRED)) && (isAssetExpired || isSubAssetExpired)) { %> <coral-card-property class="expirystatus" icon="flag" data-is-asset-expired="<%= isAssetExpired %>" data-is-sub-asset-expired="<%= isSubAssetExpired %>" title="<%= xssAPI.encodeForHTMLAttr(i18n.get("Expired")) %>"></coral-card-property> <% } I changed this for my organisation, but i think it would be a great improvement for everybody OOTB. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Currently the Percent Complete roll up at the Program level only takes into account Projects that are in "Current" status. This does not make much sense as you are completely ignoring all projects that have been fully completed and marked as such. If all projects under a program have been marked as complete status, then the Percent Complete at the Program level should show 100%
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 old one.
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 example, since product launch).3. Segments to individual dimensions. While we can do an overall segment, adding segments to individual dimensions within DW would save an enormous amount of time during data analysis. It is a staple of Workspace already.4. Edit/Delete created accounts and locations. People make mistakes but also server information and credentials becomes outdated. Leaving the incorrect information there may lead to mistakes and isn't efficient.5. account name, description and hostname seems unnecessary. This is just repetitive and counter-intuitive. It should be a name and server information. The name can be the description.6. Save notification emails. Every other repetitive task has been eliminated but this one has been left on.7. A Next button until the last tab (Notification email) would be more helpful. Given how counter-intuitive the Save button currently is (and the fact that there needs to be information in each of the tabs) a next button until the last tab follows standard web UI more closely.How would you like the feature to work1. Calculated metrics. Make it available the same way it is now in Analysis Workspace.2. Custom date ranges. Make it available the same way it is now in Analysis Workspace.3. Segments to individual dimensions. Drag and drop from the segments bucket. Make it available the same way it is now in Analysis Workspace.4. Edit/Delete created accounts and locations. Add a delete and an edit button.5. account name, description and hostname seems unnecessary. Remove description6. Save notification emails. Add a plus sign (same UI as create accounts and locations)7. A Next button until the last tab. Remove Save and add next instead. Add save to the last tab (Notification emails) Thanks to @jennifer_dungan I wasn't able to reply to your comment in the questions part.
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 as an "anchor", and thus may not truly understand the ripple effect caused by an update. Users would have to be provided with some sort of notification in the Segment Builder that shows both that a segment is being used as an "anchor" (think of a little icon next to the segment name) and which segments are using it as anchor. This option should require permission rights from an adminA change to the reference segment may break the segment logic of other segments, making them no longer work. This could happen if the container types in the reference segment were adjusted. One way to alleviate this would be to disallow the use of anchor segments in some cases, such as in sequential segments. Another option would be to not allow the anchor segment to update in a segment if the segment logic will be broken. The user would then have to be notified of the segments where this occurred so that he or she can make necessary adjustmentsWhy is this feature important to you -My organization often uses several core segments for KPIs, and then creates more nuanced segments based off of these core segments. The number of segments that use the core segments are substantial, meaning that a small change made to a core segment requires updating a large multiple of other segments with the same small change. How would you like the feature to work -When a reference segment is dragged into a new segment in the Segment Builder, a user can click on the gear option and select "Anchor Segment". Any updates made to this reference segment will automatically update this segment as wellThe Segment Builder page for the reference segment should indicate whether the segment is being used as an "Anchor Segments". This can be done using an icon or some similar call outThe Segment Builder page for the reference segment should contain some sort of interface for showing which segments use this segment as an "Anchor Segment"A warning should appear when someone tries to update an "Anchor Segment", telling the user that updates to this segment will impact other segmentsCurrent Behaviour -Dragging an existing segment ("reference segment") into the Segment Builder creates a copy of the existing segment. The reference segment component of the new segment will not update if the reference segment is updated.
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.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
