Build better products with our product team
The process for resolving Marketo-Dynamics sync issues takes way too much time. First, we have to rely on indirect means to even spot when a sync issue is occurring. They never show up in the Notifications area! Our trick is to look for a Boolean field that triggers a Dynamics workflow and fails to reset to false as a sign that we have sync problems. Once we identify the problem, we open a ticket with Marketo and it inevitably gets escalated to the tier 3 team, and sometimes even engineering has to get involved to provide log files with the necessary clues/details on the root cause. This can easily go on for weeks before we get the necessary eyes on the problem, and we’re trying to run a business in the meantime. If Marketo would give admin users access to these error logs that tier 3/engineering have access to, and a real-time notifications feature (the existing Notifications area would be fine), then the users could troubleshoot on their own. It would be win-win. Dynamics customers would greatly reduce resolution times and we would reduce the demand on the small team of Marketo’s tier 3 and engineering experts who have to work hand in hand with us today to resolve these issues.
Right now we have bulk exports for leads, activities, and custom objects, but nothing for company objects. Please give us a company bulk export just as there is a lead bulk export.
When adding a new project status, the new status appears by default at the bottom of the status list.This is also the default order as it appears to the end-user.The current workaround involves updating the order for each group, rather than an option to order at the master level (i.e. change default order for all groups).Our instance has 800+ groups, and we cannot re-order the status list one by one.There should be an option to order at a master level or at least set the order when you create a new status.
When using Visual Experience Composer it would be be incredibly helpful to add an "Insert Before" or "Insert After" function when a specific container is selected.Currently when a container is selected and you choose to edit the HTML, any changes that are made are made within the container that is selected, which can cause some ordering or styling issues if you want to add an additional element before or after the container that is selected.The work around for this is at present to "Expand Selection" and edit the HTML of the parent container, however this often involves updating the HTML for the main body container. If you edit the code for the main body container this will lock it's content, so any subsequent changes made outside of Target (i.e. through the CMS) won't show correctly which can create problems. Adding an "Insert Before" or "Insert After" option would allow us to quickly insert new elements into the page above or below current items without having to lock the code of the entire body.I am happy to expand on this if the above does not make sense.
Regular email notifications about upcoming maintenance windows and releases that will impact a user's ability to access Adobe Target. This will allow Target users to prepare for such outages.
Would like the ability to create JSON offers via the target API
Request for Feature Enhancement (RFE) Summary: Within Adobe Assets, we would like to request the ability to view and annotate on all pages of mulitpage files like PDFs, Word Docs, Excel Spreadsheets, PowerPoint Presentations and more. Currently, when a multipage document is added to a review task and/or workflow, and the user clicks "Payload" they can only see the first page of the document/PDF/Excel, etc. for annotation. We have tried to use the Sub-assets functionality, but it doesn't meet our business needs. Use-case: A user is attempting to review and annotate a PDF or other document/file with multiple pages. In AEM Assets, the user can only view and annotate on the first page of the asset. Current/Experienced Behavior: A user is notified that they have a review task in their inbox. They navigate to their inbox and open the task and click "Payload". A PDF file is opened in the viewer in Adobe Assets, and the user can only see and annotate the first page. The user has to download the PDF, annotate or comment in Adobe PDF Reader, and re-upload as a new version of the asset. Improved/Expected Behavior: A user is notified that they have a review task in their inbox. They navigate to their inbox and open the task and click "Payload". A PDF file is opened in the viewer in Adobe Assets, and the user can move from page 1 which is the first page displayed, to the second, third and higher pages, on which they can make annotations and comments, and complete the workflow task. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP9 Customer-name/Organization name: 3M Screenshot (if applicable): Code package (if applicable):
The current Workfront functionality intermixes Project level updates with those made on included tasks and issues. It includes even more breadth of topics at the Program level.This causes updates to the project or program record itself to be hidden in the noise.Please create an ability to filter down to just those updates for the object itself (none of its children/sub-items). This should be able to be toggled on/off by the user - similar to the system updates.
We are in desperate need of a "like" button in Workfront Proof. We had this button in our previous system and it is the one thing ALL reviewers/approvers keep asking to bring back, especially our Leadership team.Reviewers leave comments in a proof but the decision to act upon the comment, or not, is dependent upon cross functional business partners as well as our VP's approval. When these folks are in a proof, if they agree with the requested change they click LIKE. That is the green light for the designers to move forward with the update.We've tried using the resolve button however that is used for other situations and it got way too confusing. I fear leadership will will start to challenge if WF is the right system for us. It may seem small and insignificant to many out there but it is essential to our process.
Request for Feature Enhancement (RFE) Summary: Hi Adobe team, Opening up an enhancement request to have the capabilities of flushing dispatcher cache for non-prod pipelines, similar to the production pipelines. This will greatly help us automate our build process. Use-case: Flushing dispatcher cache with client libs and content after some dev and qa builds Current/Experienced Behavior: Non prod pipeline does not have the capability to flush dispatcher cache like the prod pipeline Improved/Expected Behavior: Non prod pipeline have the capability to flush dispatcher cache, just like the prod pipeline (with the same UI options ideally) Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager with AMS AEM Customer-name/Organization name: TD / Accenture Screenshot (if applicable): Code package (if applicable):
The issue we're trying to solve for is that users in the new experience under requests can select a request under the Name Column and leave comments/upload files there. Because those comments/files don't appear in the converted project they can get lost causing confusion/project delays. We'd like to be able to separate Requests from Converted Projects or allow us to manage the view on the request page to remove the Name Column.
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