Build better products with our product team
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.
Currently, you can only choose to color code the items in the Workload Balancer based on the project status, but it would be helpful to visualize the Tasks by their individual statuses.
Request for Feature Enhancement (RFE) Summary: Custom domain names are supported in Cloud Manager for both publish and preview services for Sites programs. Custom domains for author services are not supported. Use-case: Currently the Author service is accessed via URL in format -https://author-p<Program-ID>-e<Environment-ID>.adobeaemcloud.com Custom domain name for Author should be service should be supported similar to Preview and Publish Services. Current/Experienced Behavior: Only URLs of below format are allowed - https://author-p<Program-ID>-e<Environment-ID>.adobeaemcloud.com Improved/Expected Behavior: Custom Domain Mapping should allow URLs like https://brandAauthor.brand.com to be mapped to Author service. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2023.4.12142.20230526T152858Z Customer-name/Organization name: TA Digital Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Having an editorial feature to configure mapping of JSON fields Use-case: To decouple SPA deployments from Adobe Experience Manager (AEM), Having an adapter layer that facilitates dynamic mapping of JSON fields between AEM components and frontend SPA components. This approach ensures that changes in frontend development require minimal configuration in AEM, promoting a more agile and independent deployment process. Current/Experienced Behavior: SPA deployment has to align with AEM deployments whilst mock data mapping in place. Improved/Expected Behavior: Realtime testing in pre-prod environments before hand. Also, helps in productivity by reducing dependencies in wider teams(Infra Dev and QA) Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: PremierLeague Screenshot (if applicable): Code package (if applicable):
This idea is for Reviewer/Work license users to have the ability to view financial data/expenses within a project they are on. Right now they cannot see any financial data on the project because their plan license does not allow for "manage" rights even though the access level for the Reviewer licenses is set up with "View" under the "Financial Data" category - which does not work because of my previously stated comment about "manage rights". (sigh) I previously submitted this bug (err, feature) as a support ticket which was later closed because of the whole manage rights thing. But it is still an issue for us as we would like certain users to see this information... specifically for the project they are on. The option to give Financial Data (view) access can still be given/selected but does not work (again, because of the "manage rights" problem). Today I submitted a follow-up ticket which will probably get the same response originally given (you guessed it, because of the "manage rights" roadblock)... but I digress. :) So if this is a pain point for you too, please consider upvoting this idea to actually give the view rights to any license user we desire. Thanks in advance!
Description - It would be nice to have the read receipt function when someone reads your update, currently within our organization, we have a number of users that "ghost" our project managers or claim they never saw the message. The read receicpt functionality would help to decrease the number of those issues I believe. For the second part of my idea, having the ability to highlight and/or change the color of the font would mimic other communication platforms such as Teams and Outlook that allow for the user to highlight important information or call our different color text to mean certain this. It would just add another layer of customization for communicating in updates.Why is this feature important to you - I believe it will lessen issues regarding missed notifications as well as increase productivity if users know someone can see they have read their message.How would you like the feature to work - Once the person opens to the update that was sent to them, it automatically sends notification if that notification is toggled on in the users profile to show the sender the message was read and also shows the time and date stamp the message was read underneath the message in updates.Current Behaviour - There is no current behavior for this
Right now we can only edit comments if we have "Commenting Beta" enabled but only for 15 mins, after the comment/update was posted, we need to have to possibility to edit them at any moment, not only 15 mins after. Thank you.
Description - I think it will be great if campaign has a built-in change log to workflows that shows who made what changes and when. Why is this feature important to you - This will help improve collaboration, simplify troubleshooting, and support audit requirements especially in scenarios when multiple users edit the same campaign.How would you like the feature to work - When a user edits a workflow (adds/removes activities, makes changes in properties, modifies queries, etc.), the platform should automatically log the change with username, timestamp and type of change.Current Behaviour - Currently Adobe campaign does not track changes made to workflows. In case multiple users work on same campaign, its difficult to identify who made which all changes. This lack of visibility can lead to confusion, rework, errors etc.
Description: I want to have the ability to save the columns of a specific report as a new View.Why is this feature important to you: sometimes we figure that it will be good to have the same view of a report within the specific object and we need to manually create the view copying the report.How would you like the feature to work: within the reports editing view, columns (View) section, right next to the "Apply existing View" button, labeled as "Save columns (View) as new view".Current Behavior: there's no easy way to replicate a view (columns) of a report as a view in the object's list itself.
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