@Tim Vasilovic‚ Derrick is part of the technology organization, so yes, the WB IT team was involved in implementation. While that solution created projects directly (effectively bypassed the project request form), there are some advantages to creating the request and then turning into a project. I'd advise reviewing the data created for requests, to make sure that you are not losing anything valuable from a metrics/KPI perspective. Regardless of the route you take (request to projects or directly to projects), the Workfront APIs are quite robust and enable pretty significant customizations.
One other thing to consider: using Workfront automations in concert with APIs to do some of the heavy lifting. This may make your custom UI more maintainable over time, as the APIs evolve over time and require regression testing with every new software release. While workflow automations should also be regression tested, there may be less chance that an automation will be broken due to feature depreciation, than an integration being broken due to a change in the underlying API contract.
So many more things to consider on this front, so I'd be happy to speak with you if you like. I'll be offline a bit in August, but you can reach me by email at nina@stirling-ecs.or.
Good luck with your project!
(and Hi @Derrick Villanueva‚ !)
