Skip to main content

Filter by idea status

10000+ Ideas

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

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 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.).  

jeff_bloomer
jeff_bloomerNew Participant

Analytics Workspace - PLEASE Retain Scheduled Project Description Formatting in the BODY of Emails Received by End UsersNew

Description - It may seem simple and maybe even nitpicky, but I would like for the very basic formatting and alignment of the text in the #Description section of my scheduled project to, in turn, be directly reflected in the body of the emails received by the end users when they receive their scheduled emails instead of an incoherent, congealed blob of text. Why is this feature important to you - I already have a difficult time getting my end users to read the emails they receive without #Adobe making my job and my data storytelling more difficult. How would you like the feature to work -  At the very least, I would like the body of the emails to reflect the formatting and spacing the way it is laid out in the Description section to schedule my project, whether I'm scheduling a new project or editing an existing project. In fact, it would even be better if we had simple HTML editing capabilities to allow for richer content, and I know this should be possible. Current Behavior - Today, any text appearing in the Description is single-spaced together and placed in the body of the recipient's email with no formatting, minus one exception. That exception allows for any hyperlinks appearing in the text are made active and usable. These messages provide so much opportunity and potential for engagement with our data end-users, and this is one place where we are really dropping the ball, folks!