Product ideas | Community
Skip to main content

10000 Ideas

edersantosNew Participant

Option to Disable "Log Time" on Tasks closed or completeNew

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.

William--
William--New Participant

Make all Workfront functions available in Fusion (WEEKDAYDIFF)New

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

jlinhardt_blueAcornNew Participant

Automate the creation of the SDR in AA's admin areaNew

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.

venkatdEmployee

Making the Language Copy Dropdown Languages List Configurable via DialogNew

Request for Feature Enhancement (RFE) Summary: Currently, the list of available languages displayed in the Language Copy dropdown is sourced from the out‑of‑the‑box definitions located in /libs/wcm/core/resources/languages. To add or customize languages (such as adding Kazakhstan using ISO code “kk” or “kk‑KZ”), customers must overlay this resource to /apps/wcm/core/resources/languages. This enhancement proposes introducing a configurable authoring dialog (or admin interface) that allows administrators to manage the languages list in the Language Copy feature without the need to overlay OOTB files. Problem Statement: Current Behavior: The list of supported languages is static and defined in the repository under /libs/wcm/core/resources/languages. Customizations require creating an overlay (/apps/wcm/core/resources/languages), which is manual, error‑prone, and requires technical expertise. Impact: Customers who need to add or update language definitions (for example, when a new language like Kazakhstan is needed) must rely on a technical workaround. This process prevents non‑technical users (or content administrators) from easily managing the list and can lead to inconsistencies. Proposed Solution:Develop a new configuration dialog or admin interface that: Provides a user-friendly interface for managing the list of locales available in the Language Copy dropdown. Allows administrators to: Add new language entries (e.g., defining the ISO code, display name, and any associated metadata). Edit or remove existing entries. Reorder the languages as needed. Integrates seamlessly with the existing language copy functionality so that any changes in the dialog take immediate effect in the target dropdown. Uses a persisted configuration, such as an OSGi configuration or JCR node under /apps, ensuring that changes remain consistent across updates and do not rely on repository overlays of OOTB files. Benefits: Improved Usability: Authors and administrators can manage language definitions in a straightforward, non‑technical manner without editing repository files. Flexibility: The languages list becomes easily configurable, allowing for quick adaptations (e.g., new language support, corrections to existing definitions). Reduced Maintenance Overhead: Eliminates the need to overlay and maintain duplicate resources, reducing the risk of misconfiguration after updates. Use-case: A customer wants to include Kazakhstan in their language copy options. Instead of overlaying /libs/wcm/core/resources/languages to /apps/wcm/core/resources/languages and manually adding the language definition, the admin navigates to a “Language Copy Configurations” dialog, clicks “Add Language,” enters “Kazakhstan” with ISO code “kk” (or “kk‑KZ”), and saves the change. The Language Copy dropdown now immediately reflects the new language setting without any manual repository changes. Current/Experienced Behavior: Currently the Language Copy dropdown is not configurable by the author Improved/Expected Behavior: Provides a user-friendly interface for managing the list of locales available in the Language Copy dropdown. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 all versions Customer-name/Organization name: AGILENT TECHNOLOGIES - ACOM Screenshot (if applicable):   Code package (if applicable):