Build better products with our product team
Once an update is posted, we currently don't have the ability to go back and amend anything in that update and resave. This feature would be really handy to avoid any spelling errors, typos, incorrect mentions etc.
Description - We are using the profile API to enhance a users profile with a CDP solution. Currently when we generate a token (In Adobe Target), which is then inserted into the CDP solution, it needs to be regenerated and replaced every 90 days in order for the functionality to continue undisturbed. Why is this feature important to you - The implications of someone not remembering to do this very manual task is large and in an age where personalisation is at the front of most strategies surely this is a small enhancement that would be deemed necessary for implementation in order to minimise risk for customers How would you like the feature to work - Where Profile tokens are being generated for implementation purposes it would be great to have the ability to choose the timeframe you want the token to expire (i.e. 6,12,24 months) or make it possible to set it as never Current Behaviour - Currently the profile API token expires after 90days, a new token must be generated and replace the old one.
Request: Improve the documentation currently available under https://support.workfront.com/hc/en-us/articles/217196767-Understanding-Calculated-Data-Expressions. Informations at the level of e.g. - Are CASES zero-based? - Is DIV an integer divide? The current situation requires a lot of try-and-error till the expression is working like expected.
Description - Before the upgrade to the Adobe Admin Console, we could create users via the API. It now creates them in a pending approval state and we have to manually approve them. Why is this feature important to you - This is causing a bottleneck in quickly on-boarding users to Workfront.How would you like the feature to work - I'd like it to work as it did before :), or allow an option to be set to pre-approve the users. Or even a separate API call to approve the user.Current Behaviour - Account is created, but requires manual approval, once approved the account is made in the Adobe Admin Console.
Description: While the new Data Warehouse UI is a much-welcomed step, I think it is missing some features that would make it more user friendly and efficient.These would be: 1. Add calculated metrics.2. Add custom date ranges.3. Add segments to individual dimensions. This is a Workspace staple, it is so necessary.4. Ability to edit/delete created accounts and locations. People make mistakes.5. Requesting an account name, description and hostname seems unnecessary.6. Ability to save notification emails.7. The "Save request" button unshaded seems weird and is unhelpful as you navigate the tabs. A Next button until the last tab (Notification email) would be more helpful. Why is this feature important to you1. Calculated metrics is an integral part of Adobe Analytics, and the success of content/campaigns cannot be fully measured without it.2. Custom date ranges. In addition to previous point, several campaigns and timeframes don't align with a standard calendar measurement (for example, since product launch).3. Segments to individual dimensions. While we can do an overall segment, adding segments to individual dimensions within DW would save an enormous amount of time during data analysis. It is a staple of Workspace already.4. Edit/Delete created accounts and locations. People make mistakes but also server information and credentials becomes outdated. Leaving the incorrect information there may lead to mistakes and isn't efficient.5. account name, description and hostname seems unnecessary. This is just repetitive and counter-intuitive. It should be a name and server information. The name can be the description.6. Save notification emails. Every other repetitive task has been eliminated but this one has been left on.7. A Next button until the last tab (Notification email) would be more helpful. Given how counter-intuitive the Save button currently is (and the fact that there needs to be information in each of the tabs) a next button until the last tab follows standard web UI more closely.How would you like the feature to work1. Calculated metrics. Make it available the same way it is now in Analysis Workspace.2. Custom date ranges. Make it available the same way it is now in Analysis Workspace.3. Segments to individual dimensions. Drag and drop from the segments bucket. Make it available the same way it is now in Analysis Workspace.4. Edit/Delete created accounts and locations. Add a delete and an edit button.5. account name, description and hostname seems unnecessary. Remove description6. Save notification emails. Add a plus sign (same UI as create accounts and locations)7. A Next button until the last tab. Remove Save and add next instead. Add save to the last tab (Notification emails) Thanks to @jennifer_dungan I wasn't able to reply to your comment in the questions part.
When creating a custom object in Marketo, 3 fields are automatically created: Marketo GUID, Created At and Updated At. These fields are not available in the contraints when using a filter to which this new custom object is linked. These could be extremely useful if you are planning on using these to track custom activities in CRM so you can leverage the "before" or "after" in your date ranges based on the Created or Updated at values.
Description -One feature of the Segment Builder is the ability to use existing segments when building out a new segment. I'll refer to this as a "reference segment".Once the reference segment is dragged into the Segment Builder it becomes "disconnected", and is more like a snapshot of what the reference segment looked like at the time. If an update is made to the reference segment this will not be reflected in any other segments that use it. It would be nice to have an option to "anchor" the reference segment so that any updates made to it are also reflected in other segments. This would preclude the Adobe Analytics user from having to find and update every segment that used the reference segment, and would ensure that changes to the reference segment are immediately reflected across all reports. This feature can be limited to only public segments. There are several risks associated with this idea.Uers may not be aware of how many segments use a particular reference segment as an "anchor", and thus may not truly understand the ripple effect caused by an update. Users would have to be provided with some sort of notification in the Segment Builder that shows both that a segment is being used as an "anchor" (think of a little icon next to the segment name) and which segments are using it as anchor. This option should require permission rights from an adminA change to the reference segment may break the segment logic of other segments, making them no longer work. This could happen if the container types in the reference segment were adjusted. One way to alleviate this would be to disallow the use of anchor segments in some cases, such as in sequential segments. Another option would be to not allow the anchor segment to update in a segment if the segment logic will be broken. The user would then have to be notified of the segments where this occurred so that he or she can make necessary adjustmentsWhy is this feature important to you -My organization often uses several core segments for KPIs, and then creates more nuanced segments based off of these core segments. The number of segments that use the core segments are substantial, meaning that a small change made to a core segment requires updating a large multiple of other segments with the same small change. How would you like the feature to work -When a reference segment is dragged into a new segment in the Segment Builder, a user can click on the gear option and select "Anchor Segment". Any updates made to this reference segment will automatically update this segment as wellThe Segment Builder page for the reference segment should indicate whether the segment is being used as an "Anchor Segments". This can be done using an icon or some similar call outThe Segment Builder page for the reference segment should contain some sort of interface for showing which segments use this segment as an "Anchor Segment"A warning should appear when someone tries to update an "Anchor Segment", telling the user that updates to this segment will impact other segmentsCurrent Behaviour -Dragging an existing segment ("reference segment") into the Segment Builder creates a copy of the existing segment. The reference segment component of the new segment will not update if the reference segment is updated.
Existing Option: When am trying to scroll down for adding the location when my browser option is 100%, am not able to see scroll bar options below. (Refer the image attached below.) Every time, I have to reduce my web browser size to 80% and then select the options further. Additional Option:So, I would like to add the point as to optimize the page in a way that even when I see it in 150% zoomed option it has to get modified according to that.
Description - Add View Option to Group Members and Subgroup Members ListWhy is this feature important to you - Allow to see details about the users within the group similar to every other user list within the UI of Workfront.How would you like the feature to work - Same as all other Filter, View, Groupings setup in WorkfrontCurrent Behaviour - The Filter and Grouping option is present the View option is not. @kaliape @ewanh @moniqueevans
Once a status update is posted on a task, there are often slight edits to the update that are needed to communicate the update appropriately. Having the ability for the person that posted teh update to edit the post would be extrememly useful and save us tons of time. Currently employees are copying the update and then posting a new one, then deleting the old.
Description - Need a way to stop a running scenario from outside of the scenario itself. Why is this feature important to you - If a scenario is running on a schedule and I need it to stop, I have no way of doing so. If I open the scenario while it is already running, it is hit or miss as to whether or not it will even display a Stop button. Even if it does display the Stop button, it never works. I have literally a 0% success rate of that button ever having stopped a scenario under these conditions. Additionally, if I have started a Scenario by clicking the Run Once button and the scenario decides to freeze up in my browser (this happens a lot and is becoming more and more frequent), then there is no way to stop it. I have to wait the full 45 mins for it to time out before I can continue working on it because the stop button won't work after the freeze up and if I refresh the page, I just get a view of the diagram, not the progress of the current cycle and I run into the same situation where it is hit or miss as to whether or not the Stop button will appear and even if it does, it won't actually work. How would you like the feature to work - When viewing the list of scenarios in Fusion, there should be a Stop button for each scenario that is accessible without actually opening the scenario. Similar to the toggle switch that controls whether it runs on a schedule or not. If/when it changes to a Force Stop button, that button should truly function as a force stop, literally killing the process running that scenario immediately without regard to anything it is doing at the time. Current Behaviour - there is no button like I am describing.
Description -Why is this feature important to you - We are looking to inform our reporting system to fetch the latest 360 view of the customer as soon as the profile changes. However, due to the limitation of platform notification , we currently have to do a workaroundHow would you like the feature to work - Data ingestion platform notification should be triggered as soon as something changes on a profile, irrespective of whether the evaluation method is batch or streamingCurrent Behaviour - Data ingestion platform notification is only triggered when profile data changes via batch ingestion , however when data changes via streaming ingestion the notification is not triggered.
Description -In order to see all the Setup menu options below Expense Types (e.g. all the System setup items), you need to be able to scroll vertically. How would you like the feature to work -I would like the scroll bar that is visible at 90% and 80% (and lower %) to be visible at 100% zoom. (note: that scroll bar used to be there, just a few months ago - not sure when it went away)Current Behaviour -There is no vertical scroll bar on the Workfront Setup menu when you have your browser set to 100% zoom. It is visible in lower zoom %.
Description - The Microsoft Teams Plugin does not have the option to like an update. It is also missing a "see it in workfront" button. Why is this feature important to you - We utilize like to acknowledge a message was read but does not need a response. Without the feature, I am forced to open the object in Workfront, search for the update (comment) and then click like. It adds extra clicks and time. How would you like the feature to work - Ideally there would be a button next to "reply" called "like" similar to the features within Workfront itself. If that's not possible I would like to see a "see it in Workfront" button similar to the link within email notifications Current Behaviour - Click the link to the object. Go to the browser, navigate to the updates tab, scroll down to find the specific update (sometimes I have to use "edit > find", and click the like button.
Description -Why is this feature important to you - save timeHow would you like the feature to work - the user who creates a task to be assigned to it automaticallyCurrent Behaviour - manually assign tasks to users
Description - automate the process for "convert to task", so that when an user raises an issue in the queue it automatically becomes a tasks on the corresponding project as they select the client, instead of having the user to manually convert from issue to task.Why is this feature important to you - work efficientlyHow would you like the feature to work - automate the process for "convert to task"Current Behaviour - Manually convert the issue to task
Description - In Workfront, we should have ability to view all the templates associated to a project as this creates problem while understanding which template could have impacted tasks/ finances and lot other things for a project.Why is this feature important to you - The data reflected on a project we are not able to understand the reason for it as we do not have idea as to what template was attached.How would you like the feature to work - In project overview section, under templates section it should display all the templates attached.Current Behaviour - Currently the project only reflects the first template attached and not its subsequent templates.
Programs currently display a simple 'Around __ people are blocked from emails' message. It would be really helpful if Marketo could distinguish between leads that had unsubscribed versus those that are blocked for other reasons (e.g. invalid email addresses), particularly with operational emails that ignore subscription status.
We can currently reference a number of object types in typeahead custom fields, but not issues. I would like to be able to create a Typeahead custom field that references the Issue object please.
Description: Would like Admins to have the ability of adding a custom message when making changes or sharing things in Workfront that produce automatic notifications. Why is this feature important to you: The notifications are vague and can confuse a user as to what was changed, shared, why it was done, and what they need to do, if anything. The ability to have a clarifying message would remove the confusion and the user would know right away what the purpose is and what they need to do. How would you like the feature to work: The admin would check a box or indicate somehow that a message should be included when doing the update, change, or sharing. The admin would type the clarifying message and the notification would be sent to the user. Current Behavior: Users get notifications and then have to reach out asking why they got it and if they need to do anything. We end up notifying the audience BEFORE the official WF notification goes out that they may get an email notification. In other words, we have to send a notification about a notification, specially if the audience is leadership. 🙂@hollyse @rudyha1 @suzyf @annapu
Description - Would like the abilty to order Work List by Task Priority.Why is this feature important to you - Our production team has difficulty knowing which tasks are higher priority when they begin working for the day. Right now, they have to click the task details in order to see the Task Priority level. It would be a much better workflow for them to be able to sort the list by task priority level.How would you like the feature to work - It would be added as an option in the sort (see screen shots attached).Current Behaviour - Only sort options available are by Planned Completion, Planned Start, Commit date, Project, and My Priority
As an Admin I want to be able to enable/disable certain email notifications for several users at once without affecting the rest of their notification settings they choose.
We don't have any activity log or any smart list, where we can find out the list of deleted records. It is something like if we connect third party tool via API it will automatically delete the record from Marketo but without API we can't able to get this data that which person was getting deleted via API. I would like to suggest to implement to get the list of records deleted from Marketo database, it can be any smart list or any activity log that we would easy to find out the data and the source of deletion.
Description - We need the ability to work within and make our Workspace projects more aesthetically aligned and not have to worry about one component being slightly taller than another. In other words, I should be able to cleanly size one component, especially one that has empty space in it, to be the same size as another one right next to it that DOES contain data. Why is this feature important to you - This feature allows for easy alignment of data that is alike and easily segregates other pieces of data that are not the same. It allows for proper line of sight and does not distract the data viewer when attempting to inform data storytelling. How would you like the feature to work - I would prefer that I could simply click and drag on the border of a component and size it to the same height or width of its neighboring component and it would remain exactly the same size or height as that component next to it without snapping to a different size higher or lower. Current Behavior - Currently, if I resize a component, it snaps to a size it prefers, whether it matches the neighboring component, leaving other components out of alignment and completely ruining both the line of sight and the aesthetic.
We need to disable open and click tracking to comply with regulations in certain countries (such as Germany and Austria), but that currently has to be done for each email (open tracking) and each individual link within the email (link tracking). We would ideally be able to track or not track an open/click based on the country where that person resides, or if we have been given permission to track that by the user.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
