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のみ対応可能なので、今後は機能を拡充してほしいです
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: 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!
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.
Description - When a request/issue is made we have a custom form where a user can select a product or program associated with a different portfolio. When the request is converted into a project, our project manager has to manually change the product or program field that in the overview section for the newly created project, based on what was input in the custom form on the request. Why is this feature important to you - It creates a lot of confusion and extra work for our project manager to try to manage these two fields. If they forget to change one of them it alters reports and dashboards for them and for management. How would you like the feature to work - It would be nice if there was a way to automatically populate the product or program field in the overview section of the project based on the field in the custom form of the request and even better to tie the two fields together so that if it's updated in the overview, it's updated in the custom form. Once the request is converted into a project the field in the custom form is used as a reference only, so it could even turn into a read-only or calculated field. Current Behaviour - Right now, the custom form field is separate from the product or program field on the project and both fields must be maintained and updated separately.
Request for Feature Enhancement (RFE) Summary: I often find my self in difficulty while comparing properties of a node in AEM CS instance, where crx/de is not accessible. So for accessibility purpose this will be a very good enhancement for Repository Browser in AEM CS. Use-case: Current/Experienced Behavior: Repository Browser in its current form, is not having property type option as it used to be in CRX/DE so it is often confusing where it is String or Long or Boolean for some of the value. Though it is provided "[]" for array type but which type of array it is. Some time we just need to compare number of property, since there is no numbering for each property we need to count one by one property this is very problematic. Improved/Expected Behavior: Type column for property and serial number for the same should be there. Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Organization name: NA Screenshot (if applicable): CRX/DE: Expected: Repository Browser: Should be improved: Code package (if applicable): NA
There are several UX issues with how the notes are implemented Why is this feature important to you - In a large scenario it's often useful to see notes when fairly zoomed out. It's a nuisance to have to zoom in to see if the note is even the one I need. The positioning takes the cake. Now I get to drag, too, just to read notes. Notes should make my dev life easier - not add to my cognitive burden 🙂 How would you like the feature to work - I want note cards to open exactly where I positioned them I also want to not have to erase boiler plate text when creating a note I also want to be able to READ the note without having to zoom in So: - don't auto position notes, ever unless someone clicks Auto-align. Then move the note along with the module/filter it's attached to. Don't move the note as if it were a module - clicking a note should open what is the "editor" and show me the full note body (with scroll bar if needed) and and edit/delete button - use the attribute "placeholder" instead of hard-coded content Current Behaviour - - notes are parked a mile away - notes are illegible unless I zoom in - i have to delete a boilerplate text when creating a new note
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.