Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

PavanRaAdobe Employee

AEM - Desktop App EnhancementDelivered

Request for Feature Enhancement (RFE) Summary: Enhance AEM Desktop to detect new files from local cache and bulk upload new files within a downloaded folder Use-case: When creative users work on product creation. It is usually at a folder level, where they have multiple files within a folder. This complete folder would be treated as a single entity.The users work on multiple files within the folder, also creating new files. Users generally use save as feature on their creative Apps (  Applications for creating assets) to save/export to a particular format. The desktop app currently tracks only the existing files which are synced from AEM cloud to desktop. The newly added files even though are available on same hierarchy on their local cache is not displayed within the desktop App and the users have to manually drag and drop from local cache space to desktop app for uploading. The new file in the local cache is not even shown within the desktop app.A feature which can show some indication of newly added files in an already downloaded folder, similar to how it shows files which are edited locally will be greatly beneficial for the product designers to seamlessly sync new files in the local cache to AEM Additionally an option of uploading all changes from the immediate folder at one go, this would eliminate the need for user to drag multiple files manually and checking-in locally edited files. This would highly improve the user experience. Current/Experienced Behavior: Currently the users have to manually select the new files/ manually drag and drop into specific folders to upload to AEM. Currently users do not have a capability to select folders and upload from local to AEM Improved/Expected Behavior: Detect any new files in the local cache, display the new files to the users who then chooses within desktop app ( multiple at once) to upload with the AEM Desktop upload button. Capability to select a folder and initiate upload, if the folder contains new files the get uploaded. Any files which were edited locally are notified to users that they will be checked in with the folder level upload. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Desktop App 2.3.1 Customer-name/Organization name: H&M Screenshot (if applicable):   Code package (if applicable):  

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
Community Advisor
WilliamCommunity Advisor

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

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.