Measurements need to be exact. Our print production teams need to use decimals.
We need the ability to exclude custom forms when attaching a template to an existing project. Currently, when you attach a template to an existing project, it forces you to include all custom forms associated with that template. This means filling out the required fields just to attach the tasks you need. In some cases, the current behavior has also caused us to go over the limit of the number of custom forms we can have on one project. Our PMs regularly need to attach new tasks when the project scope changes, or if work needs to be redone. Their current workaround is to create a fake project from the template they would like to use, then copy over the tasks from the fake project to the actual project. Copying tasks from similar active projects does not work and causes issues with inherited permissions/notifications. So, the only workaround they have now is very cumbersome.
It would be very helpful if we had the option for Proof Deadlines to automatically adjust based on PTO submitted by an approver.
When proofs are routing through ProofHQ, those who have time off in their calendar and submit a delegation of their work should be able to do so for proofs as well. At my company the only approvals that are sent are those through the proofing process and when people are on vacation they would rather not have their inbox filled up and have their decisions for proofs be delegated to someone else.
Being able to pull reports that indicate the stage due date instead of the proof end date. When there are multiple stages in a single proofing workflow, it is misleading to just get the end date instead of the stage date.
Hi, Is it possible to enable multiple selections for folders, assets, and reports,...? It'd be beneficial when cleaning up the instance, for instance, to move or delete several assets simultaneously. Thanks, Charlotte
Hi Team, While exploring and testing TAM, I found that: We cannot customize the weekly reports We cannot subscribe to Account smart lists I believe it would be great if we can customize the weekly reports (if not much, at least to some extent) and set up subscriptions for account smart lists as well. Kind Regards, Vinay
Description Beyond the install referrer data that comes from the App Stores... with Universal Linking and Deep Links so prevalent now, we are losing potential referrer attribution for traffic that comes to our mobile apps. Yes, we can track our campaigns, but I would love to be able to attribute Natural Search or Organic Social Media that trigger Universal Linking to our Mobile Apps. Why is this feature important to you Most sites/apps are using Universal Linking, this means organic traffic that opens the app directly is unattributed. How would you like the feature to work Not sure if Deep Links and Universal Links have referrer headers (in theory they should, since they are still web calls), that referrer data should be captured and processed. Directly opening the app (with no referrer) would be attributed to "Typed/Bookmarked". Current Behaviour Mobile Apps currently have no referrer instances and no referral data at all... in the past, this was somewhat expected since the Apps were always "opened", but now, there are so many ways that apps can be opened directly that I think it's time for a shift. Then when we pull a referrers report, the App can be included in the data.
Description - Allow Global definition (or Group) of User Defined Roles Or Apply Roles at a Project Level. Should be able to use a Wildcard such as $$ROLE:Campaign Manager in assigning tasks to that role automatically and use in routing rules and approvals Why is this feature important to you - Makes assignment much simpler. Can then dynamically route issues and/or approvals to more roles or people, not be tied to "Project Owner" etc. How would you like the feature to work - Allow for setup of User Defined Roles to apply on Objects and for each project etc. to have a resource assignable (with an alternate). Current Behaviour - Roles can be added to tasks.
Description - Allow use of defined wildcard users in the routing for Issues similar to Approvals Why is this feature important to you - Do not want to make the routing User Specific How would you like the feature to work - Same as on Approvals Current Behaviour - Need to use a role or a person's name
Default the values for a custom form in the Request Queue / Queue Topic Allow the form to be displayed when building Queue Topics so that you can then make selections Cannot currently default different values for any field, except in Project Template
Description - Why is this feature important to you - It is important especially if there are people coming back early from a christmas break. At the moment, its showing they are off during the close down period. Is there a way we can remove "holidays" tfrom their schedules so we can book their leave and start booking in work. How would you like the feature to work - Current Behaviour -
We are constantly proofing 20-30 proofs at once and need a report that can give us a high level snapshot of which stages have been approved and which haven't. Our stages are usually tied to a particular business function - R&D or Regulatory.What's currently missing is a Current Stage Name field that we can add to a Proof Approval report. This will allow us to track which stages have approved per approval round/version.
Description - Why is this feature important to you - If the label section of the field could be unique to each form then we could reduce the number of redundant fields created. How would you like the feature to work - The label section of the field could be unique to each form. Current Behaviour - When we require slight wording variations to a field for a form we must create a new field even though the basics of the field are the same
Description - How to report on parameter /category used in reports? Why is this feature important to you - As part of a clean-up activity in Workfront, it is pivotal to know what fields (parameters) have been used in report filters, other than on projects, tasks or issues. How would you like the feature to work - Category ID or Parameter ID to be introduced under Report's report. Current Behaviour - No such feature
Description - Today the Segmentation view has a table view of all segments created, while naming convention can help organise things what is really required is ability to create custom folders to organise Segments Why is this feature important to you - This feature will keep segments view clean and help user to look for relevant segments by category or job function How would you like the feature to work - A feature which allows you to create folders to organise segments, in addition an option within segmentation create view to save it to an existing folder or create a new for that segment Current Behaviour - This functionality does not exist today.
At this moment, Dutch is not a supported language in Workfront. Within our company, we have a need for having all standard Workfront fields shown in Dutch.
It would be very efficient to be able to change the name/label of a field that's in use in Marketo without first removing it from use. This would help create less fields and be scalable/save time when changing the field. Even a better option, if a field is created in SFDC and exposed to Marketo and the name/label is changed in SFDC, to reflect the field name change in Marketo automatically. Vote up for both or either of these ideas!
Allow Project Manager to restrict access to document folders. The PM could limit who has access to a folder that contains sensitive or confidential project documents even though users had access to the project and other folders with non-sensitive information.
Description - Is there a way to report on previous (Projects/Task/Issue) status' duration and to track when it got changed to the current (existing) status. Why is this feature important to you - For reporting and analyzing Project's health. How would you like the feature to work - Previous status duration option under reporting. Current Behaviour - No such feature exists for reporting
Hi, I would like to request more dynamic dropdowns in form building. Dropdown values would be populated from a data store or other source. Also, the ability to add to that data store via importing a csv. This dropdown would also have the option of letting the end user add a new value but not allow duplicates. I would also like to have multiple dropdowns use the same values. Like 'Movie Select 1' and 'Movie Select 2' pulling in values from the same 'Movie List Data Store' thanks, Kelly
Hi, New Workfront user here. The "Assignments" icon in the top-right shows the initials of colleagues who are working on a given request: But when I mouseover this (e.g. over the "AW" in the image above), I get a tooltip "You need access to edit this field" which obscures the tooltip explaining who the user is: Can these tooltips be positioned so as not to overlap? Thanks.
Recently, for a report, I successfully inserted my custom icons. The display on my monitor looked the way I wanted it.But unfortunately, when time came for me to print the report, the icons printed as URL instead of the Icons. Problem with Workfront's current icons - they are very small - more like tiny. They have only two kinds - Tiny colorful circles more like bubbles and tiny colorful flags. Even the colors are very limited in choice.When I insert them to my report, they are hardly noticeable and hence do not make the impact that I am looking for. My recommendations:- Workfront should increase the size of their icons.- Workfront should increase the types of icons available to the users.- Workfront should increase the choices of colors to choose from.- Workfront should give the users the capability of adding their custom icons to Workfront icon files or wherever they are stored.- And most importantly, Workfront should give the users the capability to print these custom icons as icons instead of as URLs.
In a large organisation with a secondary report suite the low traffic bucket has far reaching implications for data integriy. For example a primary report suite may not ever hit the low traffic limit and as such is able to accurately report on items such as url's and page names. However when you go to the secondary report suite which has many more values from other primary report suites we commonly find that items are bundled int he low traffic bucket. This creates significant reporting descepancies between the two report suites. Which means depending on what type of query and which report suite they are looking at they can get very different or simply missing data when comparing the two. As you can imagine consistency in data across primary and secondary report suites is key, in establishing trust in data and driving data's use through out the organisation. I believe for larger implementations the use of the low traffic bucket, undermines the entire implementation. My suggestion to Adobe is to remove this from all reports and products and report on the full data set regardless of size.
Description - After submitting a request and generating an issue, there would be the ability to require certain fields filled in prior to converting to a project. There is information you ask for at time of request that may not be known but you do want before it becomes a project, this would ensure it is collected. Why is this feature important to you - Governance to ensure proper information is collected prior to beginning a project. How would you like the feature to work - Similarly to the require checkbox which makes it required for submission, this would be an additional checkbox for required to convert. Current Behaviour - Issues can be converted and key information can be missing causing undue delays in the project.
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.
