Routing Rules / Request Automation / Dynamic Forms / Automatic Project Creation - No Fusion

Forum|Forum|2 years ago
March 20, 2024
2 replies
549 views

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 Completed

Similar to #1, allow us to set routing rules based on how the request form was completed. If certain custom fields options are selected, then we are able to configure routing options such as a) assign the request to a specific user(s), b) convert the request into a project using a specified template, c) send a customized notification to specific users/roles d) automatically set the status of the request to a specific status, e) remove specified tasks from the converted project, etc.

Why is this feature important to you -

Ultimately, we're looking for more out-of-the-box functionality to configure dynamic routing based on how the request form was completed. Requiring Fusion to meet these needs places extra cost and time on the customer to build missing functionality that we believe should already be included. This functionality would reduce the amount of work/steps for our teams. These are repeatable and predictable steps that can be automated. This functionality is currently available on competitor systems (Asana, ClickUp, etc.).

N

Nid_07

Level 2

+1 These are minimum feature enhancements expected from Adobe to the Workfront platform, instead of redirecting customers to Fusion always.

S

seanaber

Level 2

Upvoted — native support for this would remove a whole Fusion scenario from my builds. Until Adobe ships it, here's what the Fusion workaround looks like in production, since this thread names it but nobody's described it: I delivered exactly the a/b/c in this idea for a creative team taking ~20 multi-asset requests a week.

(a) Assign by form data: Fusion watches the queue and assigns the request from business rules over the custom form fields (division, request type, etc.). Our ruleset resolved assignment from 100+ field combinations — routing rules can't read custom forms, but Fusion reads all of them.
(b) Convert with a template: on approval, Fusion creates a project per asset indicated on the request — named to the team's guidelines, task assignments set by the same rules, schedule set from the asset type's SLA (or the requested target date for rushes).
(c) Notifications ride the same scenario.

Two honest costs to budget for if you go this route: the intake form almost always needs a rebuild first (every field the automation depends on must be required, or garbage gets in), and you need a designated triage assignee for requests that match no rule — otherwise they go unassigned and drift.

I wrote the delivered build up end to end (including the rejection criteria and what broke at launch): https://thousandcuts.ai/guides/creative-request-intake-automation

+1 to the idea regardless — this shouldn't require an extra license to do.

Sign up

Login with SSO

Login to the community

Login with SSO