Build better products with our product team
We have in several occasions experienced that created content in a email templates disappears - and needs to be redone. This is extremely annoying and time consuming for the content producers. There are several theories what this happens, some from you at Adobe also. Like: there is several tabs open with the same template open, or there are several users working on the same Journey and/or email at the same time. To avoid this kind of situations where content actually disappears, we would like to have a features that lock the content to the user that has it open - and changes can not be done to the content by other than one user at the time. When open and try to change content when it is open already a warning message should appear and inform that this template/journey is blocked be user xxxxx. You can take over the editing role by overtaking the role. What we would like is basically a build in control feature that makes it possible for just one user to make changes at the same time to emails and Journeys.
When you have many master e-mail templates in use, and you need to do a change f ex to styling that is placed in the Head section of the templates, it takes a lot of time to update all templates with the change. If the email templates could have a centralized place where the head section was stored it could be maintained from one place - the whole style config used in the head section for all templates. This makes it easier and faster to maintain the system especially when you have many different templates to maintain.
It is important to us to be able to select multiple email templates at the same time and do a batch delete instead of deleting one by one. This is time consuming and unnecessary. The same goes for archiving Fragments. It would be nice if we could have multiple selections of Fragments and then do a batch archiving. A similar process is also wanted when you are creating a package of templates and/or fragments to be moved from one sandbox to another. It would be nice if we could do a multiple selection instead of selecting one by one fragment and one by one template into one package, This is time consuming for a administrator to do. We hope for a better and smoother solution here.
Description - Until very recently the Auto-Align button was on the main screen. Now it is hidden under the More (...) button.Why is this feature important to you - When I'm building I use this button dozens of times per day...possibly even hundreds of times. Now with it hidden underneath the More (...) button it is doubling my mouse-clicks....very frustrating.How would you like the feature to work - Please put it back on the main screen.
Description - Customize the Task Summary in Workload BalancerWhy is this feature important to you - We would need to customize fields that are getting displayed here so that it is each for the resourcing manager to choose the required fields that is neededHow would you like the feature to work - Provide an option to user to choose the fields that are displayed in Open summary section. This should be either controlled by assigning appropriate Template changes Current Behaviour - No option to edit the fields that are displayed in Task Summary field
I was developing a campaign to track records created by Web API users and assign a specific person source accordingly. Although the campaign was set up, it currently qualifies all records created via the API because there’s no way to specify or filter by the individual API user. To improve this, I suggest Marketo to introduce a "User" constraint in the trigger “Person is Created” and the filter "Person was created" to identify which user created the record. This capability would streamline tracking and attribution, making campaign management more precise and efficient.
Description: I would like the "Create CSV (Advanced)" Fusion modul to include the options "delimiterType" (Comma / Tab / Other) and "Delimiter Character" (displayed & required only if "delimiterType"="Other"), so that I can generate a CSV file with not only Comma as a delimiter.Why is this feature important to you: This would allow us to generate CSV with delimiter aligned to local needsHow would you like the feature to work: Delimiter in the generated CSV file is defined by the user in the module configCurrent Behaviour: CSV is always generated with comma as delimiter
Description - As an queue owner, I need the ability do deactivate a Queue Topic without having to delete it or obfuscate it by moving it to a "hidden" topic group.Why is this feature important to you - this will save a lot of time and effort when managing an intake queue. Allowing me to toggle a queue topic will also support intakes windows (e.g. annual or quarterly intakes) without having to (a) leave the queue topic open and manage misdirected requests, (b) delete and recreate the queue topic each time it is needed, or (c) move the queue topic to another section (e.g. z_do not use - ugly!) and back again when i need it. How would you like the feature to work -I would like to be able to "edit queue topic" and toggle an option to "deactivate queue topic / active queue topic"Current Behaviour - No functionality exists to deactivate a queue topic.@jessere1
It would be great if you could customize a calendar on the Vi !rtual Report Suite level rather than only on the parent report suite.Example: Creating a virtual Report suite which has the week starting on Mondays instead of Sunday.
Description - Add a toggle switch to queue topics that allows deactivation of the topic.Why is this feature important to you - When we need to revise a queue by way of omitting a topic, we have two options: delete the topic, which deletes the associated data, or rebuild the queue. A deactivation switch for topics would make queue administration much simpler and efficient. Additionally, it would bring the functionality in parity with many other objects in Workfront.How would you like the feature to work - Similar to many other objects in Workfront, there would be a simple toggle switch to deactivate a topic. This would hide the topic from general view, but retain detail.Current Behaviour - We cannot deactivate topics.
Description - When building a custom form you can view fields and sections in the form library. On the right panel it will note if it is used on other forms and you can click "view related forms" to get the full list. This list is incredibly helpful as is but would be more powerful if it indicated active vs inactive forms. Why is this feature important to you - Knowing that a field is only seen on inactive forms would quickly indicate that it shouldn't be used for the form I am creating/updating. It also tells me that if I wanted to make an update to the field (hide/show a choice, rename it, change the lable) no active How would you like the feature to work - Even something as simple as making the inactive forms gray and keeping the active as blue would help. Or if there's more real estate adding an x icon next to inactive forms. Another idea is to split the list into two sections one for active and the other inactive. Current Behaviour - I have to either open another tab, look at the custom forms list and quick search the form name to see if it's an active form; or run a report for active forms and see if these are on the list
We're currently undergoing an exercise to fully automate our reporting. We have a number of scheduled reports (report builder) and projects (analysis workspace) that need to go external to our company, and as per company policy, I need to be password protect them before they can be sent.Would it be possible to introduce as system that would allow us to apply password protection to files as part of the scheduling tools?
Description - Rich text fields have a few oddities when they are used in an External Lookup Field interaction. Rich text fields can cause External lookup fields to fail to be able to be selected OR result in an output that is not user-friendly. Why is this feature important to you - The more consistent a feature is in Workfront, the more likely it is that I can use it to design a useful and impactful UX for my team. How would you like the feature to work - Either bring in full support for user-friendly Rich Text results in External lookup fields, or give additional features in the setup of an External Lookup Field to allow for system admins to control the results of the field. Current Behaviour - 1. The 2,000 character limit on an external lookup field will run into a conflict pretty easily when returning the results of a rich text field which to my understanding has a 15,000 character limit. The results of a rich text field are returned with their JSON wrapper intact. This uses quite a few characters, especially in results with multiple paragraphs or a good deal of "rich text" like attributes. It also displays the JSON wrapped output to a user which can be extremely confusing. Additionally, a calculated field, or a block of textmode akin must be used to "Clean up" the result. Example here:valueexpression=IF(CONTAINS("text",{DE:YOUR CUSTOM FIELD}), LEFT(SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})), SUM(SEARCH("type",SUBSTR({DE:YOUR CUSTOM FIELD},SUM(SEARCH("text",{DE:YOUR CUSTOM FIELD},1),7),LEN({DE:YOUR CUSTOM FIELD})),1),-3)),"") 2. Manipulating a field with a dependency can cause an error result on an otherwise valid choice, creating hidden "invalid" choice amongst valid choices all driven by character limits. This is difficult to control because the JSON wrapper is variable as well, so text block of 1,800 characters could be valid in some cases and invalid in others solely based on how many paragraphs were used in the text. 3. There seems to be no support for a JSON Path-based "cleaning" of the output of an external lookup field.Example:$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'] ---> This one works, but results in the JSON wrapped text$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[*].text ---> Does not work$.data[*].parameterValues['DE:YOUR CUSTOM FIELD'].blocks[0].text ----> Does not workIf either of the 2nd or 3rd approaches worked, we could bypass some of the obscure and inconsistent outputs we get as of today by trimming the results of their JSON wrappers.
Description - Allow lookup field results to serve as the basis for display logic within a custom form. (Especially $$HOST-based fields) Why is this feature important to you - This would bring external lookup fields to parity with other selection-driven logic on other field types in Workfront. How would you like the feature to work - When a user makes a selection in an external lookup field, that field should be added to the list of possible display-logic and skip-logic choices in subsequent fields within the same custom form. Just as dropdown fields do today. This allows for greater control and intelligence within a custom form design process to ensure users are guided to selections that make sense for a particular end-goal. Current Behaviour - External lookup fields are not recognized by the system as valid choice for which a user can initiate display or skip logic.
Description - When using a $$HOST-based external lookup field and maintaining a data table, such as a list of US States, users currently have to click on each valid option that appears in the picklist for a multi-select-allowed External lookup field. Why is this feature important to you - This will bring parity to the External Lookup Field with the Multi-select Dropdown field. Much of the discussion around external lookup fields is that they can be used as a dependency-driven list of results that helps control front-end user input, especially when flowing through a custom form for an intake process. This really supports staying away from the "Garbage in, garbage out" trap of users mis-selecting options in an intake process. How would you like the feature to work - When "Multi Select Dropdown" is selected in the field setup, users should be given a UI-button that responds the same way the current Multi-select options (Dropdown, Checkboxes) works. A "Select All" option should populate all of the choices that are valid for the JSON path, and then from there, users should be able to use the "x" button on the individual choices they DO NOT want to include. When the 1st option removed, the "Select All" button should also clear, allowing for it to be re-selected, and any options that were removed, should be re-added to the list within the field. Current Behaviour - Users have to click every valid option in an external lookup field result. Bonus fix/Observation!!! - The user experience when selecting multiple options from an external lookup seems to be wildly inconsistent. Some users can click a result, and the list of possible results stays open allowing them to quickly click more options to add to the selection. Other users have the external lookup dropdown interface close with each and every selection, requiring an additional click to re-open the selection field, and another click to select an item, which subsequently closes the field again.
We would like the Workfront Mobile App to allow the screen to be mobile-responsive and display all information in landscape mode.Some of our project names are long so it only displays some of first and last characters with an ellipsis in the middle when searching for projects. We are hoping landscape mode would fix that issue and make the app more user friendly.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.