Product Communities

We've had multiple instances where we've created complex projects in Workspace for the business, and then shared them to multiple Stakeholders, only to find one of them changes or deletes something and then hits Save rather than Save As affecting the project for everyone.At the moment the work around we have to use is to make a copy of the final project and share that, so we still have the original to revert to.If when sharing there was the option to say whether it was shared as read-only or read/write it would help with this issue. Stakeholders could still make amend but if they then wanted to Save those amend it would only allow them to Save As a new project.

It would be great to be able to display multiple dimensions per row much like in a Data Warehouse export. Even if this were to function like a breakdown and it's just a style option to display in tabular form. For example: Dimension 1    |    Breakdown Dimension    |    Metricelement1         |     element1                        |     10element1         |     element2                        |     9element1         |     element3                        |     8element2         |     element1                    &nbsp

A lot of our reviewers in proof our internal employees. It would be great to see resource planning available to those users whose sole work is based in approving files in the proofer. We need to be able to plan their work accordingly, but it's difficult to see what is being planned for their workload, as there is no ability to see into their planned work. In addition, we would love to see the actual time on those making decisions on proofs so we can improve our planning and resourcing for approvers.

This post has been closed as a duplicate. All votes have been moved to the original: Calendars -- Ability to show planned duration even after actual is entered We would like to have a calendar with our planned completion dates for the tasks captured, NOT the actual completion date (this is too late).

Our schedules that we use are set for the week to start on Monday and end on Sunday, but the Timesheets, Resource planner & Workload Balancer weekly view shows a different view (Sunday to Saturday). It would be great for these weekly views in the system to equal that the Schedule setup by the system Admin. Example: If the schedule is setup as Monday to Sunday, then all weekly views in the Timesheets, Resource planner & Workload Balancer would also display the week as Monday to Sunday . This would be a great help especially with resourcing.

Automated DLP to prevent entry sensitive or personally identifiable information for the Medical, Insurance, Financial, etc. industries and comply with relevant regulations.

While standard Marketo fields are already blocked from having API names that start with numbers in the UI, this restriction is not in place for Marketo Custom Objects. This causes knock-on issues with Velocity scripting being unable to reference the field. The ability to create fields starting with numbers should be blocked from the UI.

At current if you need to print a report from Workspace, you have a choice of PDF or CSV download. The PDF version is the best option that is looks like the workspace report but when you print this it will squeeze all freeforms into one page. There should be a functionality to fit to page, or zthe zoom level, or how many pages you would like to print to.Afterall, Site Cat already allows this so why wouldnt the workspace?

Today a user complained that his children tasks were appearing on a gantt export despite the parent task being collapsed. After researching this, I found that this is by design. The documentation states that: "Subtasks are included in the exported PDF even if the parent task is collapsed and the subtasks are not visible. To include only parent tasks, select the parent tasks you want to include and leave any subtasks unselected."Unfortunately, due to this design, if a user has a lot of parent tasks, each with more than 10 subtasks below it, then the user would have to uncheckmark a lot of tasks just to get the view they need. This much manual maintenance can easily lead to mistakes and rework.Additionally, while I understand that a filter can be created so that only parent tasks are displayed, there are cases where a user would want to leave some children tasks on the export.

When a card is minimized I cannot tell if the card is in a blocked state. So when we are doing standups we cannot see that this card is in trouble. The card has to be expanded to see it. When you have many cards on the board you need to keep them minimized. Can the Blocked status be displayed when the card is collapsed?

Workfront Proof / Security Considerations Our company works with high profile entertainment and consumer goods clients and we have strict security contracts in place regarding how we manage and distribute content. We would like to start using Workfront Proof with clients but are running into security conflicts. Has Workfront and Workfront Proof considered any of the below options for improved security and auditing?An unpaid external license that allows us to password protect a proof link. Currently, it is our understanding that this can only be done with a paid work license.Flexibility around mandatory log-ins at the client level (instead of system wide)? It would be great if we could make proof access log-ins mandatory for only specific clients. Based on our current WF instance I can only see how to make log-in mandatory system-wide. Are there any workarounds?Ability to remove the thumbnail image from showing on the proof email link. Access to "download" audit logs to show

In this reference link: https://docs.marketo.com/display/public/DOCS/Automatic+Trigger+Campaign+Cleanup, I have seen the sentence “These idle trigger Campaigns will be deactivated on dd-mm-yyyy DateTime” with reasons… so as per my understanding there is a log maintaining in Marketo for identify the campaign deactivated timestamp. so why can't we use in Marketo visual page? I think this will be useful right?

