Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Description - The current functionality for routing rules is very limited. We are only able to configure routing rules for specific queue topics. Allowing us to assign specific user/teams to a specific queue topic. The following is functionality that is possible through Fusion, but want to be available without Fusion: 1. Automatically Convert Requests/Issue into a Project If a request is submitted through a specific queue topic, then automatically convert the request into a project using a specific project template. Ideally, we would also have the ability to configure this at the custom form level. e.g. If the requester selects XYZ on the request form, then convert into a project using XYZ template. If the requester selects ABC on the request form, then convert into a project using ABC template. 2. Dynamic Request Routing Based on how the Form was CompletedSimilar to #1, allow us to set routing rules based on how the request form was completed. If c
Batch Campaigns can have the status “Scheduled to run”, and you can filter for this status. Thing is, that this is in fact not their current status. These campaigns ran a year ago, yet the status is not updated. Once you click on them, Marketo recognizes the current status and removes it from the filter.I consider this a bug, and I think the status of scheduled campaign should automatically be set to “Has run” after it has run.And on a side note: If you want to archive a program that has Smart Campaigns in it that are in the “Scheduled to run” status - even if that’s not true - you can’t archive. Marketo will display this error message:
To reduce the risk of accidental interruptions, we recommend moving the Schedule Sandbox Refresh button from the main Workfront page to the Setup menu.Keeping this action button on the main page makes it easy for users who are not involved in the refresh process to unintentionally cancel or modify a scheduled refresh, which could directly impact planned activities.Since refreshes are typically coordinated internally by the team before execution, placing this option under the Setup menu provides an additional layer of protection, ensuring that only authorized users performing configuration tasks can access it and significantly reducing the likelihood of accidental changes.
I would like there to be a global Workload Balancer setting that automatically hides ON HOLD or DEAD projects without applying status-based filter criteria or needing to update the project tasks so they don’t qualify. Similar to the how completed work can be removed from the Workload Balancer through the Show completed work setting, it would be ideal if there was a Show Dead or On Hold work setting that could be toggled off once in settings rather than having to add criteria [Project: Status -- Does not equal -- Dead, On Hold] to all Workload Balancer active project filters to exclude these projects. USE CASE: When an in-flight project is cancelled or put on hold, setting its status to DEAD or ON HOLD allows the Project Owner to freeze the project where it was in its progress without having to complete or clear the qualifying tasks to remove them from showing in the Workload Balancer. That way if the project happens to come back to life down the line, the remaining tasks are still set
The Adobe Analytics API 1.4 is scheduled for decommissioning this summer, yet critical endpoints from this legacy API have not been integrated into API 2.0. This creates a significant gap in functionality that will impact many organizations relying on programmatic management of Adobe Analytics configurations.Missing Critical Functionality:The most important missing feature is the ability to programmatically:Create new Adobe Analytics variables (props, eVars, events) Modify existing variable configurations Delete variables when no longer neededCurrently, API 2.0 forces users to manually manage these variables through the Adobe Analytics interface, which is:Time-consuming for bulk operations Error-prone for complex configurations Incompatible with automated deployment workflows Difficult to integrate with CI/CD pipelinesBusiness Impact:Without this functionality in API 2.0, organizations will lose the ability to:Automate variable management across multiple report suites Maintain consiste
The feature that automatically auto tags images in a document needs to be disabled for every user, or the tagging needs to be manual to eliminate obscene language from the tagging. I have an abstract image in my template that I send to clients. If I forget to disable the auto tagging, then the client will read a caption that suggests I am sending them a nude image. There is no figure in the graphic. There is no suggestion of a figure in the graphic, but Ai suggest that there is, and it confuses my clients. Even if it says that it is an “Ai generated caption”, my clients read it as something I, myself, inserted into their document. I have turned it off. I have done it multiple times, successfully. However, I do not love that it is my sole responsibility to work around a program every single time I send out a document. Please let me know if there is a way to disable this function so that I can forget about the fact it even exists. My clients are older and I have to explain to them ever
Problem StatementIn Workfront, users submit requests through the system and may need to coordinate with colleagues in other departments on the same request. Today, if a user wants another person to be engaged in the request conversation, the most common process is to wait until after the request is created and then manually add an @ mention in the Updates section.This creates friction and can lead to communication occurring outside the request context—especially when users choose an easier workaround.Current WorkaroundAfter creating the request, users go to the Updates area and @ tag the relevant person.However, many users find it easier to:open the email notification they received for the request, and forward that email to the teammate in the other department.As a result, communication is no longer centralized in Workfront, and the “single source of truth” for the request is reduced.Proposed EnhancementCreate a field type (or input capability) that allows users to @ tag/mention others
Description—It would be ideal if we could Upload and Host an Image to be used in our Custom Forms. Currently, we only have the option to add images by adding the URL of an image hosted somewhere else. The images/documents inside Workfront do not work, as they expire after a few minutes. Why is this feature important to you - This would make the feature easier to use, and located all in one place (Workfront) How would you like the feature to work? If I choose to add an Image in the Custom Form, it would be helpful if I had the option to Upload a File to be used. That file will stay in Workfront and be connected to that Custom Form. Any User with access to the Custom form would also have access to the file. Current Behaviour—Currently, there is no option to upload an Image. We can only enter a URL. Images and documents hosted in Workfront can be added as part of the URL, but because those URLs expire after a few minutes, they generate an Error or broken link and a bad expe
We use Apache CXF for SOAP and REST clients on AEM 6.5.2 LTS and install the necessary bundles in AEM. Currently we are forced to use Apache CXF 3.3.13, which was released in March 2022, because AEM still ships with org.apache.servicemix.specs.saaj-api-1.3, and newer versions of Apache CXF require saaj-api-1.4. There are a number of security vulnerabilities in Apache CXF that have since been patched since 2022 that we would like to remediate, see https://cxf.apache.org/security-advisories.html. Our goal would be to install Apache CXF 3.6.x, currently 3.6.10, as that is still actively supported, but the old SAAJ API is preventing us from doing that, see javax.xml.soap,version=[1.4,2) -- Cannot be resolved: Our ask is for AEM to upgrade to saaj-api-1.4, which would unblock us from upgrading Apache CXF.I can provide a full list of bundle JARs that we install related to Apache CXF if needed.
If you've ever launched a large-scale campaign and watched your call center buckle under a flood of responses — or worse, seen your email deliverability tank because ISPs flagged you for sending too much too fast — wave sending in Adobe Journey Optimizer (AJO) is the feature you need to know about.In this post, I'll walk through what wave sending is, when to use it, and how to configure it effectively for real-world scenarios.What Is Wave Sending?Wave sending lets you split a single campaign's audience into multiple batches (called "waves") and deliver them on a staggered schedule. Instead of blasting your entire audience at once, you control the pace — sending in 2 to 10 waves, each with its own size and timing.This applies to all outbound actions in AJO: Email, SMS, Push, and Direct Mail. Why Should You Care?Three words: control, reputation, and capacity.1. Protect Your Sender ReputationISPs watch your sending patterns closely. A sudden spike in volume from a domain or IP can trigger
Adding an Employee ID field to the user profile would be a valuable enhancement for organizations that rely on unique employee identifiers across multiple systems.In our environment, duplicate names are fairly common, making it difficult to distinguish between users. An Employee ID field would provide a reliable way to identify the correct person and improve data accuracy.This would be especially helpful in Fusion integrations that map Workfront user information to Salesforce, where we often need a unique identifier rather than a user name.It would also be great if the Employee ID field could be added as a selectable column in user views and reports, enabling administrators to easily reference and validate user records.I hope that you will consider this enhancement request.
Currently there is no API endpoint to get the Flow details of a campaign. This is also a blocker in MCP as well since the it works based on REST API. Complete Campaign QA cannot be completed without flow details.
I recently created an SDR within the AA workspace project. The thinking is that users should be encouraged to use the AA workspace tool as much as possible, as compared to generating an excel based SDR that has to be stored externally. Some examples of what I built 1) a picture of the different sections of the SDR - 2) a picture of the different panels, one for each variable (props illustrated) indicated its number, its name and whether or not the variable is enabled 3) an overview of a specific variable details. I get that there are some items in this example that might not be easy to automate, like the BRD reference number with a hyperlink, but I think it would be great to have a tool in the AA admin areas that would generate an SDR template within Workspace grabbing all the information it can from the AA admin area report suite traffic and conversion variable screens. UX: The admin would click a button, the script wo
It would be helpful to have the option to display the updates in order by the last update made. When reply is added to an older update, it is difficult to search for because the original post is displayed way down the update feed. When a reply is made to an older comment, it would be nice to have it move to the top, truly in order of last update, be it original or a response.
The new green pop-ups at the bottom of the screen when task status is modified, such as if you click work on it the pop-up says “You’ve started working on this. The status is now in progress.” or when you remove your assignment it says “You’ve stopped working on this, the status is now new” are persistent and must be manually dismissed by users even after navigating to other objects. While having the pop-up is helpful for confirmation, we need the ability to have those auto-dismiss after a few seconds or at least have it disappear when moving to a different object in Workfront.We have users who are moving quickly through the system who now feel disrupted by having to click another item to dismiss after already clicking to change the task. They often move on quickly until these pile up at the bottom of their screen, then have to dismiss each individually. Which a large volume of work as is, any extra clicks are cumbersome to users. Thank you so much!
Hi! for clients (even sometimes for us) is confusing to see this numbers in AJO journey canvas:It would be great if somewhere in node card mention which numbers corresponds to previous execution (for example, yesterday) and which ones to actual execution. Regards.
I recently started receiving incessant in-app notifications when a team to which I'm assigned receives a work request. They look like this: [Person] wants your team, [Team], to work on this task. Many members of our department are assigned to multiple teams, causing each of us to receive dozens of notifications per day--even per hour--for new assignments that rarely apply to us. I'm told there's no way to opt out of these in-app notifications. Please add a way to opt out of certain notification types--or at least turn these off again (as they have been since we started using Workfront a year and a half ago).
Just like we can delegate project/task/issue approvals, and with 22.3 can delegate task/issue assignments, PLEASE have the ability to delegate proof approvals! There are other ideas for this with 'Not Planned' labeled, hoping power in numbers can help sway this bc this is something WF really needs. Hoping it is part of near-future proof enhancements.
What is Context7?It's an open-source MCP server from Upstash that pulls current, version-specific docs and real code examples for a library straight into your AI assistant's context - instead of the model relying on whatever it memorized at training time.Where I use it:Inside Cursor and Claude Code, whenever I'm generating code against a fast-moving SDK — so the assistant reasons against today's API surface, not the one that existed at its training cutoff.Here's the real example:Asked Cursor to implement session caching with Upstash Redis — it generated hmset, which looked correct but was already deprecated.Added Context7 via MCP, and Cursor pulled the latest SDK docs and switched to the correct hset API.AI can write code. MCP helps it write code with current context.Key takeaways:AI assistants hallucinate silently on deprecated APIs — that's the dangerous kind Training-data cutoff is the biggest hidden risk in AI-assisted development MCP turns "probably right" into "verified against c
Description - Implementing the Analytics CNAME involves creating a subdomain for our website, which is then utilized to place cookies in a first-party context. However, during SEO crawling, these subdomains are scanned as well. To prevent Google from crawling these subdomains, we need to make adjustments to the robots.txt file located within it. Yet, as end users, we lack the capability to perform this task on our own and require assistance from Analytics Engineering to handle it on our behalf Why is this feature important to you -Search engines like Google allocate a crawl quota to domains, determining the time and resources dedicated to indexing a website. If these crawlers expend their resources on redundant URLs, like CNAME subdomains, there's a potential for vital content on our site to go unnoticed during indexing. This poses a risk of missing out on organic traffic if the crawlers neglect new or updated content while focusing on less crucial areas. How would you like t
We would like to submit an enhancement request for the Journey list UI in Adobe Journey Optimizer.At the moment, the available filters in the journey list do not provide enough granularity to efficiently manage and analyze journeys at scale. We would like to request two additional filters: A filter by schedule type, so journeys can be filtered by cadence such as daily, weekly, monthly, once, and similar scheduling options. A filter to identify which journeys are included in the active journeys metric, so users can easily distinguish journeys that count toward that metric from those that do not. This second filter is especially important because not all journeys with a Closed status continue to count toward the active journeys metric. It would be very helpful to have a clear way to see which journeys are still contributing to that count.Having these filters would make the Journey list much easier to use for reporting, operational monitoring, and cleanup tasks, and would improve visibi
Description: We would love to see additional fields directly visible on a card when looking at a board rather than clicking into each card. Why is this feature important to you: This could help with quicker prioritization, understanding capacity, and organizing the work within a board without as many clicks/steps. How would you like the feature to work: Unlock the Visible on Board option for custom fields for at least a few (understanding only so much fits on a card) like maybe having a space below the assignments/due date/status that allows for up to 2 or 3. Current Behaviour: Visiblity on card only functional for pre-built fields Thank you!
While I tried to filter users, I set the option EmployeeCode, and selected “Is Any Of” and pasted 1000 user employee codes, it broke the page. It should not be like that, if it cannot process the filter it should show a warning or say something instead of being unusable, even when reloading the browser did not work.
My team needs to see more information on cards within boards. Simple interface improvements would make a hugeeee difference! Improve colors (not just a little box) See planned hr/story points See status of tasks under that card
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
