Skip to main content

Filter by idea status

10000+ Ideas

Allow Custom Fields on Program Period CostsNew

While being able to list out individual Program cost line items is a useful feature, it's limited by a few things: namely, the ability to only parse certain types of budget information based on information in the note. I would like to build a more robust approach for budget measurement and compliance in Marketo by providing a standardized set of custom fields that could provide more detail in budget analysis. While I would expect to have some of these as fully custom, I think others are widely applicable and may make sense to be in the core product. Some examples of these would include: - Spend Type: Categorizes the primary expense of the campaign (e.g., 'Media Spend', 'Agency Fees', 'Content Creation', 'Sponsorship'). This allows for a more granular analysis of where the budget is going and the ROI on different types of spend.- Budget Source / Team: Tracks which team's budget is funding the campaign (e.g., 'Corporate Marketing', 'Product Marketing', 'Field Marketing'). This is essential for leaders to see how different teams are performing with their allocated spend. - Vendor / Payee: A field to specify the vendor who will receive the payment (e.g., 'Google', 'LinkedIn', 'Gartner', 'Acme Agency'). This allows you to run reports on your total spend by vendor across all campaigns, which is invaluable for negotiating contracts. - Invoice / PO Number: A text field to record the associated invoice or Purchase Order number for the expense. This creates a direct link between your marketing plan and the financial transaction records, making audits and expense verification straightforward. Implementing these sorts of additional fields would turn Program Costs from a legacy piece of information to one that's more central to Marketo setup and ROI; please consider expanding out the feature in this way or with similar functionality.

MarlaDrLevel 4

Timesheet Profile Updates - Add option to select 'None'New

Description -We have users who do not need to log time based on their job level. For those users, we didn't apply a timesheet profile. Now we have some users were who logging time but due to recent job role changes are now not required to log time. I went to change their timesheet profile to remove it and with the new UI updates, it does not allow me to do so. It only always you to choose another timesheet profile. How would you like the feature to work - I would like the ability to completely remove or clear a timesheet profile from a user’s profile in the UI. Ideally, there should be an option to select “none” or leave the field blank, so that no timesheet is generated for those users who do not need to log time. Current Behaviour -Currently, the new UI does not allow clearing or removing a timesheet profile from a user’s profile. Instead, it requires assigning a different profile, with no option to set it to “none.” Support has confirmed this is a known limitation affecting multiple customers. They provided a workaround below, but it is more time-consuming and less efficient. Allowing administrators to remove timesheet profiles directly in the UI would simplify the process and improve usability. From Support: Best workaround here would be to create a “No Timesheet Required” profile to act as a replacement for these users. You could do this by creating a dummy timesheet profile (e.g., “No Timesheet Required”) with settings that do not generate timesheets or have no approvers/hours types. Then assign this profile to users who should not log time. You will then want to update your “no logged time” reports to exclude users assigned to this profile.

LyleSt1New Participant

Enable support for modern package managers (Yarn or PNPM) in the Frontend Deployment Pipeline of Cloud ManagerInvestigating

Request for Feature Enhancement (RFE) Summary: lease enable support for modern package managers in the Frontend Deployment Pipeline. Currently the pipeline only supports NPM, which although widely adopted is also generally known as the slowest solution for package management within the nodejs ecosystem. Consider support for yarn or pnpm, both of which outperform NPM from a CI/CD perspective. Use-case: We currently use Yarn on Managed Services to deploy full stack code. However, when migrating to Cloud Services and wanting to take advantage of the Front End (FED) pipeline, NPM is assumed and only the version can be altered via pipeline variables. We use Yarn as it has additional features and builds/deploys faster than NPM. Similarly, pnmp and Yarn PnP deploy about twice as fast as npm in our benchmark tests. Current/Experienced Behavior: Customers must use NPM and package-lock.json as the deployment package manager Improved/Expected Behavior: Customers can customize the FED deployment pipline to usee the package manager of their choice. This could be either an explicit selection, a pipeline variable, or the pipeline could lockfile detection (npm uses package-lock.json, yarn uses yarn.lock, pnpm uses pnpm-lock.yaml) Environment Details (AEM version/service pack, any other specifics if applicable): This request is for AEM Cloud Service, current version. Customer-name/Organization name: Toyota Motors North America (TMNA) Screenshot (if applicable)     Code package (if applicable):