Straightforward request: I am a big advocate of using Marketo's description fields when using any sort of asset that's in a Marketo tree—a local asset, program, campaign, folder, template, etc. This area allows you to put in key details, link your work back to ticketing systems, provide context for colleagues, and so on. However, as of today you can't search any data that's been put into a description inside the UI. For example, if I wanted to note that a certain Smart Campaign uses the form named A Cool Form with ID 1000, I might put in some text in the description like: "Processes A Cool Form (ID: 1000), assigns values, and sends an alert". However, if a user just searches in the tree for "A Cool Form", they'll only see the actual form asset named "A Cool Form". If the description data was also indexed in the search, the user could see not only the form but all related assets in one go. Could this data get additionally indexed into tree searches?
I am using a Fusion automation to send an update to any user that saves a new task into my main queue project. A checkbox should be added to the Queue Details when it is turned on as a queue to "Disallow new tasks" so that I don't have to be chasing after these users who don't want to save their task conversions into the right project. They should get an error when trying to save the task int a project that disallows new tasks. Anyone else need this? Please vote up. Cheers.
For years, the error message to someone who does not have access to a specific request queue is "This form is currently unavailable". This is just a small ask but can you PLEASE reword this to something that is a little more clear? Many new (and some more experienced) system admins still are fooled by the message and spend some time looking at custom form permissions, which are already convoluted. Rewording this to "You do not have access to this request queue" is more to the point and less confusing for the user and the admins.
Add recipient time zone scheduling to deliveries using recipient's location or explicit preference, e.g. nms:recipient/@timeZone.Deliveries gain another enumerated value in their scheduling time zone dropdown: Recipient time zoneWhen applied, deliveries will stagger sending across target population's timezones. so that everyone gets their emails at the same time on their clocks. E.g. Hawaii and New York recipients will all get their emails at 8 AM.
Description - Allow for creating audiences in the library from other previously saved audience library audiences. Why is this feature important to you - We do a lot of geo targeting and we have custom geo audiences set up for many markets. When we need to combine more that limit will allow (for targeting or for exclusion) we have to basically rebuild them all in one new audience. What a beat down.How would you like the feature to work - When building a new audience in the audience Library allow for the choice of 'rules-based' or 'existing audience'. This would also be great for combining multiple shared AAM audiences or you could have a third option of 'hybrid' that would allow you to combine rules-based logic with existing audiences to create a new audience. Current Behaviour -
We would like to submit an idea that would allow users to see Workfront Proof in Full-screen mode. The full-screen mode would eliminate pin this page gray area and allow a user to take over their entire screen
Description - Recently we shared a read-only workspace report for a critical application with our internal support team. The reason being so that they can monitor this application and proactively start looking into potential issues. By sharing the report with them we had to share access to some analytics components. However, when testing the access it looks like the 'Create Project' option is still available in Workspace. Ideally this could be restricted on certain user groups so that new workspace reports cannot be created by that group. The reason we would like this feature is to avoid non-analytics developers from creating reports that may be misinterpreted. Ideally they are only able to view the reports we choose to grant access to without the ability to create new workspace reports.Why is this feature important to you - Having this feature would help us ensure that workspace reports shared with stakeholders are truly read-only and so that we can restrict curation of analytics reports to developers onlyHow would you like the feature to work - in the admin console, add functionality to restrict user groups (or users) from being able to create new workspace reports when in analysis workspaceCurrent Behaviour - Currently users that are granted access to analysis workspace can create new workspace reports by default
It would be useful if you could Schedule an update on an object to be sent on a selected day and time to the users tagged in the update.
When you are trying to report on a queue, you only have the option to pull the requests/issues that were put into the queue in a Request/Issue Report, and then you have to create a separate report that will show the Projects/Tasks that were converted from those queue requests.Having a report that could incorporate both would be extremely useful.
This is a bit of an odd request, but hopefully I can explain this without making this too abstract. When working with email templates, there's no way to do dynamic calculations based on defined variable values. For example, if you were going to write some dynamic CSS for calculating size for a landing page, you might do something like: width: calc(100vw - 20px); in order to calculate the pixel width of the viewport width, minus 20 pixels. That sort of calculation can't be done with email markup in a widely supported way. However, other templating languages can support this sort of work. AMPScript's math functions can handle this sort of work for doing on-the-fly calculations for email. This technique can be used to enable certain dynamic features when paired with Marketo's template syntax, and I'm happy to provide private examples of how this would be used. Unfortunately, this is not a use case scenario where doing calculation inside Velocity and then having a token perform adjustment would work—this needs the ability to read from variables set in the email itself.
It would be much easier to manage large report views if (instead of having to have an erroneous amount of columns using sharecol=true), you could put HTML into the valueexpression property. valueformat=HTMLvalueexpression=IF(ISBLANK({somefield}),"<b style='color #FFF; background: #F00;'>NO VALUE!</b>", "<em style='color: 0F0;'>ENTERED</em>")Right now, that will escape all the HTML and print it as text, but it seems like a strange restriction since HTML in the value property is rendered out.
We would like to be able to add WF as a tab in a Teams Channel. Allowing team members to be able to quickly access the project in the same way we can other Apps.
If there was an error in a field calculation, the calculation methodology has been changed or the field has not been updated for any reasons before the project closure, the calculated field just crashed, there is no easy solution to fix it, we have to go ahead and open up projects one by one and that would distort the Project's Actual Completion date.Talking to the Support I had no satisfactory solution to fix my problem as the list of the impacted records is giant.We badly need this feature to make our reports reliable and to enable the report specialist to be absolutely sure that the calculations are correct.
Would like the ability to either add 0 hours to a task on the timesheet so a note can be attached to that task on that date Or the ability to post notes at task level on timesheet without logging hours.
Previous submissionhttps://one.workfront.com/s/idea/0870z000000PSdFAAW/detailSelecting this option"Send an invite email to this person"removes the optionOnly Allow SAML 2.0 AuthenticationWhen I create SSO accounts, our users do not get a much needed welcome email. Can you please allow both options to be selectable.Thank you!Drew
It seems not to be possible to display Document-specific custom forms on the Details screen of the document. Users have to navigate to the Custom Forms option on the left-hand nav bar and then select the form. Even then, it appears only on that section (Custom Forms). All other objects (can't promise I've checked every one) allow the display of Custom Forms on the object details screen and Documents should be the same.
Many SCRUM teams do not work with parent stories and subtask. SCRUM teams should be able to choose whether the storyboard shows horizontal swimlanes that are organized by story or if the board shows more like the KanBan view where there are only vertical swimlanes organized by task status. Our teams are losing too much screen real estate when grouping in horizontal, per story, swim lanes. It is common for an iteration to have hundreds of tasks for a team that spread across 30 different projects that each have multiple parent/subtask structures. It is impossible for users to quickly find their task within the story board due to the lack of search functionality in the board and the breaking down into horizontal swimlanes.
When proofing a file with more than one page in Proof HQ, the filename needs to be more prominent. As you can see from the attached images, little to none of the filename is immediately visible, making it difficult to work out which one we're reviewing, without hovering over the image thumbnailSee attached for more context
(Note that Campaigns = Projects)We have recently discovered the Campaigns I'm On/Campaigns I Own buttons that can be activated in a Layout Template (refer to Case Number 00260023).Currently this filter provides ALL campaigns and it is not possible to modify the filter to exclude 'Complete' campaigns.Is it possible to modify the underlying filter to exclude 'Complete' campaigns?
Currently, when a user has Show System Updates turned off, any user comments that are replying to a system update will also be hidden. We have experienced cases when a Designer receives a comment from a stakeholder but she can't find or see it because the stakeholder replied to a system update and the designer has Show System Updates turned off.
Imagine a world where you can combine comments from one proof to another seamlessly. In our model, we sometimes need to route the same projects to 2 depts at the same time. The ability to import comments from 1 proof to another would be game-changing.My ideal scenario will be if we're could import comments like you could combine comments from a PDF would be amazing.Another great advancement would be if Proof HQ would sort comments based on placement vs order of when the comment was made. Formatting text into proof could also save time and reduce the error rate too, especially in creating long reference blocks with itals, etc.
In the most recent update, 21.1, Workfront removed the ability to copy and paste the direct URL and share it with others. Users now have to navigate to the "Share Path" button with is extra clicks and confusing for our every day planners and our requestors. Additionally, this is not standard with how you share project, task, or document URLs, making the UX very confusion and inconsistent. Let's bring back the the URL path in the URL bar where it belongs. Thanks!
Today, there is no automatic way to set a Salesforce campaign that should be linked with a Program using only the REST API. However, when querying program information, both the linked sfdcId and its associated name are displayed. Would it be possible to update createProgramRequest/updateProgramRequest so an SFDC Campaign ID value can be passed? Ideally, there'd be an option a la the UI to auto-create an SFDC campaign in addition to setting a predefined value, but even having the ability to link pre-existing campaigns would be tremendously helpful.
Propose a toggle within the software to prevent this from occurring. This could be implemented in simple ways, such as the software simply prompting the user when they click the 'Open Proof' link with the question "Do you want to view the document or approve the proof?" then the software can direct them to existing code rather than having to reinvent the current code. This could be implemented in other ways as well without the need to reinvent the current code.For organizations that have tightly controlled and highly auditable proofing approvals, the auto-creation of the workfront approval stage when a user views a proof can create considerable extra work and audit risk.
We need to be able to disable daily digest emails. At the moment we are manually disabling them every time a new user is created. Its a workaround, but very manual and time consuming
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.
