Product Communities

Request for Feature Enhancement (RFE) Summary: The Search and Replace feature only allows writers to search and replace content in the author mode. However, this does not resolve use cases where XML tags must be replaced across multiple files.  Use-case: The writer needs to replace a product name, which is in plain text, with a <keyword>.  Current/Experienced Behavior: Search and Replace only works in author mode.  Improved/Expected Behavior: Search and Replace can work in either author mode or source mode.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Broadcom Inc.  Screenshot (if applicable):   Code package (if applicable):  

The LaunchPoint LinkedIn Lead Gen Forms integration by default adds new persons to the default partition. I'd like a way to map new persons to a partition other than the default partition by using a hidden form field in the LinkedIn Lead Gen Form.

This is so minor it may as well be trivial, but would also be (presumably) a small fix: could the MIME type Marketo serves for icon files (.ico) be updated so it uses image/x-icon? Right now, icon files are served as text/plain, which recently contributed to some confusion when someone loaded the icon directly from the URL.   This, of course, does not affect in-browser renderings of favicons, etc., so this is an edge case.

Allow wildcards to be used in templates for fields like Project Sponsor. For example this could allow a template to automate setting the user who submitted the Request as the project sponsor.

In the New Experience, long reports are now placed into a container and long reports have a scroll bar for users to scroll to see the full report. Provide option to users to allow long reports to fully show on a dashboard.

We use custom columns to break down data into monthly columns using smart lists. Today, there is a cap of 10 custom columns, which makes it not possible to create a year long report broken down my month. I suggest increasing the limit to 12 to accommodate that (seemingly common) use case.    I would also suggest that the end user could rename the custom columns. Using the unique naming of Database Smart Lists can allow you to be creative and kind of show the title you'd like, but if you use a Marketing Activities Smart List as a Custom Column, it displays the entire program file path down to the smart list. Editing the name of a column would be a welcome improvement in making Marketo reports even more usable. 

Would like the ability to add in multiple URL links at the Project Details tab. Have added to our custom forms but that information is not front and center when needed quickly. Have tried adding links into the Updates tab and they get lost in the comments. Having the option to add in more than one URL at the Project Details tab would be very helpful. Thank you!

I know we can move reports to the private folder to hide them from others, but I think it would be nice to have the ability to run a nondestructive or view only style report. Similar to SFDC, you would be able to edit an existing report by changing anything you'd like without altering the original saved version of the report.   Maybe something as simple as the ability to create report drafts. Maybe for reports in the Analytics section, there is a "Save Changes" button instead of auto-save for previously saved reports. It would just be helpful to eliminate the need to create several reports with minute changes just so you can access each version quickly without ruining the original. 

On the Updates page, when you select the Edit Custom Forms link (not on the Details page), it would be great if you could re-size/move the form window that pops up, as needed.Some text wraps, making it difficult to read. Ideally being able to re-size the window would re-flow wrapped text.I've also had instances where I'm updating the form based on one of the updates and it would be helpful to move the pop-up just a bit left or right so I can see the details in that update.

For the love of god can you increase the size of the drop-down window for templates when converting a request to a project? Instead of having to use the scrollbar it would be a lot easier if it was just a bigger window.

It would be of great benefit to our business users if the below enhancements could be implemented for Milestone view reporting:1. Can we freeze the project name column in the Milestone view of reporting, so that when we scroll to the right to view all the project milestones, we don't loose the information of which project we are looking at?2. When we hover on any milestone task in project milestone view, we are seeing projected dates. When we click on Planned dates, the dates on milestones are not updated to show planned dates. Can this issue be fixed?3. Is there a way a we don’t show red color for those milestone tasks that are completed? Can we show red color for tasks that are in progress and late?Can we have the ability to customize color coding based on tasks status and Percent complete?4. If any task is late, can we have a quick view of all the subtasks that are late?5. When we click on any milestone task, can we navigate to “Subtasks” in a task instead of “Updates”?6. Can we

Many of our Users are primarily proof reviewers. They typically just click into proof from the link in the email notification. They rarely have the full context of the project which could be gathered by reading through the Proof Details. It would be a great idea to make this information easily available in the Proof Info panel, either via a link or just as text that can be passed through. You could even make it permission based, so only certain users have access to it.

Where a task has existing hours added to a billed billing record, it would be useful to see a warning appear if the Revenue Type field is later changed from User Hourly to Not Billable.

Ability to add a table to a report with headers and the ability to add new lines as needed. Currently, we have to fake a table, creating a set of fields as Line 1, then another set of UNIQUE fields as Line 2, etc. This is incredibly messy, isn't expandable, and doesn't allow for any reporting (e.g. Line 1 Field 1 is completely unique vs. Line 2 Field 1.) ALTERNATIVELY The ability to attach the same form more than once, using the same fields each time.

Introduce an easy way to mark workfront objects without creating dedicated custom forms/fields by using labels. Good example: Labels in gMail. This gives users an easy way to organize their data without much overhead.

Hi. I'm a regular user of Advanced Search. I find it very frustrating in the New Experience because it is no longer a persistent screen of its own. It's now more of a popup on top of other screens, and the problem is that it disappears on you when you do something like editing a view. e.g. I spend quite a while setting up a complex set of filters to find the data I'm interested in, and then I realise that I need to add a field to the view. I do that, click Save and then BAM! The search results disappear and I'm back at the screen underneath it. Now I have to click on Advanced Search again, and put in all the filters again to find the results I was looking at. Can you please fix this to improve the user experience. Thank you.

We are unable to see and unable to track changes to the Duration field in the task updates. Other similar fields, such as Planned Completion Date, can be tracked so this functionality should be easy to add. Please add this field to the Update Feeds so we can track changes.Our task owners and Project Managers make frequent changes to Duration in our implementation and these changes are invisible on the task record. Once this is feature is available, we can track these changes, along with others, in a Journal Entry report.Thank you.

Description - It would be very helpful to create experiences natively in Visual Experience Composer for Target admins, save it back to AEM when necessary in a similar fashion to how AEM Asset Link works within the native Creative Cloud user interface. Why is this feature important to you - It allows Target users to embrace more features and functionalities of AEM without needing to leave the Target Visual Experience Composer.How would you like the feature to work - Natively within Visual Experience Composer; users should be able to access available Assets, make renditions of Assets within Visual Experience Composer, including Experience Fragments, and save any changes made within the session back down to AEM. Current Behaviour -

Since Proof can recognize text one of my editors thought it would be great if you could turn on spellcheck in there. Usually, they download and look at spellcheck in Word but it would save that extra step and might be possible.

My company has billing period that lies outside of a Calendar month, therefore we are unable to use the standard date prompts (e.g this month) to get the information we need. I have created custom prompts to get around this but it would save a lot of time if I only had to create them once and have them held in a library, rather than manually recreating on every report relating to revenue.I'm sure this would be very valuable to other companies that have their own anomalies

Queue details, specifically Queue topics, to be able to be referenced in custom form display logic. This allows a single custom form to be used for each request queue project. For each project, depending on the requestor's queue topic selection, display logic would populate form details applicable to only the selected queue topic.

We can now set the "Work on It" button to be a "start" button, but it only seems to apply to tasks involving a team. It would be even better if we could set this as a global standard. Otherwise it can be confusing that tasks behave one way if only users are assigned, but behaves differently if there is a team in the assignment.

Users are confused by the 'Not Done Yet' phrasing on the button next to assignments in Workfront. They are confusing that button with status. It would be more clear if this button read with something like "I'm not finished".

The current default "new form" experience is pre-populated with fields which have an "unset" or "empty" value for the Label Width and Field Width inputs (below, top). When the form renders in the Preview Draft mode, the label and field are both modified with an inline width style (100px and 150px respectively) although the input is empty by default (below, bottom).       I'd at least expect the default values for the Label Width (100px) and Field Width (150px) to be preset to the values that populate by default so that there's some clue as to the relationship between the input and the output. Given that the input is empty, it'd be great to extend/refactor the script to consider an "empty" value as a way of not setting an inline width [attribute] on an element (which generally these days is preferred for responsive design).  Better yet would be to remove the "px" appended to the value in the input (Label/Field Width) so that "400" outputs "400px" and rath

The current default setting for the Root Block Elements in Email is set to "<p>" and Landing Pages is set to "<div>". This is problematic for folks that are new to Marketo and didn't elect for, or aren't aware of, this setting. 1) It behaves like a "ghost in the machine" whenever a user uses the Rich Text Editor to modify an editable area which can produce unexpected results based on how an email is coded to handle this.   2) <p> elements in email display different from browser to browser and are not an industry standard root block element (<div> would be much better even). This is a functional issue that can "break" email layouts.3) It assumes that content is going to be some kind of text in Email using the <p> element which is problematic for non-text elements inside an editable area -- while assuming that content is going to be some kind of block in Landing Pages using the <div> element which is problematic for text element editable area