Product Communities

Request for Feature Enhancement (RFE) Summary: Related case #E-000807920 Use-case: If you want to use Launch functionality to change a template of a page that has sub-pages are using the launch functionality, then the subpages are deleted when you have include sub-pages toggle on.   Steps to reproduce: 1. Create Launch of a page having subpages2. Select the page and leave the "Include subpages" toggle on, then Next.3. Give a launch title and select the "using a new template to replace the page" option, then Next.4. Select different template and create the Launch5. Goto corresponding launch page and "Promote Launch" and continue with promote full launch.6. It shows the page's modified whereas all the subpages are deleted.   More details can be found on the ticket #E-000807920 Current/Experienced Behavior: Sub pages are getting deleted Improved/Expected Behavior: a) don't have the switch "include subpages" in the launch dialog so that you avoid this effect. This mea

Description - Why is this feature important to you - We can't use the Custom offer attributes in determining the offer eligibility of an customer in segments. How would you like the feature to work - The platform should allow to consider inbound attributes in determining the offer eligibility apart from customer profile data. Moreover, the platform doesn't provide any flexibility to use any custom attributes from the inbound request.  Current Behaviour -It can only support through events streaming but there are impact of that approach too as number of events on a profile will increase, also ;segment evaluation and offer presentation is not realtime and would need few minutes lag to return the appropriate offer.

Description - Ability to display labels instead of values from custom form fields. Why is this feature important to you - It would help with our reporting, How would you like the feature to work - when adding custom form fields to columns in reporting we want the ability to display the labels instead of the values. Current Behavior - Currently the only way to display this is to manually add conversion logic for each individual field, which just isn't feasible when we have dozens of fields.

Description:  When setting up a Scheduled Project from within Workspace, the settings require an end date for the email reports. As an Analytics consumer, we want to set this end date to be 5-10 years in the future. Importance: In our use case, we have over 3,000 workspace reports set on a monthly send schedule. It is a huge lift to renew and extend these expiration dates every 11-12 months. How would you like the feature to work: The end date field would remain, but the future date would be extended.  Current Behavior: When setting up a Scheduled Project, the settings require an end date for the email reports, and it is capped at one year.

I've been enjoying the new Intra-Linking feature in order to create a Table of Contents at the top of my (often very long) Workspaces. For example:What I'd love is a new Visualization that users can drag in from the left panel that is automatically filled with intra-links to all visualizations and auto-extracts the name of each visualization into the ToC. Even better, if we could uncheck any visualizations that don't need to be linked.

Description - When configuring an error handler in Fusion, I would like an option to have it RETRY the same module again.  This is particularly true for Connection errors.  Sometimes modules timeout in a search so I would like to have an error handler that just tries it again.  I would like to be able to configure the number of times it will retry before it actually becomes an error.   An alternate option would be to just have Fusion do this inherently.  If the error type is a connection error, retry up to 3 times.  That way I wouldn't even have to add the extra error handler modules.   Why is this feature important to you - I'm frustrated with having to add multiple extra modules to my scenarios because the error handler won't just tell the module to try again.   How would you like the feature to work - see above.   Current Behavior - there is no retry option.

Description - Typeahead fields are essential for maintaining data relationships.  Enable the current filtering functionality to also respect dynamic filters (like other parts of Workfront).   Why is this feature important to you - Currently a typeahead field can only filter to a hard coded filter (ex: portfolioID=12345).  The challenge with typeahead fields is that they can have tons of possible options - many of which may not be relevant to a given scenario.   How would you like the feature to work - Enable dynamic filters (ex: portfolioID=DE:Custom Field) This would allow us to dynamically filter the results based on an attribute on the project - leading to cleaner data and easier experience for end users.   Current Behavior - It returns erroneous results.

Would like the ability to change the view and add/remove columns in the Submitted Requests page.

