Build better products with our product team
Description - This would be an additional field type and would need the definition of colums. It would enable the request for multiple items using the same "fields". The columns would need to be selected from the list of other fields available on the same object Why is this feature important to you - Since you cannot have the same field multiple times on one form you have to either enter multiple items or use Fusion to create the additional items. This would How would you like the feature to work - On Custom Forms ability to select a table as a field type. Columns on the table would be selected from other fields. When data is then entered on the form the field would allow multiple rows to be entered at one time. Behaviour would be similar to a Purchase Order in a purchasing system where unlimited lines could be added. If this was entered on an issue, each line should be able to be converted to its own project, task etc. The rest of the information would all be available on the new object Current Behaviour - No option at this point
Description - A simple query takes an unexpectedly long time to complete. See examples below. This indicates that AEP Queries is just not ready for widespread, "production" use, really. Why is this feature important to you - 99% of writing a correct, working query is figuring out the way to write it. This requires a lot of iteration from a simple "SELECT * FROM table" to the final query. Querying speed is especially important here, so as to help the analyst improve upon the query until the final one is obtained. Any time spent waiting for a query to complete is time that could have been used to more productive use. Without this speed increase, Adobe can expect all of its AEP customers to flock to Google BigQuery and never look back. How would you like the feature to work - Improve the querying engine's processing from minutes to milliseconds. Current Behaviour - See examples. SELECT * FROM table LIMIT 10; --> 2.5 minutes SELECT * FROM table WHERE table.eventType = "something" ORDER BY timestamp LIMIT 10; --> 10 minutes --> and to add insult to injury, the query failed. SELECT * FROM table WHERE table.eventType LIKE "something" LIMIT 10; --> and yup, only to find out that it failed again.
Description - Strangely, there is no vertical scrollbar in the data governance table. Why is this feature important to you - The table almost always has a loooooooong list of rows. Scrolling with a scrollwheel is ridiculous (and noisy!). Scrolling with a trackpad is likewise ridiculous. A scrollbar allows the user to control how fast/slow to scroll, allowing for easier manual eyeballing of the row items. How would you like the feature to work - Show a vertical scrollbar in the data governance table. Current Behaviour - There is no vertical scrollbar in the data governance table.
Description - It looks like the dataset preview overlay has been designed for large monitors and/or large resolutions. However, on a standard laptop screen, the preview overlay's table needs a lot of scrolling, and that causes the table's headers to be gone from the view. Why is this feature important to you - There is a lot of unnecessary scrolling to identify the column names (need to scroll up and down repeatedly). How would you like the feature to work - Freeze the table headers to the top of the table, so that scrolling down still allows the column headers to be seen. Current Behaviour - see screenshots:
Description - Schemas that are in use by datasets cannot be edited directly. This contradicts https://experienceleague.adobe.com/docs/experience-platform/xdm/schema/composition.html?lang=en#evolution . Why is this feature important to you - Descriptions add human-readable metadata about what the schema is. While the schema might not change, including its name, there could be some wordings in the descriptions that need to be updated from time to time. How would you like the feature to work - Allow editing of descriptions directly, as expected. Current Behaviour - Schema descriptions cannot be updated without temporarily changing the schema name too, i.e. Edit the schema. Change the schema's name. Update the schema's description. Save the schema. Edit that same schema. Revert the schema's name to its original name. Save the schema. Notice the additional extra steps needed.
Description - Workfront Proof allows Approvers to continue making comments after they've entered an approval decision. I know it is possible to set proofs to lock after decisions are made, but we have several Approvers reviewing proofs simultaneously, and the proof will stay open for the other Approvers. I often think specific Approvers are done reviewing a proof, only to find they've entered additional comments. There are also times when an Approver will ask a question of another Approver in the comments, tagging someone who has already entered their decision. It would be great if we could set our proofs to automatically remove Approvers' decisions when they, 1. make additional comments after entering a decision, or 2. are tagged by another Approver or Reviewer in comments on the proof. The Approver whose decision is removed should then be notified that their decision has been removed and informed that they would need to review the comment(s) and re-enter their decision.
Description - I have been working to resolve a problem where an issue is failing to convert to a project using a project template. I have found that the project custom form limit is being exceeded at conversion which is causing the process to fail. There is an error message, but it only shows after submitting the "convert to project" form, being routed to a "project not found" page, and then using the browser's back button. Basically, error handling for the "convert to project" process may need to be updated to prevent users from submitting a "convert to project" form when the custom form amount exceeds the predefined limit. The custom form section could be highlighted to stand out and include a notification informing the user they are unable to submit the "convert to project" form until the amount of custom forms are reduced to 10. I attached a marked up screenshot that may help elaborate. Why is this feature important to you - Generally speaking, error handling is good for the user experience. Especially if they can be caught before submission. I understand that is difficult is some instances, but the handling for this particular issue can be confusing for user that are less technical. How would you like the feature to work - Error handling for the "convert to project" process may need to be updated to prevent users from submitting a "convert to project" form when the custom form amount exceeds the predefined limit. The custom form section could be highlighted to stand out and include a notification informing the user they are unable to submit the "convert to project" form until the amount of custom forms are reduced to the predefined limit. I attached a marked up screenshot that may help elaborate. Current Behaviour - Users can submit "convert to project" forms with more custom forms than what is allowed by the system. After submitting the form the user is rerouted to a "project not found" page. If they click the browser's back button they are taken back to the "convert to project" form and an error is displayed stating that the number of custom forms exceeds the predefined limit. "Project not found" page the user is rerouted to: Error received after clicking back button in browser: Suggested error handling with markup:
Description -It would be great to have the ability to make global updates to all of your user layouts so you don't have to go into each one every time you need to make an update that affects everyone. Why is this feature important to you - This would save a tremendous amount of time because you wouldn't need to go into every single layout and update it. How would you like the feature to work - I'm not sure about the best way to make this happen but perhaps there is a "global layout" and any time you make a change to this, it asks you if you're sure you want to make this change for all layouts. Current Behaviour -
Description - Send a notification to the document/proof owner if the proof fails to generate. Why is this feature important to you - Right now, unless the user waits for the proof to generate before continuing with their other work, which can take quite a while sometimes, they have no idea if the proof failed to generate which can slow down work. How would you like the feature to work - If the proof fails to generate it sends an email and in-app notification to the proof owner that the proof failed to generate. Current Behaviour -no notification is sent if the proof fails to generate.
It can be a guessing game to know when a SAINT either browser or FTP is fully uploaded.It would be helpful to have status to know an estimated finishing time, or even a more general status.
Description - It would be helpful to have a tag library for tags that can be applied to cards on boards similar to the field library that Workfront has for custom forms. Why is this feature important to you - A tag library would help streamline the creation of tags for boards. How would you like the feature to work - It would be helpful if a tag library functioned the same as the field library does for custom forms. Any tag created in your Workfront instance would be stored in the library and can be used for potential reuse. Created tags could be searched and added via the Tag Manager on boards or in the Tag field on individual cards. Current Behavior - There is no library for tags across created boards. You have to create new tags every time you create a new board.
Description - It would be great if the Workfront page could automatically refresh once a reviewer providers their approval on a document approval request. Why is this feature important to you - We have had a lot of issues where a reviewer will click approve twice because the status (see attached screenshot) remains as pending, and we lose the record of the approval and therefore cannot progress our work forward, or post the asset in our content library. How would you like the feature to work - once a document approval is sent the page should refresh and update the status to approved. Current Behaviour - when a document approval is provided the check mark turns green but the status stays as pending, so the reviewer clicks the check mark again which actually retracts the approval. Email notifications trigger to the project owner but when they check the document approval they see it as pending, it also remains in the reviewers work list as pending.
Description - In Team's "Current Iteration" view, adding a new story is missing the parent task input that exists when adding a story from the "Iterations" view. Also, it would be helpful to have an input for Assignee, which currently defaults to the team if no assignee is provided. Why is this feature important to you - It is missing feature that exists in another screen, and without it, requires manually moving tasks. How would you like the feature to work - Same as "New Story dialog" under "Iterations. After selecting a parent project, show the input for parent task. Add new input for assignee. Current Behaviour - Missing Parent Task input and no option to default the assignee (defaults to selected team, but prefer option to set a user or self)
Description - Workfront system should send out a notification or planned hours reminder when actual hours are 80% of the task's total planned hours. Why is this feature important to you - To help keep track of actual hours and avoid overage on the project's budget How would you like the feature to work - When a user logs time to a task and the actual hour is 80% of the planned hours, the system will send an email to both the project owner and assignee of the task to warn them status. Current Behaviour - There's no current notification
JavaScript activity can give more extension to the workflow engine, and it can be very useful to have a logging interface. Adding js activity to the workflow and a dedicated admin interface to record data for tracking will be a powerful step for ACS.
It would be great if a user's access level was preserved/stored when they are deactivated. Currently when a user is deactivated, their access level is removed. If that user is reactivated (via checkbox), they are not granted any access level, which basically leaves the user as deactivated for all intents and purposes. It would be useful if, when a user was deactivated, it "removed" their access level but stored it in a variable, field, or database so that when the user was reactivated, they automatically reobtain their old access level. This would remedy the problem of having activated users without an access level, but also I have also encountered situations where a user was deactivated which removed their access level, but there was no record of their previous access level on the System Updates section of the User profile. This prevented me from knowing what Access Level the user should have when I later reactivated them.
DESCRIPTION OF NEED: --------------------------------------------------------------------------------------------- For fields where there is a Category and a Sub-Category (example using cars: Toyota (category) Corolla (sub-category), it would be helpful if there was a custom field type that would allow for the category and sub-category to always remain in sync. CURRENT LIMITATIONS: Currently on a custom form, I can use display logic to show my sub-category only when the proper category is selected. HOWEVER this can not be accomplished on a report. Currently, if I select a category and sub-category, then CHANGE the category, the data remains in the sub-category field creating invalid data. Currently, there is no out of the box way to select the sub-category and have it imply the Categories above (example…. Selecting Corolla under Sub-Category would automatically infer Toyota as the Category and make the change). This is the case for either custom form or report. Why is this feature important to you - Automated and mandated Metadata / Taxonomy conformance vs. one-off resources and time to measure and manually address
As an Admin I'd like the ability to download a Layout template's decision data, including all current state configurable data elements contained within, such as Top Menus, left menus and field detail for all views, etc. Layout templates contain a very large number of configuration points across many different user views. Our organization maintains a large number of layout templates, which over the years have become more rich with an ever growing number of configuration points, yet there is no easy way to export the current state layout template for team review/approval. In our vision of the future state there would be an option available to download the decision data contained in each Layout template as an .xls/x file displaying key decisions with data arranged on tabs. This standardization would allow for much improved review and approve of team decision points for layout template configuration.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK