Can we have an inactivity filter "Not Was Added to SFDC Campaign" in place for identifying leads that missed entering in a particular SFDC campaign?
Every time we need to develop a lead flow logic, smart campaigns are required in the first place. Sometimes we have to create multiple test campaigns for achieving the desired results. It would be best if we can have a Lead Flow Preview in place without having to run single or multiple campaigns while testing the logic. We can use dummy or real leads and see whether they'd pass or not through the smartlist criteria, choices, flows, etc without having to make a campaign live.
It would be great to see when an email asset was both created and last modified right in the Summary tab. I can find the info today using search but it would be so much nicer and less time-consuming to see it right on the Summary tab like we do for Smart Campaigns and Programs.
It would be handy to be able to have a "Test Flow" function when building Smart Campaigns that allows you to use either dummy data (that would theoretically satisfy the flow), or using real, database data (but have no actual consequences) BEFORE the Smart Campaign is activated (and affect real data). Something similar to how MS Power Automate, or Zapier etc allows you to 'test' an automation to see if the logic holds, prior to setting the automation flow loose on real data.
Please enable an option to send daily proof reminder emails on open proofs still awaiting decisions.
We just switched over to New WF Experience and we love it. I got very excited to see a place to change "Planned Completion" at the top right of the project header. However, the deadline is hard set to midnight, which makes the entire function useless to us, since it defaults the final task date to the previous day. Changing that hard setting from midnight to 11:59 pm, or some other late-night setting, would make this function jive with the task dates, and that would be invaluable. For example, I have a project whose Planned Completion is 8/1 and I want to change it to 8/30, I can go to "Planned Completion" and change that to 8/30 (which is super helpful not to have to enter the Edit screen, go to Overview and change it there). But since the new Planned Completion function defaults to 8/30 at midnight, the final task in my Tasks schedule changes to 8/29 instead of 8/30, and I have to go into Edit > Overview and change it to 11 pm anyway, which defeats the whole purpose.
In the "classic' WorkFront, we were able to File-->Print (or Cntrl-P) a timesheet for HR's archiving (paper or PDF). Now when we try to print in the "new" experience, the print out gets cut off after the first line and there is no way to print out the timesheet. Can you add back in that feature to export/print a timesheet in some way?
With respect to user account management, when SSO & Auto-provisioning is enabled - currently newly provisioned user accounts must be manually enrolled in the new experience.It would be helpful to have a setting that would allow all new users to be auto-enrolled with the new experience upon account creation.
It would be nice to see who the next task is assigned to that depends on your current task in the home view. When viewing the home task list, it would be helpful to have a field that shows dependent task assigned: First Name Last Name. This would help alert workers who to tag with questions or documents for the next task without having to go into the project and ladder up.
The proofing functionality recently became available in our instance and everyone who held a Worker license or above was automatically given a proofing license. Due to this, they have the ability to create proofs from an object's Documents tab which may cause confusion if they stumble upon the functionality. We'd like the ability to disable the following proofing buttons that appear inside of the main Workfront application. There is not currently a way to do this.
It looks like there's been some recent improvements to Marketo Engage's form accessibility around validating fields. This is great! However, there are some small tweaks that need to occur in order for these new items to perform in a way that's stricter to WCAG standards. 1. The aria-describedby attribute for inputs should only be inserted at the time that the validation message itself is added to the DOM; otherwise, the attribute has nothing to reference. 2. Items displayed in .mktoErrorMsg should additionally have aria-live set to assertive. 3. This isn't strictly accessibility-related, but when looking at validating form fields against behaviors, I'll also use setCustomValidity() and set the required attribute upon validation if validation fails for required fields. This can help with CSS/JS presentation if the Marketo customer uses custom behavior/visuals elsewhere.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.