Build better products with our product team
Description - When converting a request to a task or project, the user would see the documents section that is typically available to the requester during form submission. This would allow the user to quickly drag and drop any additional files that were not uploaded when the Request was first submitted. They could do this after the Project is created, but that involves a few more clicks around the interface and this would be faster. Why is this feature important to you - It would reduce the number of clicks needed to add documents either before or after. My process would be more efficient. How would you like the feature to work - This would work exactly like adding a Task to a Project using the "+ New Task" button and clicking "More Options." Picture attached.
The Workload Balancer is really the only part of the Resource Manager that our teams use. The other features have not proven to work for us. The Scenario Planner (which seems unfinished) needs more of a connection between its features and the Workload Balancer. Combining the two would unify the planning of possible initiatives with the reality of a team’s capacity. They are currently disparate and fall short in how much they can be used to roadmap work quickly and efficiently. If you were able to quickly work on new initiatives and broadly assign users to those initiatives on the fly, that would be an extremely useful feature. Another disparate feature is the relationship between the Workload Balancer and the Work Effort columns in a project view. I should be able to update this percentage in the Work Effort column from within a project view and have this be reflected in the Workload Balancer. Right now it is only the “small, medium, large” shortcut, but it should be specific percentages like the allocation feature in the Workload Balancer allows. It takes too much time to click away from a Task view and into the Workload Balancer view from inside the project. The new filters GUI should allow you to switch between to a text edit view.The 3 month view should still split the allocations up by weeks. The current distribution of hours is very confusing when applying a single percentage to an entire 3 month period. It’s hardly ever used because of this. The tool should show Task status colors in Workload Balancer. Currently, you can only choose to color code the items in the Workload Balancer based on the project status, but this is misleading if the project is in-progress (green), but the task is on hold (red) because all tasks would show as green. It would be helpful to visualize the Tasks by their individual statuses.The Utilization feature is not used because it is only month-to-month, the filter system is yet another method of configuring, and it doesn’t describe actual user assignment. This is another example of a feature that should be more integrated with the Workload Balancer and not a separate view. Anytime the tool only shows “FTE” instead of the actual % is confusing. As an example. This can be seen in the Planner view. [4/22/2024] The ability to move/shift task dates would be a HUGE time saver. It’s understandable that doing this is difficult because of the various task constraints and dependencies of the tasks within the project. However, you have options if you auto-set the tasks to fixed dates once you move and the original task constraint doesn’t work with the change you’ve made. Another option would be to treat these if you took the approach of the Scenario Planner and treated the
This would be helpful for when using a prompt in a report and the filters are worth saving as a new, non-prompted report.
Description:The Scenario planner feels like a forgotten function of the tool. It’s very convenient for quickly getting projects added to Workfront as initiatives and moving them around, but it falls short in how it can be made more useful during project roadmap planning. The function would need to include:Project-to-project dependencies The ability to tie the start date of an initiative to the end date of another. This would be great for regular projects as well versus having to associate tasks within them.Custom form editingThe ability to associate custom form data at the initiative level that would carry over after publishing.Project summary view within the scenario plannerIf an initiative is tied to a project, you can more easily see the project details without leaving the page. More initiative dates optionsThe ability to sync resync my initiative dates with project dates.More specific dates - monthly increments can be too broad Reveal the Scenario Planner’s initiative rank as a valueCurrently this isn’t reportable like the portfolio optimizer rank, but it would help if it was. Merge or better integrate with the workload balancerThe current hours/FTE tracking of the current Scenario function is confusing and unusable. You can extend this same frustration with the disparate Calendar feature that is also useful in its own way, but disconnected from the way the rest of the tool functions. These features feel like they were designed for one company in mind, but don’t apply to everyone else. The use case that involves the scenario planner is:A marketing team of creatives begin to develop initiatives (project ideas) that align to the goals set by leadershipThe team adds these project ideas QUICKLY onto a roadmap view (Scenario Planner). They can move the initiatives around quickly and in correlation with actual projects. They can associate form data like objectives/goals, status, and relationship to other initiatives/projects with the initiatives in the planner.They can publish to create or update projects, but also sync project changes back to the initiatives in the planner.
Description - We would like all custom fields to have a check box that denotes "System Admin Only" can update. We want this to appear on existing and future fields created. We want to be able to select this during and after a new custom field is created. We want a System Admin to go into a custom field and select "System Admin Only". Why is this feature important to you - We have approximately 60 key custom fields that we only want System Admins to be able to modify. Yes, we educate and enable System Admins and Group Admins on how custom forms/fields work. We ask that any requests to modify these 60 key fields be brought to Governance Board. We have a custom form with these fields on it that we ask users to refer to. We also have a google sheet with these fields listed. We have learned (the hard way) that people forget. We need to add in a level of checks and balances to these key fields. This monitoring becomes even more important as we integrate into new applications in the future. We are currently integrated into AEM, and have active fusion scenerios. How would you like the feature to work - We want all existing and future custom fields to have a checkbox titled "System Admin Only can update". This should appear at the top of the field. There would be in information text that would advise the user that only a system administrator can update this field, please reach out to them directlyCurrent Behaviour - Group and Sys admins can create and edit key fields that require governance before creation or editing. Realize this would require existing fields to be reviewed by Governance Board, which is fine. Also acknowledge ongoing governance would be needed to identify future key fields that require the "Sys Admin" only updates.
Request for Feature Enhancement (RFE) Summary: If someone is migrating to AEM and now want to add whole folder in assets without choosing single files. So, to reduce production time there should be option to upload a folder in AEM assets. Use-case: It will help to upload folder in assets and helpful in bulk assets upload. Current/Experienced Behavior: Currently there is no option for uploading folder in AEM assets while we upload DAM assets to AEM Assets. Improved/Expected Behavior: It will be helpful to upload a complete folder of assets instead of single assets file. Environment Details (AEM version/service pack, any other specifics if applicable): All Versions. Customer-name/Organization name: Bhavi Screenshot (if applicable): Code package (if applicable):
Description - It is a known issue that the Recommendations UI cannot be trusted. This is problematic. Why is this feature important to you - Without accurate data, troubleshooting and set-up is incredibly difficult.How would you like the feature to work - The counts and data should be accurate.Current Behaviour - It shows incorrect counts, it shows expired products, the data is mismatched. At a minimum, it should be made known that the UI is incorrect in the solution. Target can be used to put banners on websites, how about a banner on the catalog page that the data can't be trusted?
There is no native integration between Marketo and Instagram. Marketo Engage should either provide a native integration or enhance the Facebook integration to also support Instagram requests.
How many times a trackAction is activated with an ID that is not registered or is entered incorrectly within the native app code.Taking into account that the development cycles for the deployment of applications within the different STORES (Android & IOS) can take months, these trackActions are dirtying the data and can sometimes increase the useless consumption of SERVER CALLS in your company.This can cause unwanted SERVER CALLS billing.Currently, the "CONTEXT DATA" data in the event we want can be modified through Adobe Launch, enriching the event from "Adobe Launch", but we cannot prevent a "SERVER CALL" from being executed even if we do not need it in our implementation. How would you like the function to work?Ideally, to avoid unwanted "SERVER CALLS", we would include an option in the "MOBILE CORE" where we could prevent the execution of a "trackAction" or a "trackState", conditioning based on its "action name" and/or contextData (in Adobe Launch UI). Current behaviorThere is no way to prevent a "SERVER CALL" from being consumed and counted, even if it is not controlled, or has been included by mistake within the source code of the mobile application through the "trackAction" / "trackState" events. There are some issues in the community regarding this that are quite old.This feature should be a "MUST" to better control the data that reaches the Report Suites, it would give a lot of flexibility and control over the data.
Description - Allow the Widget options on the homepage to be sticky, i.e., Collapsed vs Expanded, "Showing" number, etc.Why is this feature important to you - Most of my projects are long-term, so I like seeing all my project names without the tasks unless I'm working on that specific project.I change "Showing" from 25 to All and collapse all the projects so I only see the project names. This is better visually (not as overwhelming when I don't see all the tasks under the project) and helps me prioritize at a glance and recognize new projects that I might have a one-and-done task instead of multiple tasks.How would you like the feature to work - If I change "Showing" from 25 to All and expanded to collapsed, make those changes stick unless I change them again. Also, make the widget window resize automatically to fit the displayed content instead of leaving a big white space. Current Behaviour - The My Tasks widget defaults to "Showing" 25 and all projects are expanded and the widget window doesn't resize after I collapse them. I do this multiple times a day. Also, after changing "Showing" All, it doesn't give me the original options again, i.e., 25, 50, 100, All. Thanks for considering!
Hi Team,I hope this message finds you well. I would like to propose an idea for a new feature that could enhance our document access management.Feature Proposal:The proposed feature would allow document access to be automatically managed in two steps:Initial Access: Grant public access to external users, allowing anyone with a public link to view the document.Automatic Change as per selected date: After a defined date or time automatically change the access settings to restrict visibility so that only specified users on the access list can view the document.Benefits:Enhanced Security: Ensures that sensitive documents are not permanently accessible to external users.Improved Workflow: Simplifies the process of managing document access by automating transitions.Time Efficiency: Reduces manual effort required to update access settings.I believe this feature could significantly benefit our team by allowing temporary public access while ensuring privacy and security after the designated period.I would love to hear your thoughts on this idea and discuss its feasibility for implementation. Please let me know if you need any additional information or clarification.Thank you for considering this suggestion. Best Regards,Saurabh Birwadkar
We would like to have a direct link between a Slack channel and the Workfront update feed of a project (and other work items).When sending a message in the Slack channel, an update is automatically posted on the related project in Workfront. This would work in both directions. When writing an Update in Workfront, the Slack channel gets updated.With this feature no important information will get lost in a Slack channel, but to be found where it is needed the most!
Currently, when you upgrade an extension, you get this notice:This has scared quite a few clients off of upgrading, because there really is NO going back. Especially for Adobe extensions, there is a strong need to be able to revert in case of issues (not to be snarky, but appMeasurement/VisitorID code updates have a history of finding major problems in the first month after release). Issues like Re: What are possible reasons why ClearVariable fails? make it clear why someone may want to move back. If you upgrade and you do see something break in staging during testing, you'd have no way to go back/compare/undo.
Current Behavior: When a proof is created and a custom proof message is used, by default it will be used for every version of that proof. Sometimes the custom message is very specific to the round of proof. When that message is sent out in additional versions it can cause confusion. By defaulting it between rounds users can forget to uncheck it when creating new versions. This has caused confusion with some of my groups.Proposed Behavior: Include a setting that would reset the use of a custom notification for additional rounds of a proof at an instance level. If active it would uncheck the “Add custom message” radio button at each additional round of proof. They can reselect it and add a new message if it is needed.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.