Build better products with our product team
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
Request for Feature Enhancement (RFE) Summary: When user account is created in Admin Console side, then the user gets sync up with AEM & user is shown in AEM side.In the same way, when user account is DELETED from Admin console, then that user shall be removed from AEM. Use-case: Management of user addition, user deletion from Admin Console. User addition/deletion policy shall have a clear user case in association with Admin Console. Current/Experienced Behavior: If existing user is DELETED from Admin console, then that user is shown as "enabled in AEM" & not removed from AEM. Improved/Expected Behavior: When user is created, then the user is shown in AEM side.In the same way, if existing user is DELETED from Admin console, then that user shall be removed from AEM Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud 2021.05 version Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - Need the ability to move custom fields added to cards in the Configure --> Cards area. It is already clunky and buggy, but if you have to add a new field towards the top of your custom fields, you have to delete EVERY custom field added, then add the new one, then add EVERY custom filed and update names. Almost makes it not worth using boards if you have to update custom fields on the cards. Why is this feature important to you - When designing boards and the card fields, there is a bunch of feedback given to make adjustments, so every time an adjustment is needed, it takes a large amount of effort to make these additions. How would you like the feature to work - Be able to drag and drop custom fields once they are configured to be on the cards (Board --> Configure --> Cards) Current Behavior - Does not allow for moving or re-sort custom fields once added to the card configuration
Description - Right now if there are 2 assignees on an issue there's no way to edit allocations. The only option is 50/50, and that is not great for capacity planning in WLB. Why is this feature important to you - It would make the WLB a more accurate representationHow would you like the feature to work - 1) adjust allocations within WLB, or 2) adjust % within the assignment area of the issue when editing.
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?
In design studio, we are able to move image or file from one folder to another folder. It would be great that we can move Advanced BI Analytics reports from one folder to another folder. This will be very helpful to re-organize the reports location. Right now, we cannot move the reports from one folder to another. Thanks
We need the ability to send out automated emails with a Dashboard attached. Currently this is only available at the report level, but my team and I have often needed to send out an entire dashboard on a regular bases, and it doesn't make sense to send out each individual report from the dashboard (too many emails). There should be a way to send out automated emails with a Dashboard attached.
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.
Description -I would like to see the My Projects and My Tasks widget column show the same way project and task view shows in project pages, whether or not the user access has filter edit. Why is this feature important to you - My Projects and My Tasks filter-grouping functions the same as projects and task filter-view-grouping, for users without filter edit permissions. It would make sense if users without filter edit permissions could also see My Projects and My Tasks column, since they can see projects and tasks view.How would you like the feature to work - All users can see My Projects and My Tasks columns, without having access filter edit permissionsCurrent Behavior -Only users with filter edit access permissions can see My Projects and My Tasks columns, without having access filter edit permissions
Description - It would be amazing if the LOG ID or Error Event ID and/or URL were added to the "Add Error Handler" modules. By defualt you only provide the fields "Type, Message, and Detail". Adding the LOG ID to the error would be immensely helpful. Why is this feature important to you - We use the Ignore module but still want to send private message like this - That works well, but we are then forced to search through hundreds of logs to find the right error log related to the event. If we could pass a URL to the log or an ID for the event (that we could use to create our own URL), it would be awesome and save so much time!! How would you like the feature to work - Add the URL of the log and/or the ID of the LOG related to the error that occurred and triggered the "Error handler"! Current Behaviour - it does not exist.
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.
Description - Please add the Workfront Project "securityAncestorsDisabled" field to the "Project Endpoint" in the public API!! It's shocking that this is not in the public api and part of the internal-only api. Why is this feature important to you - it would be good for us to have this type of information to better align data over fusion updates and also have the ability to better know which projects are intentionally isolated from permissions. Going through the internal API is harder. How would you like the feature to work - add the "securityAncestorsDisabled" field to the Project Endpoint in the "public api". Current Behaviour - the field "securityAncestorsDisabled" is only available in the private/internal-only api. Thank you,DD
Description - Do not allow time to be entered on a project or task before the Start Date (planned or actual) Why is this feature important to you - better compliance when it comes to entering time/timesheets and in the end give more accurate reporting. Currently our team is using Workfront for time/timesheets so it is important to be as accurate as possible. How would you like the feature to work - When a user goes to enter time on a project or task, the days before the start date of the object are greyed out, not allowing them to enter time in the past or before the object was created. Helpful if this could be an option in the Setup menu. Current Behavior - The user can enter time in the past for a project or task that was just created, giving inaccurate data on Timesheets and in reporting.
When a user is deactivated, they should be removed everywhere. I keep finding little easter eggs of old users and can't even begin to find all the places they need to be removed. Examples, assignments on templates, sharing on projects created from templates, custom views sharing. The only thing that should remain, is a history of what they did. They should not still have views and such shared with them or newly created projects shared/assigned.
Description Sorting for bucketed dimensions in CJA should default to logical sorting by the dimension's numerical value, rather than it's label. Buckets should be displayed more clearly (Less than 30, 30 to 59, 60 to 119, 120 or more) Why is this feature important to you Bucketed dimensions are intuitively understood when sorted in logical order by the value of the dimension. For example, shortest to longest time. It's confusing when two buckets are ambiguously defined and contain the same value (example: 30 to 60, 60 to 120). How would you like the feature to work Bucketed dimensions should default to logical sorting by the dimensions numerical value. At a minimum, users should have the option to sort by logical order. Example: If I have a bucketed dimension for time in seconds (Less than 30, 30-60, 60-120, 120 or more), I'd like the option to sort them logically as either: Less than 30, 30 to 60, 60 to 120, 120 or more, or 120 or more, 60 to 120, 30 to 60, Less than 30 Bucket ranges should be clearly displayed (without any overlap) Current Behavior Sorting by the bucketed dimension sorts by non-intuitive, alpha-numeric orders either: Less than 30, 60 to 120, 30 to 60, 120 or more, or 120 or more, 30 to 60, 60 to 120, Less than 30 Bucket ranges overlap (30 to 60, 60 to 120, 120 or more), causing confusion.
Why is this feature important to you - Everyone has done it: Deleted a report when they didn't mean to or know better. This moves cheese for our users and creates more admin work. How would you like the feature to work - Like other objects, send deleted reports to the recycle bin and therefore allow admins to restore them. Current Behaviour - We cannot restore reports. They're gone forever upon delete.
If you delete a project it is permanent. Adobe should implement a 30 day recycle bin where you can restore your deleted projects.
Description: When we create a filter in CJA, the size is default and we are not allowed to resize it. It limits the information displayed for the user, as seen in the image attatched to this idea.Why is this feature important to you: There are no workaround to solve this to us because the filter with this information is important to our reports, so only allowing to change the size would solve our problem.How would you like the feature to work: Similar at it is implemented in Workfront.Current Behaviour: Each filter has a default size and it is not posible to edit this.
Workfront advertisments for LEAP are listed on our main user login page. We'd like to be able to remove them. We do understand and appreciate your position as a SaaS company. Please try to understand that we are using WorkFront as a portal to working with our customers. So, by having the LEAP Conference splash page, or any other advertisement on the login screen, you are promoting to our customers - not just to us. We're a small company, but that is 400 customers with over 2,000 contacts who think they are logging in to work on a Level Data project. We've been having to explain away the LEAP Conference. My request is that you treat the splash page the same as how Salesforce treats theirs - it is up to the subscribing customer to set how they want to use it. Enabled to Salesforce default with whatever they want, Disabled completely, or set to what the subscribing customer wants.
With two or more report prompts, it's not possible to reorder them without deleting and re-adding them in the new order. It would save administrators time when they want to reorder the prompts.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
