Build better products with our product team
I think this has already been submitted somewhere, but it would be great to have a feature where you can join branches of a scenario (router paths) back to the main scenario. For example, I have a form with a multi-select dropdown for brands; the selected brand determines who owns the issues, then other people are notified based on other form fields - those additional users are universal, but we need to create new issues for each brand. Some issues will only have one brand selected, some will have multiple that require duplicate issues to be created with different owners. It would be great to be able to check if multiple brands are selected, and if so iterate through the brands, creating new issues for each in a branch (if only one brand is selected, continue with the main scenario), then have that branch rejoin the main scenario and iterate through the issues to set the rest of the “universal” users based on the shared fields.
Description - We can duplicate modules in Fusion. It's frustrating that we cannot do the same with filters. Why is this feature important to you - We all know what it's like when you're working on a Scenario and then you realize you need a filter to be on the other side of a module. Unfortunately, there isn't a way to move this like a module. Instead, you have to rebuild it. And, depending upon the complexity of the filter, it can be a pain. (I'm encountering this right now.) How would you like the feature to work - Just like you can clone a module, you should be able to copy/paste a filter. Current Behaviour - It doesn't do that and it's extremely annoying.
Attached/below. Keen to hear counterpoints and other considerations for use.
I believe I have seen this in another thread somewhere and wanted to check on it to see if there have been any updates around this feature but can't seem to find it.. This would be a HUGE win for us if this functionality was possible. Description - Ability to utilize the same 'multi-choice' field on multiple custom form hiding certain choices. Why is this feature important to you - We use the same "Asset Type" dropdown field across all of our different custom forms so that we can easily report on this data, however not all Asset Types should be an available option across all forms. For example: How would you like the feature to work - Example: On Custom Form 1 we would like the 'Asset Types' dropdown to include Print, Email, Social, Web as options to choose from. On Custom Form 2 we would like to hide Web as an Asset Type for them to choose, and only display Print, Email, Social. Current Behaviour - Currently (to my knowledge), you cannot hide any options without it hiding on ALL custom forms. We have to create workarounds on each form where (ex.) Web is chosen as an Asset Type on Custom Form 2, we populate descriptive text that says "Sorry this is not an available option, please de-select this choice". However, this is not always a successful method because the form still allows you to Submit, so if a requestor purposely ignores it, or selects multiple Asset Types in which they may miss the message and continue with the form- it causes more work and aggravation on the team to have to reach out and let them know they cannot request that in which we receive a "well why is it an option then?" response 🙂 We are trying to avoid creating multiple versions of the same field so that we can pull clean reporting.
Currently, Workspace allows us to export reports in PDF and CSV formats. We would like to know if it would be possible to also add Excel (.xlsx) as an export option, as we are experiencing several issues when working with CSV files:- We work with program and video titles that contain commas. When exporting the report as a CSV and opening it to process the data, these titles are split into multiple columns, making the data difficult to work with.- For time-based metrics, the CSV export converts the values into seconds, causing us to lose the time format (hh) and preventing us from working with the data correctly.We would also like this enhancement to apply not only to report exports, but also to the scheduled delivery of reports in Excel format through both Workspace and Data Warehouse.Thank you in advance.
Indonesia is becoming a preferred destination for businesses focused on sustainability, renewable energy, and waste management. With increasing government support for green investments and environmental initiatives, entrepreneurs are exploring Indonesia company formation to establish circular economy ventures. Whether you plan to open a company in Indonesia for recycling, eco-friendly manufacturing, or renewable energy, understanding the registration process is essential for legal compliance and business growth.Why Choose Indonesia for Sustainable Business?When you choose company registration in Indonesia it's offers a large consumer market, abundant natural resources, and a strategic location in Southeast Asia. The government actively promotes investments in sustainable industries through supportive policies and incentives. Businesses engaged in recycling, green technology, ESG consulting, and renewable energy can benefit from a favorable investment climate and expanding market demand.Company Registration in IndonesiaForeign investors generally establish a PT PMA (Foreign-Owned Limited Liability Company) to conduct commercial activities. This business structure allows foreign ownership while providing limited liability protection and access to Indonesia's growing economy.The registration process typically includes selecting business activities, reserving a company name, preparing incorporation documents, obtaining government approval, registering for taxation, and securing operational licenses. Depending on the business sector, additional environmental permits may also be required.Documents Required to Register a Company in IndonesiaTo register a company in Indonesia, investors generally need:Passport copies of shareholders and directors Registered office address Articles of Association Business activity details Investment information Corporate documents (if a corporate shareholder is involved)Accurate documentation helps ensure a smooth incorporation process and compliance with Indonesian regulations.Indonesia Company RegistryThe Indonesia company registry maintains official records of incorporated businesses. Registration provides legal recognition, enables companies to open corporate bank accounts, sign commercial contracts, and operate legally within Indonesia. Keeping company information updated is essential for maintaining compliance with corporate regulations.Online Company Registration in IndonesiaThe government has simplified the incorporation process through digital platforms, making Online Company Registration in Indonesia faster and more efficient. Online applications reduce paperwork, improve transparency, and allow businesses to track registration progress electronically. Professional guidance can further streamline the process and minimize delays.Benefits of Sustainability Company RegistrationBusinesses operating in Indonesia's circular economy can enjoy several advantages, including access to a growing green market, government incentives, improved investor confidence, and opportunities to collaborate with local and international partners. Industries such as renewable energy, plastic recycling, waste management, sustainable agriculture, and eco-friendly manufacturing continue to attract significant investment.ConclusionIndonesia's commitment to environmental sustainability and economic growth makes it an excellent destination for green businesses. Entrepreneurs seeking Company Registration in Indonesia can establish a strong presence by choosing the right business structure, meeting regulatory requirements, and leveraging available incentives. Whether your goal is Indonesia company formation, to open a company in Indonesia, or complete Online Company Registration in Indonesia, proper planning and professional assistance can help your sustainability business succeed in one of Asia's fastest-growing economies.
You govern everything that moves through AEM. Every image has metadata. Every template has an owner. Every asset runs an approval before it ships. That's the whole point of managing your content and assets in one place instead of scattered drives. So here's an uncomfortable question: can you prove that every font rendering across your web properties, and sitting embedded in your asset library, is actually licensed for the way you're using it, and on-brand? For most enterprises, the honest answer is no. And that gap is quietly two problems at once: a legal exposure and a brand problem. The blind spot at scaleA DAM is built to govern assets. Fonts are a strange asset class, though, because they usually aren't a file in your library; they're a dependency living inside other files. They arrive embedded in PSDs and PDFs, baked into agency deliverables, uploaded inside templates, riding along in third-party creative. They slip governance precisely because nobody catalogs a dependency. Multiply that across thousands of assets, hundreds of published pages, and dozens of internal contributors and outside agencies, and no one can answer the basic question: what typefaces are we actually using, and are we allowed to? The DAM knows everything about the files. It knows almost nothing about the type inside them. Why this is a real risk, not a theoretical oneTwo things go wrong here, and both stay invisible until someone finally looks.Licensing. Font licenses are real, they're specific, and they're enforced. Desktop, web, and app rights are typically sold separately. A face a designer licensed for their desktop is not automatically cleared for webfont delivery on your site or embedding in an app. At enterprise scale, across many properties and real traffic, unlicensed use isn't a rounding error. It's exposure, and foundries do pursue it. The teams most at risk are usually the ones most confident they're fine, because "the design team handles that" is not the same as documented, delivery-appropriate rights. Brand drift. Without a single source of truth, type quietly wanders. One page ships with the wrong weight. A landing page falls back to Arial because the webfont didn't load. An agency subs a "close enough" face nobody signed off on. Each instance is tiny. Together they erode the brand you spend real budget enforcing everywhere else and unlike a broken image, off-brand type rarely trips an alarm. Where AI actually changes thisFor years this was simply unmanageable. Auditing every typeface across a large asset estate was manual, tedious, and never anyone's priority so it didn't happen. That's the part that's changed.Identify. Font-identification models can now look at a rendered asset — an image, a PDF, a live page, and tell you which typeface it is, then cross-reference against what you're actually licensed to use and flag the gaps. This is the problem I work on at Lipi.ai: turning "we have no real idea what's in our library" into an actual inventory, and surfacing unlicensed use before legal does. An audit that used to be a quarter-long project becomes something you can run continuously.Generate. Half the reason contributors grab random fonts is that getting an on-brand, properly licensed one is slow. AI generation collapses that: produce a bespoke, brand-owned typeface, full character set, consistent across every glyph, licensed to you so the sanctioned option is also the easy one. When the right font is the path of least resistance, drift drops on its own.Govern. The real win is putting both inside the pipeline you already run. AEM is where assets are managed, approved, and published so a font and licensing check belongs in that same approval flow, not in a once-a-year scramble before a rebrand or an audit. Governance that lives in the workflow is governance that actually holds. A practical font-governance checklistIf you want to close the gap, this is where to start:Inventory what's actually in use across both stored assets and live pages, not just the fonts folder someone maintains on the side. Map each face to its license and confirm you hold the right rights for how it's deployed (desktop vs. web vs. app). Define sanctioned brand fonts and make them the default in templates, so the on-brand choice is the effortless one. Add a font and licensing check to your asset approval workflow, catch problems at ingest, not at audit. Re-scan on a cadence. New assets, new campaigns, and new agencies introduce drift continuously; a one-time cleanup goes stale fast. The bottom lineYou already treat images, copy, and templates as governed assets, with owners, metadata, and rights. Type has been the one quietly getting a pass, because until recently there was no practical way to govern it at scale.That excuse is gone. You can finally know exactly what type you're using across your properties and prove you're allowed to use it. The enterprises that get ahead of this won't just avoid a foundry's letter; they'll ship a more consistent brand, faster, with one less blind spot in the system they've already built to keep everything else in line.Aditya Thakur is the founder of Lipi.ai, a font intelligence platform for identifying, generating, and licensing type at scale.
Request for Feature Enhancement (RFE) Summary: Support for Amazon Linux 2023(Linux kernel6.x). Use-case: Use as the OS for new servers. Since Amazon Linux2 is reaching EOL, I want to use a new standard OS. Current/Experienced Behavior: AEM 6.5 supports kernels up to 5.x. https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en#server-operating-systems Improved/Expected Behavior: AEM 6.5 supports kernel 6.x including Amazon Linux 2023. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Query Preformance and QueryBuilder to be available to customers on AEM as a Cloud Service Publish tier Use-case: Currently the Query performance tool /libs/granite/operations/content/diagnosistools/queryPerformance.htmland Query debugger /libs/cq/search/content/querydebug.htmlare not available to customers on AEM as Cloud Service even from the Developer ConsoleThis is useful when customer wants to perform a query on publisher for troubleshooting purposes or if they want to validate something. This is useful for Assets Implementation Projects using Publish tier as well. Current/Experienced Behavior: Not available to customers on AEM as Cloud Service even from the Developer Console. Improved/Expected Behavior: Make it available to customers on AEM as Cloud Service even from the Developer Console. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service , AEM Assets as Cloud Service Customer-name/Organization name: N/A - This is a general feature enhancement request Screenshot (if applicable): Code package (if applicable):
The older version of the API, 1.4, allowed us to download a JSON of the processing rules in a suite. Since these are instrumental in transforming data into eVars, Props, and Events, they are an essential part of maintaining the data quality of a suite. The newest version of the API, 2.0, does not currently support accessing the processing rules, and it's been stated on Github that, as of this idea submission, processing rules access is not even on the roadmap. Unless Adobe is going to eliminate these rules (and the eVars and Props that are driven by them), a mature multi-site installation of Adobe Analytics, esp. across mobile and web, relies on a constant overview of processing rules for maintenance, QA, and to aid site and mobile app developers.Please make sure that processing rules are accessible via the APIs, not just in version 2.0, but in all future versions. Leaving 1.4 up is not a complete solution, as Adobe may deprecate it at any point.
I've been experimenting with different ways to reduce repetitive operational work, and I'm curious about other people's experiences with AI agents.Our team still jumps between project tools, email, spreadsheets, and chat just to keep work moving. Even after trying a few automation tools (and recently looking at platforms like WorksBuddy), I keep wondering whether AI agents actually reduce the workload or simply create another layer to monitor.For those who've used AI agents for things like updating project status, managing follow-ups, summarizing meetings, or syncing information across different tools—has it genuinely saved time?Where have you seen the biggest impact? And where do AI agents still struggle enough that you'd rather handle the work yourself?I'm especially interested in real-world experiences rather than feature lists. Has anyone found a workflow where AI feels like a reliable teammate instead of another tool that needs constant supervision?
Description -Why is this feature important to you -Basic formatting (e.g. Bold, Italics, Underline, Superscript, Subscript) to assist with interacting with and responding to commenters How would you like the feature to work - Include the formatting in the commentsCurrent Behaviour - There is no formatting (e.g.Bold, Italics, Underline, Superscript, Subscript) in the proof commenting
Hi there,It would be great if Marketo introduce a feature to add the custom meta data to the Marketing Assets so that it can be leveraged for the 3rd party integration meetings.Thanks!
Currently, collections on Content Hub can only be shared with people who also have log-in credentials for the portal. This doesn’t cover all business cases in day to day work, though.You want to be able to make CH collections public for anyone with the link as well.Why? Here are some examples:Agencies with short-term contracts don’t need accounts to access a specific subset of assets for a project. Sales or Product Management can share a collection of product data assets with a customer who can download directly A link to a collection with corporate assets can be shared on the intranet for everyone to access, even people who don’t usually use CH A Marketing colleague can share a collection of campaign assets with Sales regardless of their ability to log into CH or notThere should be an option to make collections public, which is linked to admin rights. Not everyone should be able to make any collection public for everyone with the link, but admins at least should be able to do it.
DescriptionI wish there were a more comprehensive panel for Engageable Profiles in Adobe Experience Platform. Why is this feature important to youPrimarily, it would provide organizations with a deeper understanding of profile usage.Recently, our organization faced an issue that resulted in nearly one million profiles becoming engageable due to an error. Identifying the root cause required us to use Query Service to identify the journey, then open the journey to determine the associated audience, and finally analyze the audience to understand how those profiles were ingested.This investigation process was very time-consuming. Having an out-of-the-box monitoring capability for Engageable Profiles would significantly simplify troubleshooting and usage analysis. Important monitoring could include:New engageable profiles by day Which journeys are triggering new profile engagement, allowing users to display a sample of the newly engaged profiles Which namespaces are being used by those journeys The number of profiles that have not been engaged in any journey for the last 9, 10, or 11 months, helping organizations anticipate profiles that may soon be removed from their licensed usage due to inactivityPlease note that the main focus here is on the delta, not simply the total number of engageable profiles currently available. The existing usage panel already provides the current total. The goal is to provide deeper insights into how many profiles are being engaged for the first time and what is driving that growth. How would you like the feature to work?A similar experience to the Customer Journey Analytics usage panel would be ideal. CJA provides a very detailed view, showing which connections and datasets are responsible for usage. In AEP, I would like to see which journeys, audiences, and namespaces are contributing to increases in Engageable Profile usage. Current behaviorThe current License Usage panel in AEP only displays the total number of Engageable Profiles measured against the licensed amount, broken down by sandbox
Description - When using the My Tasks widget, would like the ability to see completed tasks. Why is this feature important to you - My creative team like seeing completed tasks so they can quickly jump back to things if needed from this page.How would you like the feature to work - Allow this widget to pull in completed tasks from a preset Workfront filter or a custom filterCurrent Behavior - Currently does not display completed tasks as seen in the compare and contrast example below. Trying to use a filter that pulls in tasks from last week, this week and next week that are both not complete and complete, the widget does not seem to pull in completed tasks. My Tasks with custom filter: A report with the same custom filter:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.