Build better products with our product team
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のみ対応可能なので、今後は機能を拡充してほしいです
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.
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):
Description: Make it possible to delete a report suiteWhy is this feature important: To clean up accounts or prevent an old, legacy report suite from receiving traffic (and therefore causing cost)How should this feature work: Add a button to the report suite manager that, after a confirmation dialog, will trigger the deletion of a report suiteCurrent behavior: Right now it is not possible to delete a report suite, though you can hide it from being displayed to the user
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
Request for Feature Enhancement (RFE) Summary: Request to make paraformat options configurable for Richtext field in content fragment in AEM 6.5.20 Use-case: Ability to author H4 to H6 in richtext field in content fragments in AEM 6.5.20 Current/Experienced Behavior: Richtext field(sling:resourceType=dam/cfm/admin/components/authoring/contenteditor/multieditor) in content fragment supports paraformat options from H1 to H3. If we have to add H4 to H6, it needs overriding of OOTB file /libs/clientlibs/granite/richtext/core/js/plugins/ParagraphFormatPlugin.js which should not be the case Improved/Expected Behavior: Please make the paraformat options configurable / make all the standard header options (H1 to H6) available OOTB Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.20 Customer-name/Organization name: NRG Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.