Adobe Workfront General

Problem: Adobe Captivate and Adobe Learning Manager do not have a proofing platform. Authors must use their own environment to provide their customer with the content to review. Proposed Solution: Use Workfront’s proofing mechanism to review and collaborate on Training Content. Native publishing from proof approval to the Adobe Learning Manager's Content Library would be ideal.

Description Problem: Currently, the LMS does not provide a way to organize, view and structure Training Content. While the content is uploaded, the UX is limited in being able to sort or find content, content ownership, permissions, etc.. of the content uploaded. Typically, a company needs to implement an LCMS (learning content management system) for this.   Why is this feature important to you - Organization and lifecycle management of training and learning objects is hard to do, and requires a CMS solution, with project management capabilities. I believe we have all of this between AEM, ALM, and WF.    How would you like the feature to work Proposed Solution: Use Workfront Fusion to provide native connection for tracking the lifecycle of Training Content from concept to deployment within Workfront. I believe Workfront and additional connectors like AEM Assets or SharePoint for storage has all or most of the capabilities that an LCMS in the market today has.   Curr

Description - Could we add multiple owners on a Team? Why is this feature important to you - Allows multiple users to add/edit the people on a team and allows greater control when managing items throughout a group. How would you like the feature to work - Ability to select current owners on a teams or set 'resource managers' on a team. Current Behaviour - Only one name can be assigned to each 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

It would be great if you could have another option besides alphabetical for sorting the items on a calendar. This is a minor change, but one many team members of ours have noted. Currently, we use a workaround of prefixing with a number (e.g. "01 - Item Name"), but this can be messy depending upon what the item is named.

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 decis

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 f

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.

Description - The process of adding users as Group Admins is very time consuming and inefficient, many times the same user needs to be Group Admin for many Groups and this can be done only by editing each group and adding the user there and then changing from Member to Group Admin   Why is this feature important to you - We have growing number of Group Admins per country and region, who support their countries, solving incidents and implementing requests, we add many existing and new users as Group Admins to numerous groups.   How would you like the feature to work - Have a Group Admin field in user edit window or being able to bulk edit several groups and add Group Admin to these groups in one go.   Current Behaviour - Currently we manually add each user to several groups as Group Admin one by one, this is very time-consuming.

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)