Description - Copy Project does not copy cross-project predecessors as one would expect when copying predecessors. To not copy cross-project predecessors mean manually having to re-associate tasks. That means having to manually compare projects, use the inefficient task selection dialog for predecessors (project/task filtering by name isn't good enough to actually find specific projects or tasks), and confirm that everything in the project is set up properly.   Why is this feature important to you - Copy Project is incomplete if it does not copy all attributes of the source project.   How would you like the feature to work - Copy Project must provide a way to copy all attributes including cross-project predecessors if it's going to be a full copy.   Current Behaviour - Copy Project ignores cross-project predecessors

Description - Prompts reflect classic experience when typing in a name. Why is this feature important to you - Lacks consistency of entire platform and reduces confidence in user base. How would you like the feature to work - Display email address and job role like Updates and Assignments area.   Current Behavior - Please view below:  

Description - The Fallout visualization is more than just a pretty visualization, it also is my favorite way to create (complex) Sequential Segments. Next to the Flow viz, it is the most beginner-friendly way into more powerful segmentation techniques. To make the visualization more powerful and the Segment creation easier, I prose to offer more options when editing a step: Besides Eventual Path and Next Event/Hit, there are many more useful restrictions I can think of: Session based: Within the same Session In the next Session In a next Session After/Within X Sessions Time based: In the same month/week/day/hour On the next month/week/day/hour After/Within X month/week/day/hour Dimension based: On the same dimension item (like page) On the next dimension item After/Within X dimension items Event based: After/Within X events Distinct dimension based: After/Within the nth distinct dimension items

Currently within fallout reports users have two criteria options for evaluating paths: "eventual path" or "next hit".Given that segmentation capability exists for within hits, pageviews, visits, minutes, hours, and additional time periods, it reasons that more options could be made available. This idea is to enable support for any of those criteria within the fallout report.   A specific example from our site: We'd like to be able to evaluate the flow directly from 'page a' > 'page b' > 'page c'. Our 'page b' is a search results page and users can view it many times sequentially. As a result using the 'next hit' criteria, even with a page name eVar (with visit expiration) is very different than the results for 'then within 1 pageview', regardless of which setting for 'repeat instances' is selected at the project level.   For a more generic use case, this would allow folks to do page level fallout pathing more accurately, given many users will have link hits that can exi

Description - The workfront task/ story/ epic Description needs text formatting capability (including table creation) & also should allow image insertion on the go Why is this feature important to you - Improves the readability of the content and also helps not to miss the key points that were highlighted/ formatted   How would you like the feature to work - As like in text formatting screen   Current Behaviour - No text formatting or Image insertion support provided 

Description - making the threads in the updates more clear for user   Why is this feature important to you -   the users get confuse on to how they are answering or how to answer making this more that once the updates or responses to the are not correctly received and making the ticket not meet SLA   How would you like the feature to work -   make it clear to what thread you are answering or updating maybe using bubbles to surround the updates even colours to see different discussions   Current Behaviour -   no clear threats is just a black page 

Workspaces and Partitions should be archivable.   I am new to community posting but I was told this is the only way we might see a solution to this issue.  We use workspaces for different clients and we can not have data crossing between projects and in some of our projects we have HIPAA Concerns and legally can not.  The biggest issue for us is that when we end our contract with a client, there is no way to archive the workspace.  I see this as a major issue for us because every year we are adding to this structure and there is no way to clean it up.  

Hi, Analytics Workspace Dropdown feature currently needs the specific values to be dragged on to the dropdown to show those filter in reporting. This may result in manual update to the dropdown values frequently when new dimension values are available in reporting. Request is to have an all values dropdown that can auto populate new and existing values with one drag and drop when initially creating the dropdown. This would have saved everyone's life a lot better. Please reachout if you need any additional details or questions. Thanks & RegardsAbraham  

Description - It would be nice to be able to configure in Target UI the default setting for where audiences are saved when new audiences are created. Why is this feature important to you - The current default for audiences in 'Audience Library'. Unfortunately, the vast majority of audiences that our team creates usually should be saved in 'Activity-Only'. Because of the default selection, authors are often moving fast and not paying attention to where the audiences are saved. Allowing us to configure what the default setting is would help minimize a cluttered Audience Library. How would you like the feature to work - toggle setting somewhere in the admin that allowed us to choose the default location Current Behaviour - There is no configuration currently. The default setting for a new audience is always 'Audience Library'.

Description - It would be helpful to allow (with warning) the capability to delete Audience Library audiences even if they are referenced by old activities.  Why is this feature important to you - After many years and many users, the audience library is cluttered with hundreds of audiences (that should have been saved as 'activity-only probably). These audiences are no longer valid, but are used in old, archived activities. In order to delete these old audiences, I have to also delete the activities that reference the audiences. This will be a tedious manual effort for cleanup. How would you like the feature to work - This could work the same way it is handled for AAM audiences. If an AAM audience that is referenced in an activity is deleted, the activity remains intact but displays a warning symbol that indicates the referenced audience is no longer available.  This feature could even be limited to only working for activities that are archived, and could exclude activi

I'd like to be able to export the list of Marketo Sales Insights user with the Email Add-in from the admin panel. These can currently be viewed but there's no way to export that list of users.

When viewing a project's gantt, either from the task list page or via a report, it would be useful to see all milestone diamonds associated with child tasks "float" up onto the parent task's bar on the Gantt.    In a task report, this would allow you to bring in only the parent task to the report but still be able to see the distribution of the nested milestones across the parent task's timeline. 

We have really a lots of projects in Workfront. That's why it would be very useful if we could filter on active projects when moving tasks. The same with the search. We would really appreciate if not always completed projects would be listed first.

Currently when viewing a week in the Workload Balancer, it shows Sunday - Saturday.  To maximize display area, would like the option to show weekdays only.  This could be a configurable setting.

Description - At present project conditions (In Trouble, At Risk, and On Target) are controlled at the system level but many groups would prefer to use custom conditions (e.g. Red, Yellow, Green) for their Group. Why is this feature important to you - The default conditions do not align to how our org reports status and the default terminology without color confuses some folks (which is worse In Trouble or At Risk? Hard to know without a color association.). This would allow Group Admins to control the condition and align Workfront more closely with the org processes.. How would you like the feature to work - allow group admins to customize the names of project conditions for their group. For example:our group would prefer a simple Red, Yellow, Green (and gray for projects that are not in progress and where condition is not applicable) Current Behaviour - Conditions are only customizable at the System Level.

Workload balancer is not useful the way it does hours.   Today, if you have a task assigned to a user that should start today and is worth 4 hours but the task gets delayed and doesn't start until 2 weeks from now, the task itself will show on Workload balancer but the 4 hours will be stuck back on the original date. This is even if using projected dates. This makes the workload balancer unusable to "balance work" as it will look like the user has 4 extra hours of capacity.    If a task gets delayed, I would carry the 4 hours over to the projected date on Workload balancer so it has an accurate representation of a user's actual workload. Until this is fixed, I have no use for Workload balancer or Resource Planner.    We should not have to edit the planned start date of the task if it falls behind. That is the purpose of the projected start date.