Description - Filters for the Workload Balancer do not stay locked when we would like to target them on different team dashboards. It instead saves the last used filter by that user for all dashboards that have the balancer on them. Why is this feature important to you - We need to be able to have filters stay "sticky" when they are targeted to a dashboard. We have built many dashboards for different creative teams, but we cannot effectively use them as the filters do not stay targeted on that page and always divert to the last filter that was used across the board by that user. This makes it very confusing for our users and they have to continually switch the filters to get the view they would like. How would you like the feature to work - Once a filter is created, Workfront should create a unique URL link. Or if this is not possible, could the balancer act like a report and be added to a dashboard as an object? Current Behaviour - We currently use the link to add the balancer to dashboards, but since the link is not unique enough it reverts to what was last used/filtered on the balancer page.
Hello, I wanted to share an idea of having an automatic time tracker per project. If there could be a way to add time tracked as a base work time tracked per projects once they get opened. For example, add 1.5 Hrs. as a base time track to each project as soon we open them, since we would like start charging a base standard fee to open and manage each project. Maybe can that be something we could add in one of the tasks in the task list templates thank you!
Description: Workfront uses the Event Subscription API to transmit changes to our services when a document in created or updated on a project. Currently, when a file is moved (drag-and-drop) from one folder to another, it does not fire any event to indicate that this action occurred. The argument i got from support was that this just "changes the folderID field 'on' a document", and that their product was functioning as intended. However, changing the folder ID for a document is in fact a change TO the document, as you are changing critical information associated directly with the document. In computers, a file/document always exists within a folder. When you change where the document lives, in computer operating systems and workfront, it is always done by doing operations on the file icon itself, or specifying the file's path and/or name. Thus, it makes sense that changing the folder a document is in should be an notable enough be considered an "UPDATE" event in the Events Subscription API. Why is this feature important to you: This feature will be used heavily by the Marketing department at our University. Documents will be initially created in a "Campaign Notes" folder, and will later need to be transferred into a "Finalized Files" folder. After the transfer to Finalized Files, an event should be fired to our services that downloads said folder into storage in our University's infrastructure. It is necessary that an event fires to signify that an existing file was moved into that folder. How would you like the feature to work: When any document is drag-and-dropped between folders in a Workfront project, a Document UPDATE event should be sent using the Event Subscription API described in following link: https://experienceleague.adobe.com/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-api.html?lang=en Current Behaviour: Currently, UPDATE events are only sent when a new version is uploaded from an external source, and CREATE is only sent when a new document is uploaded from an external source. As an upload is simply a "move" operation from an external source into workfront, I'm not sure why the same logic wouldn't apply to fire an event for "moves" of the file within workfront, also.
Form submit button is activated when Date-Time-my.token-Based is system date.
Description - Request Link Why is this feature important to you - Creates efficiencies around getting requests and briefs from our external contacts How would you like the feature to work - I want to be able to send the "share path" link on a request over to an external contact and it direct them to the correct log-in page Current Behaviour - Currently the link sends them to my company's internal single sign on page instead of their log-in page
Following the implementation of autosave, it would be advisable to include the possibility of enabling and disabling it if necessary, preferably directly within the WS project. It is very important to add this functionality: 1) to avoid modifying scheduled or shared reports during presentations by mistake; 2) to avoid saving many copies of the same report; 3) to avoid making continuous report switches between the original and the copy in case of live changes during a presentation.
Marketo offer to the functionality to publish the pages to Facebook. However as this social platform are becoming less relevant for some B2B clients it would be great to have this functionality for other channels like LinkedIn. We should reach to more audience in more channels.
We use calendars to show project go-live activities along with Change Freeze Windows and important (Executive Interest) tasks. The Calendars should have the ability to "Add Holidays" to the calendar directly from the user's schedule or the calendar creators selected schedule. It should be in the calendar option Add to Calendar so I can select which color the holidays show up in. It should be in the Advanced Options where you can show Tasks, Projects, Issues and Time Off - there should be one more option (Holidays). In there, you should be able to add Holidays from a particular schedule or best option, show Holidays for the $$USER.ID Schedule.
Description Currently, you can turn off, make daily digest only, make instant only, or make daily digest& instant notifications for email. However, you cannot customize what notifications you see in app independent of the email notifications. For example, it would be beneficial to my users to be able to say they want instant email notifications when they are directly tagged in an update, but only in app notifications for updates on threads they were previously tagged into. Why is this feature important to you Enabling this feature will allow users to cut down on the noise of notifications more efficiently and sustainably. Especially for our project management team who receive notifications on multiple projects at once. Previous Ideas request There is a request from 2017 that was put in by @ericma and it has many updates on it but Support has asked me to put in a new Idea request so I have. How would you like the feature to work: All communication types that are available via email will also need to be available via in-app notification (currently only Work-list and announcement are available via in-app as per Workfront Support) All email notifications have the options of a combination of daily or instant including turning them off completely or having both enabled. Adding a third option for in-app would allow users to decide where they are notified for each communication type. Current Behaviour: As per my support case # 00341694, the current behavior as identified by your support team is as follows: The in-app notification feature contains two types of information. Work-list and announcement. The work-list notification can be governed by the email-notification customization but will also impact the email notification.
Request for Feature Enhancement (RFE) Summary: Allow "READ" operations using the Adobe Experience Manager Assets HTTP API without requiring "WRITE" access Use-case: Users who are not given write access should still be able to fetch asset data using the Assets HTTP API even if they don't have WRITE access Current/Experienced Behavior: Right now, if a user only has read-only access, he or she is not able to use the read functions of the assets API Improved/Expected Behavior: Provide the flexibility to be able to use the API while only having a read access Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Prequire Screenshot (if applicable): Code package (if applicable):
Description - Why is this feature important to you - Mobile Scorecards is such a great feature/tool, but unfortunately we can't roll it out across out business because we have 200+ websites and there wouldn't be an option for the recipients to view reports isolated to their websites. How would you like the feature to work - Simple option for user to select Report Suites from pre-defined list specified in the configuration of the scorecard. Current Behaviour - No option to filter report on report suite.
Many teams that we have worked with are in hopes that they are able to select a portfolio or program field when submitting a request. This would allow the resolving project to be placed automatically into the portfolio or program when it is converted to a project. It would save teams time when the requestor already knows what portfolio or program to put it in. Note: In many cases for marketing teams the program or portfolio objects are their campaigns and would allow tactics/deliverables to be placed easily into the correct campaign or bucket.
Description - Why is this feature important to you - It would be great if images could be uploaded in response to questions/content on a custom form. We have many situations where we're uploading documents solely because they have creative in the documents section, but it would make more sense logically to upload them in a response on a custom form. How would you like the feature to work - When creating or editing a custom form admin's would have an option add an image option that would allow users completing the form to respond with an image. Current Behaviour - when a custom form is being used as a request there is an option to add documents, but that option does not exist when creating a task or project custom form.
Description - Many times when I attempt troubleshooting problems in Workfront, I find I need to look up information from a few months back. And, of course I attempt to do just this and I can't. Ultimately, there should be at least 90 days worth of historical data. Why is this feature important to you - I can't troubleshoot problems if I don't have the information. How would you like the feature to work - Just like now, but 90 days instead of 30. Current Behaviour - 60 days less of historical data than what I need.
It would be great to be able to copy and/or move a card between Workfront Boards. Currently you can only move them to a different column within the same board.
Hiya!I've noticed some automated anti-spam checkers have been clicking links many times automatically causing the lead score for some of our leads to be over-inflated and disingenuous; it's causing them to hit MQL stage way before they are actually at that point.A way to prevent this would be to restrict the number of times a lead can pass through a campaign for a certain time frame, however Marketo's smallest unit for time is hours. This poses a problem as it is plausible for a lead to engage with an email link or social app button more than once within an hour time frame. I did attempt to use decimal points (i.e. every 0.5 hours) however the format could not be saved.Could Marketo please consider adding in 'minutes' as an option to the available units. This will allow the lead to be restricted from passing through the flow for an interval smaller than one hour, but prevent them from running through 10--20 times within one minute as has been happening with some of our leads. Cheers,Brooke
Request for Feature Enhancement (RFE) Summary: Language Navigation should match the expected language code "id_ID" for Indonesian (Bahasa). Use-case: Language Navigation displaying incorrect language code for Indonesian (Bahasa). Current/Experienced Behavior: Language code displayed is "in_ID" or "in" which does not match the expected language code "id_ID" Improved/Expected Behavior: Language code displayed should be "id_ID" or "id" Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: AEM S3 connector support for SSE-C Use-case: For protection of customer data, encryption in transit and at rest is required. Some data stored in S3, requires the use of customer managed, customer provided keys. This provides an extra level of security through separation of duties, as one team/role can manage the keys, while another team/role can use the provided keys for encryption of the data. Currently, AEM S3 connection supports only two of the valid encryption options for S3 server-side encryption. SSE-C encryption is needed to allow for that separation of duties. Current/Experienced Behavior: AEM S3 connector currently supports SSE-S3 and SSE-KMS, but not SSE-C (customer managed, customer provided keys) Improved/Expected Behavior: AEM S3 connector would support all 3 encryption options Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 13+ Customer-name/Organization name: US Government Customer Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Restrict IP access for ingress integration that use Service Credentials on AEMasCS author without putting the whole environment behind vpn Use-case: The third-party connector leverages Service Credentials to access AEM as a cloud Author. It uses POST and Sling Post requests for updates in AEM. We want to make sure that if the credentials are compromised, nobody would be able to make any updates to the production environment from IPs that are not whitelisted. While the environment should be still publicly accessible. Current/Experienced Behavior: No IP restrictions per Service Credentials/Integration Improved/Expected Behavior: It is possible to restrict the access for the integrations per IP Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Macys Screenshot (if applicable): Code package (if applicable):
Description - Just as Timesheet Preferences can disallow logging time to Projects, add option for disallowing logging time to Issues Why is this feature important to you - Only wish Projects and Tasks to have hours put to them How would you like the feature to work - Add option in Preferences. Have overiride on Projects so that the Project Owner can decide whether hours can be logged on issues. Can be set on Templates in Issue Settings Current Behaviour - Only Project Hours can be prevented
Description - Since it is not possible to retrieve information from the parent Workfront window from an embedded iFrame, it would be good if the Messaging API, or similar technology, were implemented. Why is this feature important to you - It would be helpful to pass session specific information to the embedded iFrame, like the currently in Workfront logged in username How would you like the feature to work - Invoke a JavaScript Function returning an object with the relevant information Current Behaviour - no possible Messaging API
I've seen a few great requests about filtering/sorting Workfront notifications and while I'd love that, I'm really just looking for the ability to apply a "group by thread" approach (similar to Outlook emails) to the notification button/dropdown box at the top right side of the WF web interface. So instead of the current way notifications display--only in chronological order--they could be grouped together by project/task/issue so we can understand the conversation better without having to open each individual update page to see each whole thread. Even if that's not possible, it would be very helpful to at least have a way to "click as read" for all notifications in that dropdown box related to posts on the same thread. This is important because I can't always "mark all as read" and spend too much time doing the endless scrolling to decide which blue dots need my attention and which get clicked. There are times when I'm merely tagged on a project just "for awareness" and I don't have to read every subsequent post to that thread. Thanks for any help you can provide!
Description - Similar to how a user can expand fields in a custom form, by grabbing the corner. It would be very useful for users to be able to do the same in the Request Project > Description field Why is this feature important to you - Our partners submit a significant amount of information on requests. The small Description field is cumbersome to work with if you have a large amount of text. How would you like the feature to work - The same as the feature available in custom form text fields, where you can grab the corner and expand the box to be larger. Current Behaviour - The current Description box is not expandable. __PRESENT
please add a private notes option so the whole company can't see every update
Adobe Analytics is limited out-of-the-box to First Touch and Last Touch attribution models. In some cases in makes sense, but limits the ability to dig deeper into the user path and attribute performance accordingly to the proper marketing channels. A few blog posts highlighting various models now offers for free by Google Analytics puts Adobe Analytics' offering behind the curve. Adding the option of time decay, position based, weighted, or even algorithmic attribution model would be a huge plus!
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.
