Build better products with our product team
Description - A "week of year" dimension, that functions similarly to the "month of year" dimension item. "Month of year" allows for year-over-year comparisons at a monthly level and can produce a view where the user can see the raw numbers for current year and previous year along with the percent change between the two time frames.Why is this feature important to you - I would like to be able to do year-over-year comparisons at the week level where I can also see the percent change. How would you like the feature to work - In the same manner as the "month of year" dimension. The values could be 1-52 (sometimes 53) or even better, the month of year and week of the month, for example, "April week 1".Current Behaviour -In current state, I can only add a time period column, which allows me to see the raw metrics for each time frame but does not allow me to see the percent change.
We use programs as a container with projects as a sub-container for types of work/documentation. It would be nice to be able to copy projects to another program or copy a program all together with the ability to remove issues/tasks/documents.
Description - Unable to associate lookup dataset with multiple datasets within the same connection. Why is this feature important to you - It's such an important piece that is missing; if this is not given, I cannot make meaningful reports or spend more time creating my mapping in CJA. How would you like the feature to work - Give the flexibility to associate lookup with multiple datasets. Current Behaviour - While setting up connections, I am ingesting multiple event datasets, a profile dataset, and a lookup dataset in CJA. However, I can associate lookup with only one dataset.
Description - There should be settings or options to NOT create Email only profile/account in Workfront and in the Proofing tool.Why is this feature important to you - As detailed in Current Behaviour, this feature should fix all these issues or provide easy solution or workarounds.How would you like the feature to work - Current Behaviour - In Proofing, If the email address does not belong to an existing Workfront user, Workfront will attempt to create an “External User” or “Guest” profile for them. This is creating duplicate accounts for the user which is causing :1. Users not able to access Proofs on which old account is there2. New proofs getting new account added3. We have to raise a Adobe support ticket to merge both accounts proofs and delete duplicate accounts. There is no way System Admins can fix this.4. No consistency of new account is Guest or old account becomes Guest, email ids crisscrossing5. Please refer Adobe Support Case Number 00438353 from Dell company.
First, the new business rule feature is extremely helpful as it greatly enhances the user experience and strengthens various processes tremendously. Idea: Allow for multiple business rules with the same object and operation (trigger)Current Behavior: System will not allow multiple business rules on same object and trigger Benefits of this idea: Allows enterprises to create multiple simple rules instead of extremely large and complex formulasEnables quicker implementation with simpler testingMultiple administrative team usage - ability to separate business rules by different areas in an organization (limits risk from other teams impacting your rules)Description and title could be customized for each rule for ease of understanding, expansion and correctionsMove from potential large formula chaos to simplified manageable and searchable lists of rules _____________________________________________________________________ FROM Overly complex and risky for enterprise management: TO Simplified, Less Risk, User Friendly:
Description - Approval flows are key functions that often support compliance standards or even legal requirements. Retention of the approval information is essential. Lack of retention has consequences that can devasting to a business if they are audited and found out of compliance.Why is this feature important to you - What is the point of an Approval flow function if there is no record of it? To reliably capture approvals, I now have to build a workaround, probably with a custom form.How would you like the feature to work - Retain the decision of an Approval flow indefinitely. Either retain the Approval flow, log the decision in Updates, or both. Bonus points if you give sys admins the ability to lock down the ability to remove Approvals from objects.Current Behaviour - If you associate an Approval with a request, then convert that request to a project, the Approval is removed from the request. There is no place where the outcome of that Approval flow is documented—not the Approvals area and not the Updates area. Workfront support confirmed that this is behavior as designed.
Description - It would be nice when you copy a template it would also carry over the users that the template is shared with Why is this feature important to you - It's redundant work to add the users again when you're copying from a template How would you like the feature to work - Carry over the users the template is shared with Current Behavior - It does NOT carry over the users when you copy a proof workflow template
Description - Enable proofing in the Workfront Sandbox Instances. Why is this feature important to you - All other "add on features" that are integrated with Workfront like Scenario Planner, Resource Management Tools, Goals all are available in a sandbox so users can test out different scenarios without creating test data in production. Now that proof is integrated, it should follow the same path. Also, when trying to implement proof for the first time, the users will need longer than 1 week to do configuration and testing, making preview only useful for shorter testing functionality. If we are forced to use preview that creates A LOT of extra work on implementation.
Description - Add modules to Fusion that allow reading / updating content in Excel files stored in Workfront, without downloading the the files, similarly to the modules in the existing "Microsoft Excel 365" module family.Why is this feature important to you - We rely on importing data from XLSX files into WF via Fusion and currently this can be done only by saving the files to OneDrive. This is a workaround that raises data security issues: Any member of the Fusion team holding our scenario can access all files stored in the OneDrive. (Plus the scenario needs to be updated when the owner of the OneDrive leaves the company.)How would you like the feature to work - New Module family (group) including a set of modules analogue to the existing "Microsoft Excel 365" group, except maybe the "Watch event" modules. Retrieve type modules allow accessing data stored in XLSX files stored in WF. Update / Delete type modules update the file stored in WF, resulting in a new version of the file added.If the Update/Delete type modules are too difficult to implement, the Retrieve type modules alone would be a great addition.Current Behaviour - The described modules do not exist. Pulling data from / editing XLSX files is only possible if the files are stored in OneDrive.
Description - The "my task" widget on the New Home area defaults to showing ALL tasks that a user is assigned to. We have the option to set default filters at the layout template, but it becomes "sticky" when an admin does this. The default filter for my tasks should prioritize work that can/should be happening. The my work widget isn't optimal to use since it's not as streamlined as the My Task widget. Why is this feature important to you - Users need a list of actionable to do items that's clean and easy to manage. By showing them things not ready for them it's confusing and not a great user experience. How would you like the feature to work - Default to the filters to show only current work or allow admins to change it without it impacting other areas of the tool. Current Behaviour - User has to pick the filter or the admin can set it but then it becomes sticky across all pages.
Related Case Number: 00437896Summary:We request a feature enhancement that allows administrators to disable the "Log Time" button on tasks while still allowing users to log time via the timesheet.Current Limitation:Currently, adjusting the task access to "View Only" (as advised in case 00437896) removes the “Log Time” option from tasks — however, it also disables time logging from the timesheet for those users. This limits our ability to manage permissions flexibly while maintaining operational efficiency in time tracking.Business Need:For governance and process control, our team needs to restrict time entry directly on tasks to prevent incorrect logging, especially after a project is no longer active. However, we still need users to log their hours via the timesheet, which is our preferred method. The current limitation forces us to choose between two incomplete solutions.Proposed Solution:Introduce a configuration option (at the system or access level) that:Hides or disables the “Log Time” button on tasksRetains full access to log time through the timesheetThis would provide more granular control over how time is entered into the system, improving data integrity and aligning with our internal time tracking policies.Impact:This change would enhance compliance with internal controls and reduce the risk of post-project time entry errors, without disrupting legitimate timesheet workflows.Thank you for considering this feature request.
Description:There are a few functions available in Workfront expressions that aren't available or easily accomplished in Fusion. For example: WEEKDAYDIFF which works similar to DATEDIFF but only counts weekdays. This is useful since durations are measured in working days, and we have automations that need to calculate durations based on various inputs. WEEKDAYDIFF isn't available in Fusion as a function and there isn't a clear or easy way to calculate it using the available logic.Fusion supports advanced expressions that would never be possible in Workfront. There should not be any situation where Workfront can support a simple expression using a single function, but that same logic is difficult or impossible to accomplish in a Fusion expression. Why is this feature important to you:It is sometimes difficult to mirror Workfront logic in Fusion because Fusion doesn't always have a similar function to mimic. Extra time spent by developers trying to devise workarounds reduces the value that Fusion offers. How would you like the feature to work:Review the list of all functions that Workfront supports, and for the few that don't have a matching function in Fusion, add them to Fusion. Calculated Data Expressions Current Behaviour: For the few Workfront functions that aren't available in Fusion, we fall back on performing the logic in a Workfront calculated field. This is less efficient and requires custom parameters on Workfront records that wouldn't otherwise be necessary. If you like this request, please take a moment to view and vote on my other Idea Requests: https://experienceleaguecommunities.adobe.com/t5/user/viewprofilepage/user-id/17555852/contributions/ideas?filter=authored
ダイナミックチャットとZoomを連携させてほしいです現在ではMeetのみ対応可能なので、今後は機能を拡充してほしいです
I recently created an SDR within the AA workspace project. The thinking is that users should be encouraged to use the AA workspace tool as much as possible, as compared to generating an excel based SDR that has to be stored externally. Some examples of what I built 1) a picture of the different sections of the SDR - 2) a picture of the different panels, one for each variable (props illustrated) indicated its number, its name and whether or not the variable is enabled 3) an overview of a specific variable details. I get that there are some items in this example that might not be easy to automate, like the BRD reference number with a hyperlink, but I think it would be great to have a tool in the AA admin areas that would generate an SDR template within Workspace grabbing all the information it can from the AA admin area report suite traffic and conversion variable screens. UX: The admin would click a button, the script would create an AA project, add panels for all the evars, props and events and then pull in the details from the admin area. The script would have to be smart enough to know how many panels to generate - meaning company A may have 10 props where company B may have 30 props enabled. The script would have to check to see the 'largest' number variable (prop10 for example) that was enabled, use that number as an input and generate that number of panels. The template should have additional placeholders for the 'BRD requirement number' and 'administrator notes', so you can then encourage adobe admins to fill in the missing details. Longer term, it would be great to be able to click a button and 'update' the SDR project with any new information, not overriding the information that was entered in manually (like BRD reference number), but that might be too much to ask as an initial idea. I also have an example of a BRD and a Tech Spec document I built within the tool as well. Meaning this idea could be expanded to include all types of documentation templates. Given the flexibility of AA workspace, I don't see why we (as a community) can't document everything within the AA tool. On a side note, I just saw Adobe's EXCEL based "adobe_analytics_inherited_implementation_playbook" that was just released. Again, why was this was done in Excel when Workspace's API could have been used, is beyond me.
Description:We are requesting a reporting feature that provides visibility into the usage of widgets on users' homepage dashboards. This feature would help us better understand engagement with dashboard components and identify which widgets are actively being utilized. Why is this feature important to you?Understanding widget usage is essential for optimizing dashboard design and ensuring that users have access to the most relevant and effective tools. By identifying which widgets are frequently used or have been recently interacted with, we can make informed decisions about dashboard layout, training needs, and potential areas for improvement.How would you like the feature to work?The feature should generate a report that includes the following details for each user:Type of Widgets in Use: A list of the widget types currently active on the user's homepage dashboard.Date Last Touched or Frequency of Updates: Information indicating recent interaction or update frequency for each widget.Note Text Widget Status: Specifically track whether the Note Text widget is active, without needing to capture the content within it.Importantly, we do not need to know the specific data entered into the widgets—only whether the widget itself is present and actively used.
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