Fusion to expand the functionality of Workfront - aligning datasets in Workfront

Hey Richard - Just wanted to remind you that Fusion is just a connector tool, so Fusion itself couldn't do the report. But you could connect to a reporting tool.

We don't use Fusion, but we have an integration where we bring info from WF and our financial tool into a SQL database and then use SQL Reporting Services to create our reporting and dashboards.

Richard - you might want to talk to your Workfront reps and ask about a demo of the New Reporting Experience they are working on. My understanding is that the goal will include being able to report on multiple object types in one report.

Although I'm also curious to hear from others about the learning curve of Fusion from a non-dev background.

Hi Richard, we love Fusion and use it a lot to enhance functionalities in Workfront. As the reporting goes, we add calculated values (e.g. total amount of approved / unapproved hours) in a nightly run on the project and task to get a little be more out of the "cross-object" reports. But as Heather said, there is a new reporting coming and the preview I've seen was awesome. I only hope that it will be included in our licenses and not yet another add-on we have to buy...

I'm sure the "new" reporting tool is a long way off so for more immediate needs you may need a developer to pull the WF data in to a SQL database as Anthony mentioned. I've done this since day one of our Workfront implementation. Reporting possibilities are limitless using this method. You can also do away with finicky (and limited) kickstarts for importing data. Puts and Posts are also possible, allowing you to update records en masse or create new ones.

I'm also a bit concerned hearing that there is no text mode in the new reporting tool. There will always be something we want to do that Workfront didn't think of and that's where text mode comes in really handy.

Thanks for the context @Matt Thomas‚!

@Randy Roberts‚ (noting, yep, threadjack accomplished...), I was teleported back in time when I read your but-whattabout-textmode concern, above, as that was among my very first inquiries to Matt when we first met in person just over a year ago, which I then underscored by introducing him to some of our textmode aficionados from here on Community. Really, a bit unsportsmanlike on my part, in hindsight.

However: since then, thanks to some time having passed for Matt to assemble his team and acclimatize, we've now spoken many times, and I've had several opportunities to see where New Reporting Experience is headed, including (just last week) being among the first round of Beta testing. In short, I am impressed and excited about where Matt and his team are headed, and have a Project Status Report in mind that I'm going to use as a yardstick for cross-object reporting (more on that here, for those interested). So, noting that the current Workfront reporting has been here even longer than me, I encourage you to stay tuned, and rev up your hopes for Something Good.

There is one other huge point I'd like to mention: in addition to Matt's above aspiration/reassertion about text mode, one of the best things I heard a few meetings ago is that he and his team recognize and are planning for the ability to allow users (e.g. SysAdmins) -- when the right time comes -- to convert a classic report into the New Workfront Experience report. That. Is. Huge.

Details to come still (Matt, any you can share at this time...?) but definitely one I'm paying attention to, and plan to leverage.

Regards,

Doug

While I certainly have strong opinions on the possible deprecation of text mode, I will bring this thread back to the Fusion question.

I find myself using the Fusion hammer on more and more Workfront nails. If you take time to learn how to use the API, it becomes hyper-capable. It absolutely can compile your project/task/issue data into single CSV files.

We use it to:

• Automatically manage a robust request queue setup that involves 8 request queues, ~150 Topic Groups, and ~2,200 queue topics/routing rules. On any given day, we may retire up to 5 Topic Groups and 75 Queue Topics, and replace them with new Groups, Topics, and Routing Rules - Fusion does it all for us using status triggers and data from custom forms.
• Configure request assignments and access based on data in the request custom form.
• Manage requests that are copied into Workfront from another system via webhooks, attach custom forms and move the request to its relevant project based on data in the request.
• Ensure our "universal" custom forms are attached to all object types - projects, requests, documents, users, anything; even if a user is not following a process that would otherwise ensure the form is attached.
• Automatically configure newly auto-provisioned users with some basic profile updates, and send them a welcome email that explains what they should do next and where they can get internal support.
• Overwrite a user's name that is updated by Active Directory every time they log in with their preferred nickname.
• Automatically put projects into their correct Portfolio and Program based on the request from which the project was converted.
• Enhancing the update stream and object details with data that isn't ordinarily available, such as who/when/what template(s) have been applied to a project (because Workfront only tracks the first template applied); or pushing custom data, updates, and statuses from one object to other objects that are not systematically related to the original record, but the work is related and stakeholders have an interest.

Some things I have in development are:

• Copy object attributes that are not reportable (or have limited report functionality) into tasks which can be easily reported on.
• Custom project sequence numbers based on the working team (each team has their own set of consecutive short project numbers, prefixed with their team code)
• Monitor a shared excel workbook for new expense entries, then push that data into the relevant Workfront record.
• and a million more for which there is never enough time.

As far as intuitiveness and learning curve of the tool, my own opinion is that it's moderately difficult for anyone that is not an experienced software engineer (which I am not), but if you're willing to invest the time in self-learning (including concepts and skills not covered in the Workfront provided training), the payoff in new efficiencies and capabilities is absolutely worthwhile. So many things that Workfront couldn't do in the past suddenly become possible, you can automate a ton of system administration/housekeeping, and you can start saying "yes" to a lot more requests. Start with simple builds, then as you master those you can begin to increase the complexity and learn what you need when you need. The more you build, the more opportunities you will recognize to use the tool that you might never have considered in the past.

In short, go for it.