It appears to be a JSON encoding. You could likely do some testing and play with things to figure out how you'd want to do it. Appending would likely be as simple as just adding to the blocks array and republishing.(I haven't tested this, just speculating based on the structure that I'm seeing he...
Yes, if you have the report built, you can use the "Text Mode" variation to pull that in using <objcode>/report. It's a great way to leverage Reporting to build what you want and then the API to extract to other systems.
Pulling data from Workfront is going to be best done via a report or a search operation. Then aggregate that data into a CSV. Then upload to your downstream system.Here's an example using SFTP as a destination. You'd need to modify, of course, for your needs.(Standard disclaimer: not tested, use ...
This is how we do it, too, though via Google Sheets (sorry, Adobe). We also use LucidChart or other Visio-like tools for flow diagrams, UML sequence diagrams, etc. These are especially helpful for the Fusion scenarios.
DescriptionWe have LOTS of reports with which our users engage on a regular basis. To help onboard new users and ensure existing users can easily consume new reports, we need some kind of way to provide the user with in-system instructions and tips/tricks/reminders about specific reports.Why is thi...
You can explore the APIs available via https://developer.adobe.com/workfront/api-explorer/. If you search for "User", you can find a few options, like "User Preferences", etc. I don't know all the various options that exist, but you may want to try a few Fusion Custom API calls to the various endp...
Thanks, yes, I'm aware of this. We've updated the "disable after X errors" value from 3 to 9999. Hopefully this will help reduce the impact of events.There is still a functionality/feature gap around setting a scenario to NEVER be disabled and/or monitoring the Fusion scenario's state via APIs or ...
Thanks for the reply. I'm aware of how to add error handling for a specific module with routers for various paths of handling. What I'm trying to avoid is needing error handling on EVERY module. These can be very complicated and large scenarios and adding error handling everywhere makes the modul...