Product ideas | Community
Skip to main content

Ideas

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.

Tlovie
TlovieLevel 3

Scenario Planner enhancementsNew

Description:The Scenario planner feels like a forgotten function of the tool. It’s very convenient for quickly getting projects added to Workfront as initiatives and moving them around, but it falls short in how it can be made more useful during project roadmap planning.  The function would need to include:Project-to-project dependencies The ability to tie the start date of an initiative to the end date of another. This would be great for regular projects as well versus having to associate tasks within them.Custom form editingThe ability to associate custom form data at the initiative level that would carry over after publishing.Project summary view within the scenario plannerIf an initiative is tied to a project, you can more easily see the project details without leaving the page.  More initiative dates optionsThe ability to sync resync my initiative dates with project dates.More specific dates - monthly increments can be too broad  Reveal the Scenario Planner’s initiative rank as a valueCurrently this isn’t reportable like the portfolio optimizer rank, but it would help if it was.  Merge or better integrate with the workload balancerThe current hours/FTE tracking of the current Scenario function is confusing and unusable. You can extend this same frustration with the disparate Calendar feature that is also useful in its own way, but disconnected from the way the rest of the tool functions. These features feel like they were designed for one company in mind, but don’t apply to everyone else. The use case that involves the scenario planner is:A marketing team of creatives begin to develop initiatives (project ideas) that align to the goals set by leadershipThe team adds these project ideas QUICKLY onto a roadmap view (Scenario Planner). They can move the initiatives around quickly and in correlation with actual projects. They can associate form data like objectives/goals, status, and relationship to other initiatives/projects with the initiatives in the planner.They can publish to create or update projects, but also sync project changes back to the initiatives in the planner.  

sai121New Member

Feature Request to improve Publication Behavior for Locked Live Copy PagesInvestigating

Request for Feature Enhancement (RFE) Summary: AEM sites Rollout and publication issue Use-case: When a editor rollout and publishes a master page, the publication process start publishing the live copies in random order and fails when it encounters any market page that is locked to a user. This results in inconsistencies leaving the page changes published to few random markets. Ideally this should have completely stopped or skip the locked page, deploy to rest and notify about skipped page. Current/Experienced Behavior: The rollout/publication does not follow a predictable sequence and succeed for markets until it encounters locked pages then silently fails making it difficult to track progress There is no summary or report indicating which locales were successfully published and which were skipped. This results in inconsistent rollout and makes it hard to identify which pages need manual intervention Improved   Before initiating rollout publication, the system should check for any live copy pages that are currently locked by users If any locked pages are detected, halt the entire replication process. Display a clear error message indicating which pages are locked and by whom. Environment Details (AEM version/service pack, any other specifics if applicable): AEM version - 6.5AEM service pack - 6.5.22 Customer-name/Organization name: British Airways(BA) Screenshot (if applicable):   Code package (if applicable):