Attention all Fusion users! Do you have an idea for a Fusion template that you’d like to see added to our library? We’ll pick a few customer-submitted ideas and create them for you! While we’d love to, we can’t create all of them. Workfront to Workfront/Adobe automations will be prioritized, but don't let that stop you from sharing your idea. All ideas are welcome and we're excited to see what you come up with!
If you don’t already know, public Fusion templates are pre-built automations or integrations that Adobe creates for all customers to use. Read more about how they work and what templates are available.
Post your idea as a reply to this Discussion and feel free to up-like any other submitted ideas.
Hi @Lawson02 , We are looking at adding more guidance on much of this shortly in Experience League. Focusing our attention on pagination needs. Do you have any specific cases you feel would be useful to highlight either in that documentation OR via a template? Please tag me in your reply.
This would be great to help with iterations within the waterfall project lifecycle, which is a gap in functionality for some clients. Especially those that have strict compliance standards to follow.

I'd love to see at least a basic template for Fusion error logging to a dedicated project in WF (like what was shown at today's Fusion Exception Handling Framework workshop). I'm sure folks would need to customize handling for their specific needs, but it'd be great to have a staring point--along with tips for setting up the logging project, custom forms/fields, etc. Maybe a template along with a future cookbook recipe?
Splitting large datasets to process them in batches that could help to resolve errors related to hitting history/log, etc limits
Hi @viovi this has been recognized as a gap in our documentation that is being addressed in the near term. Look for guidance on pagination in about a month. I will try to make sure to update this string when the article is up and available. Thank you for submitting.
Workfront customers currently rely on manual checking of the Product Releases page. This is a high-risk process because there are frequent changes to the relevant release data and it is often spread across several deep-linked sub-pages, making new updates nearly undetectable without constant, dedicated oversight.
We propose a Fusion "Product Release Watchdog" template that establishes a zero-fail, proactive governance framework to ensure system stability and accelerated feature adoption for all customers.
Key Automation Functions:
- Continuously scans the release pages and triggers only upon true detection of a new (quarterly/monthly) release or update to the list of enhancement features.
- Instantly creates a standardized Change Management Review Project in Workfront, ensuring an actionable task for every release feature.
- Extracts every Enhancement Feature and creates an assigned task, immediately informing the System Admin, Group Admin, or assigned team to begin Preview environment testing, and the decision on communication strategy for internal audiences.
- Eliminates human error, secures system governance, and accelerates the test, feedback, and communication cycle.
This template would deliver a boost to customer satisfaction and adoption by:
1. Ensuring Seamless Transition: Minimizing disruption from new releases by enabling thorough pre-release testing and feedback submission.
2. Accelerating Feature ROI: Faster, organized review means customers can implement and leverage new features sooner, driving immediate return on investment.
3. Building Trust: Providing reliable targeted communications based on early validation, reducing user friction and confusion.
Hi Adobe Team,
As the Ultimate Success Technical Account Manager for Equifax and other customers, I dedicate 30 minutes to two hours weekly to reviewing and sharing information about upcoming changes with my customers. To streamline this process, it would be incredibly useful to have a fusion template option (if possible; not sure what/how that would look) for customers to reference, or an opt-in feature that provides an easy way for customers to access newly posted updates on a regular basis (other than sifting through posted documentation having to distinguish what is old/new).
Currently, this process feels manual, both in terms of reviewing and sharing updates, even internally, we often don’t receive this information before it’s published publicly. In some cases, updates are posted after implementation has already occurred, or on the very day of implementation, making it challenging to manage communications effectively. A more proactive solution would add significant value to both internal teams and customers.
Views
Like
Replies
Views
Like
Replies