Build better products with our product team
I created a wildcard report that calculates the number of days the individual has selected as time-off. To have a more accurate calculation I used the expression WORKMINUTESDIFF so that it would not include any days that are Schedule exceptions (aka holidays) since a lot of people will take off around an extended weekend. I noticed there were incorrect calculations for some of my users and after research discovered that WORKMINUTESDIFF only refers to the Default schedule instead of the user's schedule.I wish there was an easier way to make a time-off report that did not involve so much text mode deciphering and could cleanly calculate John Smith has taken 10 PTO days this year.
I'm trying to see the differences between two Platform requests. The meaty part of the Platform request, which I control as an implementer is the "events" area of the post body. This is where all of my custom name/value pairs I am sending are contained. In the current formatting of the Debugger, it's nearly impossible to compare two requests side by side because this info is displayed in a tiny cell. You would have to click one cell, copy the JSON object then click the other cell and copy the JSON object and then compare the two using some other tool. Please make it easier to see the differences in the request between these two fields. I suspect this is a challenging task in all of the tools that have switched to sending data in the post request body (e.g. at.js 2.x) instead of as query string parameters.
It would be helpful if all system managed field mapping, such as the Owner fields, were displayed in the Field Management. It seems odd that they are mapped but not displaying as mapped under the "CRM field mapping." In order to clear up any confusion, ideally those fields would display the associated mapping.
It would be nice if a project is a predecessor task on a 2nd project, that the predecessor task % complete field automatically update as it's linked project percent completion progresses. for example: Project 1 - is currently at 50% completion, a few tasks within this project are completed and the % completion changes to 60%Project 2 - has a task (Project 1 as an enforced predecessor), as the activity in Project 1 causes it's % completion to update to 60%, it would be nice for the task in Project 2 to automatically update to 60% to coincide.
Problems often arise with actions written in another language. An additional language file could solve this problem, for example.I have installed the German version of Photoshop. But many actions are offered in English. It would be practical to use them here without problems.So either to be able to install a complete second language file, or to be able to switch quickly, or to have an integrated translation of the corresponding terms.I apologize for a possibly bad English, but I use a translator, because I don't know English.
Would like to be able to build a report showing report creation date. We would use this as a KPI report indicating how we are utilizing the information housed in Workfront.
Many of our users select and copy different field values from project details to paste into other programs. A 'copy to clipboard' button next to each field would be a great time saver.
It would be so useful if we could include multiple values inside of the Member of Smart List filter, the same way this is possible for Member of Program and Member of List filters. It can get complicated if we want to easily pull in multiple smart lists inside of 1 smart campaign without listing a filter for each one.
Right now, there is no accurate way to determine if a file is identical, but uploaded with a different name inside a Marketo instance. While you can pull file size and try to 1:1 compare sizes to understand if a file is identical, this is an imprecise method. By storing some sort of checksum hash (MD5, SHA-2, etc.) with an asset, there's now several options for handling duplicate files. Uploads via API or UI could use the checksum to prevent duplicate uploads, and exposing the checksum via API (or even UI in some way) would allow for faster and more accurate detection of existing duplicate files.
Our pages have always showed up on Reports with the intended characters themselves, but in Workspace we get the raw code instead of special characters in things like page name / page title, so the display is ugly. Logically we'd fix this by changing the data source or processing, but the reality is that we have tens of thousands of site pages and years of data. Changing our data source or rule process to clean up the many pipes, dashes, ampersands and other special characters would lead a bunch of overhead and 2 years of transition time between old and new pages and titles (our long tail is... long). The activities around this would require major, sustained effort in order to:Get reasonable data on most popular content where top page views aren’t splitting counts of the same page between old and new titlesDo analysis like year over year comparisonsMaintain internal enterprise training and communications reminding stakeholders to use whatever workaround we put in place while doing analysis for those 2 years:probably a SAINT classification name value for all name sand titles work rather than the usual ‘page name’ or ‘page title’ variable requiring setting up daily automation for adding dozens of new titles to the classification, just swapping characters where code appears. The inability of Workspace to render characters instead of presenting the raw code in the display seems like a product issue, since it is out of step with the way content was presented in other Adobe interfaces (Reports). Since Workspace has way outstripped Reports in sophistication and has been made the go-to tool for data democratization and direct stakeholder use, would it be feasible and reasonable to ensure that Workspace displays actual characters rather than code versions, the way Reports does? Thanks for considering.
I would like to create sub panels to better organize information. Collapsing panels is an important feature to me to allow a clear overview of the reports available. Creating a sub-panel under a main panel would also help in better structuring reports.
Look at this screenshot: Did you know that you can edit the schedule's time by clicking the "2:53 PM" time? I bet you didn't. Because the "2:53 PM" black text looks just like the "Feb 11 2020" black text, just as it looks like the black text every where else. So your first reaction was "that is static text, not a link". Adobe, for a creative company, this UI design is really backwards! Stop hiding user-actionable links/buttons behind a "beautiful" design. A design fails if the user doesn't understand how it is supposed to be used. That is Design 101. Make links look like links, and static text look like static text.
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