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!
Currently in Setup -> Project Preferences -> Projects -> Custom Quarters, I am only able to specify 8 quarters. I would like the amount of quarters to be unlimited. Our instance has over 5 years of data, and if we do any trend reporting further back than 2 years, it shows "no value" for the quarter which is undesirable. We do have a custom calculated field for quarter, but it isn't perfect.
Description - Ability to create multiple versions of an interactive proof at one timeWhy is this feature important to you - timesaver for setup and proofing.How would you like the feature to work - we have a week’s worth of site homepages to proof. We’d like to set them up as versions 1 through 7 in one proof – 7 links – and have the proofers be able to flip from v1 through v7 to proof/comment on them all at once.Current Behaviour - set up 7 different proofs to the same workflows, proofers review 7 individual proofs.
Description - Ability to add a 'learn more' hyperlink to annotations that can take the user to a company-owned space.Why is this feature important to you - For release annotations, we could link to release details. For anomalies we could link to triage notes, etc.How would you like the feature to work - Link to a company-owned url outside of Adobe Analytics.Current Behavior - Does not exist
Description - Can we please add a search function to the "Reports" and "Dashboards" page? Currently I keep having to export them to then search in Excel. In addition to this, the user experience for moving Reports and Dashboards in to the folders is very painful.Why is this feature important to you - it is very inefficient, i keep creating a new report that i didn't need to, because another one that met the needs existed but i wasn't able to search properly, i can't find it. Also, the user experience for organizing and moving the reports/dashboards into folders, really sucks. I can't ever get the report to move into the folder, i have WAY too many to sort through to do this one at a time, especially when it seems like you have to click in one exact spot to be able to move those.How would you like the feature to work - put a magnifying glass/search section, like you have everywhere else. Current Behaviour - really poor user experience. I have to export then open the excel file to sort/filter/search and then go back to workfront.
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.
Description - We would like to have the ability to recalculate timeline when in a project MilestoneWhy is this feature important to you - this would save time on large projects. Often, we work in the milestone since WF is slow on big projects. It saves us time adding project tasks at a milestone level. How would you like the feature to work - add the recalculate timeline to the three dots on the milestoneCurrent Behaviour - it is time consuming since we add new tasks, predecessors and dates under the milestone, and everything sits for a long time in gray. We need to get the new dates, so we have to exit the milestone and recalculate timeline from the three dots at project level.
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.
Description - Currently, you cannot change the dates of tasks within the Workload balancer, although there are tiles that can be moved from person to person.Why is this feature important to you - When a user is doing the activity of workload balancing, there are frequently times where lack of capacity forces work to change Start or End date. Being able to do that within the same exercise and assigning work to people would save so much time, reduce risk of incorrect input, and improve user experience/adoption.How would you like the feature to work - We would like for the bars tied to a task to be movable across the date columns.Current Behaviour - Currently bars can move up and down from person to person, but they cannot move left to right from day to day.
We finally got the planned dates to "stick" so now the calendar is usable (for me!) and not dependent on when people mark their tasks done. However, not being able to export or print the calendar is still a problem so I can't use it as my single point of truth. We need to be able to print in order to take notes and distribute more widely. I'm very bummed about this turn of events.
Description -Why is this feature important to you -Customer asked for it. How would you like the feature to work -Ability to report on active vs inactive session. Active session is where user was engaged with the website/app and inactive session is when user left the browser or app open and was not engaging with the web/app. Current Behaviour -Not available.
Description -Why is this feature important to you -The customer asked for it and useful while downloading reports in PDF format How would you like the feature to work -The ability to switch on labels in the charts which will display Data labels for each. Current Behavior - by default its hidden, one has to hover over it to see the data label
Ability to customize the table of content displayed in the public link. Currently it takes every panel/visualization names which makes it cluttered specially when the audience is usually executive. Please allow to edit this with-in CJA.
The new Update Variable action in the AEP Web SDK extension would be a lot more helpful if you could start with an existing XDM data element and update that, rather than having to start with an empty XDM object every time.In the scenario where you’ve got a lot of fields that you want to set on every event (e.g. domain, customer id, whatever), I’d want to start with an XDM object that’s already got all those fields populated, and then update that. Likewise, if I've got a lot of ecommerce events, I would want to start with an XDM object where the basic productListItems array is already defined, and then just update that with the relevant additional fields for the particular event (product view, basket add, etc)Currently, you have to start with an empty object in every rule, so you end up repeating a lot of work if you have rules that share a lot of fields.Another, perhaps better, option would be if you could just do the equivalent of the Merge Objects data element in rules. For example, if I've got some default 'global' fields that I want to set in every event, and I've got some standard ecommerce fields that are set on all ecommerce events, a simpler workflow would be:Create an XDM data element that contains all my global dimensions.Create an XDM data element that contains all my standard ecommerce fields.In my 'cart add' rule:Start with the 'global' XDM data elementMerge it with the 'ecommerce' data elementUpdate it with a few fields that are specific to the cart add (e.g. carts adds metric)Then I could just duplicate this rule for all my ecommerce events, and just tweak the final 'update' action depending on if its a product view, cart remove, etc. This would be much cleaner than the current situation where you eitherHave one XDM data element per rule, where you're repeatedly setting the same 'global' and 'ecommerce' XDM fields.Have layers of 'merge object' data elements, where you build up the object before putting it in the rule (e.g. global + ecommerce + cart add)Use the Update Variable action where, again, you're repeatedly setting the same XDM fields over different rules.
From time to time, we have one Fusion scenario call another Fusion scenario in order to centralize things like authentication token management. (An example of this is when we call NetSuite, where NetSuite requires a specialized token process that isn't supported out of the box by Fusion's credentials mechanism.) Adobe PS recommended we put the token generation/retrieval process be put in its own scenario, and then call that scenario in whichever scenarios we'll be doing further business logic (such as calling NetSuite for some specific API calls using that token gathered before).The issue we're finding is that Fusion sometimes returns an "Accepted" response rather than the intended webhook JSON. Basically, it looks like Fusion webhooks are not guaranteed to execute when called but may be queued under some loading conditions. Retrying isn't necessarily guaranteed to fix this, either.What's really needed is the ability to execute that dependent/child scenario _within_ the runtime of the parent scenario. That is, we should be able to avoid the "Accepted" error if we can directly execute a second Fusion scenario rather than having to call it via a webhook.So the ask is for some kind of Fusion module or other implementation to allow for temporarily suspending the current scenario, calling a specified scenario (and passing in appropriate parameters), having that second scenario return a response, and then start executing the original scenario using the response returned as a data point.
We are currently facing an issue with field name changes in our CRM. When we rename fields in Microsoft Dynamics (MSD), these changes do not reflect in Marketo, affecting our ability to use these fields in smart list filters. We have learned from support that field names are locked during integration and cannot be edited. However, due to our process requirements, we need the ability to change field names in the CRM and have these changes flow smoothly to Marketo.This functionality is crucial for our operations and should be considered a fundamental feature of the tool. We kindly request that this be implemented for our instance as soon as possible to avoid any operational confusion and ensure seamless integration.
Description - Create native fields that roll up all of the project's planned hours and actual hours into program level fields. Similar to how project's have native fields that total all of task's planned and actual hours. Why is this feature important to you - We budget/allocate hours at the PROGRAM (Campaign) level then there are several projects within those campaigns. We need to report at the PROGRAM (Campaign) level our budgeted hours (planned by mangement) vs. planned hours (entered into projects by the PMs) vs. Actual Hours How would you like the feature to work - Workfront create two new native fields: Program Planned Hours (sum of all project's planned hours for the projects that fall inside the program) and Program Actual Hours (sum of all project's actual hours logged for the projects that fall inside the program). Then these native fields can be easily used on program level reporting. Current Behaviour - Can only pull PROJECT level reports and group by Program to get total planned and actual hours. But because the Budgeted Hours (custom field, not native) are at the Program level this doesn't help. There is no way to have a program level report that shows program's budgeted hours vs. planned hours. vs. actual hours.
Description - Allow blank entry for drop down list fields.Why is this feature important to you - Currently, when you select a value and save, you are not able to change it back to blank. The only way around this is to delete the task and create a new one. How would you like the feature to work - Allow list values to contain a blank or space value.Current Behaviour - List values do not allow for blank or space values.
Hi Team,I want to give some idea regarding form notifications. If any user edit the forms a particular permission will be there that one will receive notification from Marketo directly whichever form gets edited.This will help users to identify the changes in forms and also they will keep an eye if any critical issue may occur on live.I would like to suggest this idea to Marketo support and implement in Marketo. Please let me know if this can be a good idea to implement.
When we add multiple email addresses in the send alert flow step it sends an alert email to the first email address and cc's all the others. Can we please have an option to control the recipients and CC list through this flow step?However, you can use multiple flow steps to send the Alert to the recipient but imagine if there are 10+ recipients and you have to add an equivalent count of flow steps to send the same Alert.
Description - Please change the CJA icon back to the black logo so it's easy to differentiate between CJA / AA Why is this feature important to you - When migrating, validating, etc., the old black CJA logo made it very easy to know which analytics tool was open in a specific tab. The new logos are identical so it's very easy to get the two mixed up. How would you like the feature to work - CJA has a distinct logo from AA making it easy to know the difference Current Behaviour - Both logos are the same which causes confusion.
Description -I want to create a web hook from a given page to an Adobe Analytics dashboard triggered from a browser's Console entry. Basically, an entry that would be something like 'See this web page's traffic volumes here: https://experience.adobe.com/#/@mycompany/so:somecode/analytics/spa/#/workspace/edit/aaaaaaabbbbbbbbbcccccc?PAGE_URL=www.mysite.com/some/page' We would define a dashboard with a Segment of a dimension 'page url'. I would need that segment to - instead of having a statically defined value - read the value from the PAGE_URL query string. The dimensions and metrics would prefill based on the segments filter value, making it evergreen for any page that a user loads it from. The segment filter currently only accepts static values and what i'm asking for seems pretty unique. The url concept could also be usable to generate bulk reporting emails by tokenizing the assembly of a static value (the Workspace destination) with a dynamic token (the URL). Why is this feature important to you -Automation at scale with a lower lift than using the API to automate the static (re)definition of trivial data points. How would you like the feature to work - Current Behavior -Segment builder takes statically defined text only. I'd have to rebuild the Workspace for every URL I own.
Description - We want to be able to export info from fusion, specifically the scenario history tab.Why is this feature important to you - We want to use this info to calculate time saved via fusion automations.How would you like the feature to work - There would be an "export" button that would let you export the history into an excel sheet, similarly to other reports in Workfront.Current Behaviour - No reporting options exist.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
