Build better products with our product team
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.
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?
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?
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.
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 current build without completely deleting it from the interface. (possibly access by right clicking on the action?) Add ability to move/copy actions between rulesIn the same way it is useful to be able to copy between properties, it would be useful to be able to move/copy actions between rules within a property. (possibly access by right clicking on the action?) Add 'save and continue' to unsaved changes warningWhen you navigate away from something without saving first you get a warning but it doesn't give you the option to save! Add 'go to property' option when copying to another propertyWhen copying to a property, it is logical that you would want to go to the property you have copied stuff to. At the moment there is no shortcut to get there. Compare revision from within Edit Library (under publishing)When reviewing a library (e.g. before publishing) you typically what to compare revisions. It would be good to be able to do this within the library screen rather that have to navigate out to Data element/rules. Auto associate library with environment when rejectingWhen a library is rejected back to a previous stage there is no environment automatically associated with the library. If there is only one environment at that stage and no other library is using the environment it would be a time saver if it auto associated the environment. Retrieve library back to previous stage once submittedIf you submit a library to across to a stage that you do not have permissions for, you cannot get it back. e.g. accidental approval ready for publishing by a tester cannot be retrieved by the tester, you have to find someone with publishing permissions to reject the library. It would make sense to me that if you have permission to push a library to a particular state you should be able to retrieve the library from that particular state. Remove comments during minificationAlthough custom code seems to get minified, comments do not appear to be removed from the code which seems odd. Can't search within long sections of custom code Where a JS library has to be put in by cuting and pasting custom code you can end up with large blocks of custom code. It is not possible to search this custom code due to the way Adobe incrementally loads this code as you scroll to view it. This can make it difficult to manage. Default to more items on the rules list and elements listThe default is 10, I'm regularly selecting 100. Could you default to a larger number or remember the users selection? Add ability to alert when a library is published (e.g. via email, SMS/Text)From a security point of view we would like to be able to have alerts sent out whenever a library is published. The publisher should not be able to block the alert or amend the distribution list.
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 the last name on our end in CRM (e.g., "Kumar (deactivated)". Unfortunately, the first and last name in CRM are locked and synced from Active Directory… we cannot change them in CRM directly.
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.
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK