Build better products with our product team
We would like to see the ability to create billing records with $0 amounts / actual revenue for any R&D projects we complete.At the moment, it let's you override by using company billing rates, however, since user billing rates still apply when adding hours to billing records, this defeats the purpose, as it just takes the user billing rates anyways (even with a company billing rate override).
I would like to request that users have the option to select up to 18 months in the Workload Balancer. Currently the longest a user can go is 3 months, which doesn't give user enough insite into their workpipeline.
Build in a tab into WF that stated the average time for similar tasks and then asked the team member to confirm if that allocated time was accurate. We could possibly just have 2 radio buttons, one that indicated that the recommended time was accurate and one that allowed you to select "other" and input the actual time allocated.
When making an update on a project, it would be nice to have a box to check to "Notify Project Team", who would then all be cc'd on the update. By "Project Team", I mean all Personnel on a given project. This way you won't have to remember who all to tag. ALL who are on the "Project Team" would get the notification.
My company develops some very detailed PPT presentations to include in-depth speaker notes. We currently have to create PDFs in notes view of our PPT presentations in order to view and comment on the notes section. We would love to be able to proof those notes directly and avoid the extra steps.
Managers should not have to depend on Project Creators to "share" correctly. If they are left off of the project sharing, they do not have visibility to their direct reports task assignments (unless you do wonky workarounds like creating a report run with the access level of system administrator).Currently in Setup > Access Levels > you can set up rules for projects to automatically grant view access to the project creator's manager.Likewise for Task Access Levels, you should be able to set up a rule to automatically grant view access to the task assignee's manager.
When performing more advanced customizations of forms, it's not uncommon to deploy complex CSS to present Marketo's form styling differently. As an example, this screenshot shows a Marketo form field with three radio buttons with transformation: In order to maximize accessibility, only the text ( e.g., "PDF - Option for U.S. [...]") is stored as the display value for Marketo; the rest of the styling, including the unique imagery for each radio option, is performed via CSS. Therefore, I need to target the label elements for each option. By default, Marketo outputs a randomized ID to each radio and label, such as mktoRadio_39390_0. This does not relate back to the field name itself, though that is set is the input's name attribute. However, if a form is updated—even if the update does not touch any form fields, like with an HTML text area change—the randomized ID changes every time. This leaves the form designer with two options: Write supplemental JavaScript to assign a unique-but-consistent attribute to the radio buttons' labels Update CSS selectors every time a form is updated Neither of these are ideal. Because the field name is already being pulled for the name attribute, could the code output be updated to set IDs based on the field's API name? For example, if the input has name="billing_format", could the radio buttons' labels be named like "billing_format_0", "billing_format_1", etc.? This would provide a consistent selector for styling.
Reference - Case Number 00297963https://amazonaccounting.my.workfront.com/report/61bbc0e1004a4c432da4912d216478a0/detailThe above issue report is group by Project Name and provides a total of a custom field called "Total Annual Support" which is a custom calculated field. I would like to sort the report so that the project with the highest Total Annual Support value is at the top of the report.Currently, the only possible way I see is to run the report and manually click on the header name for "Total Annual Support" but the system sorts based on each individual issue value and not the total at the project grouping.It would be great if there was a switch to indicate whether to sort on the individual issue value or the group total value.Thanks,James
‚Hi, we need an hours/user report which shows General Time, the breakdown of hours against those items and the notes so that we can see how much time is lost on non-chargeable items and on what. Have spoken with your helpdesk and this isn't currently possible. I have to do this manually by logging into each user and reviewing their timesheet then manually add to a ppt template. Thx
A trigger event that occurs for the winning lead of the merge An example of where this is useful is that when 2 leads become merged there could be new webpage visits/anonymous activity on the winning lead activity record after the merge which means that we should recheck attribution campaigns to see if this person's first touch parameters should be updated I am sure there are more use cases for a trigger like this
We are getting daily notifications with "Marketo is unable to update the following records in Microsoft Dynamics." These are records that have recently been merged and are no longer active (deleted) in Marketo and Dynamics due to that reason. We receive this notification because updates must be in process. You can ignore these notifications as they do not cause sync issues. We would prefer that these notifications do not come in at all since the records no longer exist in both systems. Hence, no actions are needed in Marketo or CRM.
We want to give users permission to be able to import leads but we ONLY want these users to be able to import leads using “Skip new people and updates” List Import Mode ONLY. i.e. we don't want to give them permission to import leads using “Default” List Import Mode as we don't want them to be able to import new leads. Would be awesome if user Role permissions could be configured to do this
I'd like to have the ability to display a field based on what role, team, group a user is in.
We're managing a large implementation across several countries where we have limited contact with the users. We're not sure what our users are finding helpful (and equally importantly, what they're not using at all). It would be good if administrators could see which reports are being viewed. Not just total figures but the ability to see which users are accessing which reports would be useful as well, as we would contact the users of deprecated reports or such.
There are teams that are interested in seeing if there could be functionality to see when an approver has downloaded a document. This is important as it will allow document owners to see if the approvers/team members are taking action on the document.
Hi,In order to manage properly all risks in a project, it would be great to have custom forms/fields to have more information in risks menu.The vision is to combine the default fields with new one's, in a custom form, as occurs in issues and tasks. Is this possible?Also would be great to have the possibility to convert risks into other objects(tasks or issues)
Request for Feature Enhancement (RFE) Summary: "Build Form" should "stick" on the metadata schema editor page Use-case: To be able to create metadata schemas easier Current/Experienced Behavior: When we are creating metadata schemas that have a lot of fields, it is cumbersome to drag the field from the top of the page (since the "Build Form" scrolls with the page) and drag it again to the bottom of the page Improved/Expected Behavior: The "Build Form" should stick to the page and not scroll with the page so that it is within easy reach. The "Build Form" interface then should have a separate "scroll" from the page, to scroll through the field types. We also think it would be better to have it in the left side of the screen and collapsible so that it does not intrude as much in building the metadata schema. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Default option values when creating dropdown options in the metadata schema editor Use-case: To be able to create metadata schemas faster especially when creating dropdowns with a lot of options Current/Experienced Behavior: When creating dropdown options, we need to enter manually both "Option text" and "Option value" Improved/Expected Behavior: When creating dropdown options, as a default for the "Option value", it should have the same value as the value inputted in "Option text" Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Ability to copy fields in the metadata schema editor Use-case: When creating a metadata schema that involves similar fields, it will be a lot easier if there was a copy function for the fields Current/Experienced Behavior: No copy function for metadata fields. We need to define similar rule settings over and over again for several metadata fields Improved/Expected Behavior: Ability to copy fields so that rule settings, field type, and field options (if applicable) will be copied as well. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Ability to re-arrange options in the dropdown fields in the metadata schema editor Use-case: Easier to maintain dropdowns in metadata schemas Current/Experienced Behavior: Currently, the metadata schema editor does not allow the re-arrangement of the dropdown options. For us to change the order of the options, we need to delete and create the options again according to our preferred dropdown option arrangement. Improved/Expected Behavior: Ability to drag and drop the dropdown options according to our wanted display from first to the last dropdown option Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description When using Analysis Workspace, one key workflow of my users is the creation of Segments from filtered Freeform tables. While we can use the super efficient workflow of right-clicking a selection of items from a table, we can't do the same with the summary row of a table:However, being able to create Segments from those rows would be highly useful. Filters and breakdowns defined for those rows could automatically be used for the segment definition. In the screenshot above, right-clicking the Page row would produce a Segment like HIT(Page exists) as there is no filter used on that row. On the Entry Page row, which is a breakdown and has an advanced filter for contains "category" and "2", the Segment could be HIT(Page equals "articles" AND (Entry Page contains "category" AND Entry Page contains "2")).This simple workflow would make it much quicker to build segments like this and free users from the tedious validation required after Segments have been built.Why is this feature important to youTo make it easier and faster to create more complex Segments.How would you like the feature to workAs described aboveCurrent BehaviorToo many left-clicks, not enough right-clicking.
Moving a task from one project to another is more cumbersome and time consuming in the new interface. In 'Classic' a user can search for the destination project using part of the project name and case sensitivity doesn't matter. In the new interface you must start at the first letter of the destination project name and correctly enter the full name (including upper/lower case) until you winnow down your results enough to see the destination project. This is one area of the new UI where the update is inferior to what it replaced.Please reconsider the Destination Project Search. Having it operate like it did in the Classic interface is much more user-friendly.
In Workspace, is there a way to turn off background and percentages at an account level? Every project I create I have to go into each column in every table and turn off these features. Would be great if I could do that once at a project level or even at an account level. Thanks.-Peter
The new Landing page layout is nice... but there's one thing I would add! In our Marketo instance, we have several workspaces and domain aliases setup. I never use the default domain for the work I do in my workspaces and need to change the domain every time I open a landing page. It would be nice to be able to pick the domain alias when previewing the landing page. It would be nice to have an option in the admin area to set the default LP domain alias for each workspace. At the moment, I'm using a javascript injected snippet to achieve a similar objective. A "Change Domain" drop-down allows me to pick the domain I want to use in one of the 4 workspaces I'm currently active in. Using the drop down, I can pick the domain alias to use and it updates the link so I can click to open it or so I can copy it to the clipboard. The drop down could contain a list of all alias domains or a sub-set configurable in the admin section for each workspace.
I would like to EXPORT OLD Programs to CLEAN / DELETE them out of our Marketo instance (to keep things 'tight & right') It is way too time consuming to UNHOOK everything and delete each asset / program manually. I have 4+ years of programs to delete -- across 10+ business units. And we have only three resources to run campaigns and manage the instance. Another thought is -- after 2 years of archiving -- Marketo automatically deletes assets/programs.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