Sometimes in projects a task is no longer needed. However, you do need to complete those tasks in order for the project to automatically close. It would be nice if we did not have to complete them in order to close / complete a project. As this misrepresents a true depiction of what actually occurred with the project. Perhaps a recommendation could be a task status (no longer needed) or (decommissioned). The project should accurately depict whether or not a task has been completed, after a project has been closed. You should not have to complete them in order to close out a project

Our Project Management practice refers to Change, Issues, Decisions, Accomplishments and Risk as CIDAR. We have custom forms associated with the Workfront Issue Tab. We know we can change the name of the tab, however, Workfront controls the capitalization, only allowing the first letter to be capitalized, Cidar. Since we are using CIDAR as an acronym, it would be nice it all the letters could be capitalized.related Case Number 00207948

On our login screen, we've handcrafted a "For Workfront Support, contact..." with our sysadmin names & emails. It's part of our branding background image. It would be great if that was officially part of the login screen and could be edited from Setup.

In the setup area, there should be a way to opt out of "ads" that may pop up after login, or show up on the login screen.

Creating an overview page with more useful information such as:Change History (most recent Data Elements / Rules updated)Most recent Publish History (and by who)It would be much better than the youtube link. 

I'd like to recommend that the page showing the list of rules page is vastly improved.The main problems to be addressed are:- Currently limited to show only 10 rules at a time- No ability to filter by rule attributes such as event type (with priority) & extension type & conditions- No ability to sort by any of the key attributes of a rule such as event type (with priority), extension type & conditionsTo summarise, the ability to sort, filter and even just visually see the rules in place for a property is mostly limited to using the names of the rules. This means we have to try and enforce consistent rule naming conventions in order to meet these needs - which can be difficult to achieve when multiple staff are using the tool.

Currently Workfront Analytics only has one filter available. It would be great to have two or multiple filters available to be able to make comparisons. Such as: Actual Go Live verses Actual Project Completion or Planned Go Live verses Planned Project Completion

Marketo can report a high number of soft bounces in Smart Lists that go onto Open/Click emails and don't show in the Email Performance Report. The majority of these are returned with the reason '550 [internal] [oob] The message is an auto-reply/vacation mail.'Marketo currently interprets this return code as a soft bounce action and I would like to see this reclassified to not be marked as such. 

We've recently moved over to using Adobe Launch which was on the whole a very positive experience. However, there is always room for improvement and I've kept a list of all the little niggles that we came across in the first month which I've provided (in no particular order) here below... Adobe Analytics Set Variable action - Add conditionality to individual variablesThis form/interface seems a little clunky and unsophisticated.  I'm guessing this is because it was done this way for DTM backwards compatibility?  It would be good if this was re-thought.  In particular, I'd like the ability to add conditionality to the setting of individual variables to stop us having to fall back to custom code. Add ability to enable/disable actions within a ruleIt would be useful for trouble shooting to be able to quickly knock out actions to see what affect it has.  Also in the same way as disabling rules, it would be good to be able to remove something from the curr

There’s been a long-standing issue with the way Marketo sees CRM users (in both MS Dynamics and SFDC) in that it will display all users – active, inactive, deleted – as available users to sync leads to from within Marketo.  Many companies like us never delete user records - instead, we deactivate them in CRM.  For example, a contractor who transitions to an FTE which requires a new/different enterprise ID (and CRM user record).  For example, Arun has two records in CRM (one active, one deactivated).  Yet when we attempt to sync a lead to him, we see this:Since Marketo only shows first/last, there’s no way for us to identify the active record.  To make matters worse, just this week a new issue has surfaced where Marketo is throwing an error flag when trying to sync since it’s now using just the user's name as the unique identifier (even if we select the active record) - why Marketo doesn't use the user GUID makes no sense to me:One workaround would be to modify

I would like to request the ability to assign an assignee(s) while creating a new story. By default, it should assign the story to the person creating the story. The reason why this is important is because currently, a new story is not assigned to anyone after creation. This "loses" the story in the list of stories. By requiring an assignee to the story, even defaulting to the creator, it'll help avoid the situation of a new story getting buried in a large set of stories.

It is presently recommended to only use a 100% browser zoom setting due to possible inconsistent results. This idea is to allow other browser zoom settings to help those that may be disabled or have vision issues. Enhancing the zoom settings will also benefit those while traveling that have less screen area available for viewing. I

the Data Insertion API allows for passing IP Address. This allows for companies to develop middlelayer services to communicate between client and Adobe. The Media Collection API does not allow for passing IP address as a payload value.This causes [Regions, Cities, Countries] dimensions to contain the location of the middlelayer (since the IP address of the middlelayer is used for geo location). It would be great if this inconsistency between the Media Collection API and the Data Insertion API was remedied