Note that the following documentation is an example set of instructions for how to customize the Claravine provided blueprint for you to connect your Workfront project to a Claravine template. Workfront will need access to the Claravine API in order to sync data from Claravine into Workfront. Different teams can leverage your Workfront data to streamline and automate with precision: by generating standardized campaign tracking codes, integrating and automate campaign operations, and enabling performance measurements from end to end, across channels.Ĭlaravine offers a solution with Workfront using Workfront Fusion and the Claravine API. Your customized Fusion Blueprint passes data -like a project, dataset, or transaction ID - between Workfront and The Data Standards Cloud, unlocking access across the organization. So all your teams do is use Workfront as normal - except they get standardized file, asset, and campaign names automatically, since Claravine powers data standards behind the scenes. While your teams fill in and save core task fields like they always do, The Data Standards Cloud generates a name in your custom format and populates the designated Workfront fields. Standardize naming conventions in Workfront automatically by configuring a pre-built Fusion Blueprint to fit your Workfront scenarios and connect it to The Data Standards Cloud.Integrating workflow data across and beyond the Adobe Experience Cloud ecosystem with Claravine, enables you to:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |