Search

Claravine + Adobe Workfront Solution

Rebekah Garner
Rebekah Garner
  • Updated

Integrating workflow data across and beyond the Adobe Experience Cloud ecosystem with Claravine, enables you to:

  • 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. 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.

    w1.png

    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.

  • Collaborate across teams seamlessly. 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. 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.

  • Sync Claravine Data Into Workfront

    Claravine offers a solution with Workfront using Workfront Fusion and the Claravine API. Workfront will need access to the Claravine API in order to sync data from Claravine into Workfront. 

    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.

    In Claravine

    1. Configure the Claravine template schema to match the fields in your Workfront Custom Form. An example of fields in Workfront Custom Form below:
      w2.png

    2. In order to import data from Claravine into Workfront, you will need access to the Claravine API. Request access to the secure REST API from your CSM. Once enabled, please reference our Knowledge Base article on the Claravine API to create your API Key and Secret.
      Your API Key and Secret are only displayed during initial creation and cannot be recovered if lost. If the secret is lost, then you’ll need to delete the old Key and Secret and create new ones.

    3. Your Claravine CSM will send you a JSON file which contains your blueprint which will need to be imported into Workfront in step 5.

    In Workfront

    1. In the Workfront Fusion instance, navigate to the Scenario tab on the left side menu.
      w3.png

    2. Click the Create a New Scenario button in the top right-hand corner.

    3. Click Skip past the orange services to integrate the page to the blank new scenario.

    4. Click the …More” menu.

    5. Click on Import Blueprint to browse to find the blueprint for the “ConfirmDataWasPosted” scenario or “Scenario2” and import it into the blank Scenario space.
      w4.png

    6. Once the Scenario has finished importing, rename the Scenario something unique which will help you keep track of what is going on in the workflow.

    7. Create the first module CheckForData data store.

      You should already have your data store set up at this point since it’s imperative that this Scenario will reference the same data store set up for our PostingToClaravine scenario. Example below:
      w5.png

    8. Connect your data store by selecting from the browse arrows; your data store will appear here.

    9. Make sure the filters for DatasetUUID and TransactionUUID exist and are set up properly.

    10. In the SetVariables module, set your Key Value and Secret Value from your Claravine API account.

    11. In the GetStatus, module make sure to check that your dataset and transaction UUID for the Claravine template are referenced properly.

    12. Update the connection for all the update record modules left in the scenario to the SystemAdminWorkfront connection you set up in scenario 1 for Importing Data into Claravine.

      Make sure to also update the ID field to the Project ID being referenced in your check for Data module (if it’s a transparent value you will have to select it manually and delete the transparent value). Example below:
      w6.png
    13. After setting up the connection, make sure to set up all the data stores so your data is properly deleted after running.

    14. Click Save.

    15. Run a test case by first creating a project and making sure the create dataset in Claravine scenario has launched.

    16. After a successful run you can turn on the scenario and set the time interval to 5 minutes (which is the lowest it will go) and click save.

  • Import Data Into Claravine

    Claravine offers a solution using Workfront Fusion and the Claravine API. Workfront will need access to the Claravine API in order to import data from Workfront into Claravine.

    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.

    In Claravine

    1. Configure the Claravine template schema to match the fields in your Workfront Custom Form like the example below:
      w7.png

    2. In order to import data from Workfront into Claravine, you will need access to the Claravine API. Request access to the secure REST API from your Claravine CSM. Once enabled, please reference our Knowledge Base article on the Claravine API to create your API Key and Secret.
      Your API Key and Secret are only displayed during initial creation and cannot be recovered if lost. If the secret is lost, you’ll need to delete the old Key and Secret and create new ones.

    3. Your Claravine CSM will send you a JSON file which contains your blueprint and will be imported into Workfront in step 7 in the next section.

    In Workfront

    1. In the Workfront Fusion instance, navigate to the Data Stores tab on the left side menu.
      w8.png

    2. Click the Add Data Store button to create a new data store in the top right-hand corner.
      • a. Title your data store something unique.
      • b. In the Data Structure section, click Add to create a new data structure.
      • c. In the Data Structure module; enter a data structure unique name.
      • d. Click Add item in Specification. 
        • Select ProjectID, click Add.
        • Select DatasetUUID, click Add.
        • Select TransactionUUID, click Add.

      • e. Click Save to save the Data Structure.

      • f. In Data storage size in MB field set data storage to 1MB; as scenarios get processed the data will be removed from the store so it does not need to be too big.

      • g. Click Save to save the Data Store.
        w9.png

    3. Navigate to the Scenario tab on the left side menu.
      w10.png

    4. Click Create a New Scenario. Click Skip past the orange services to integrate the page to the blank new scenario.

    5. Click the … More menu.

    6. Click on Import Blueprint to browse and find the Claravine JSON file. Click Save.
      w11.png

    7. To set up your Webhook to trigger for your inciting event, go to the Trigger module and click Add.
      Make sure you are signed into Workfront in a different tab as a system administrator.
      w12.png
      • a. Title your webhook something unique to the Scenario.
      • b. In theConnection section, click Add to add the Connection Name "SystemAdminUserClaravine”. Click Continue.
      • c. The connection wizard will prompt you to input your organization’s Workfront in the format {organization}.my.workfront.com. Click Continue.
      • d. On the “Allow Application” modal, click allow access to access your Adobe Workfront Account.
        To do this you should have a separate tab opened with Workfront as a system administrator. 
      • e. Once connected to Workfront, select the inciting event type and event filters in the Record Type section. The  inciting event will launch the Scenario and whether the Record Origin should be a “New”, “Updated”, or “New & Updated” event. 
      • f. It’s recommended that you pick a task as the inciting event. In our example scenario we launch based on the update of a task called Push to Claravine from Workfront.
      • g. You will need to make sure this task is part of your Workfront project which contains the form with all your metadata.
      • h. Optional: You can choose to pick an event filter for your record which will launch the event such as a specific name for a task when completed. This is where you would list “Push to Claravine” as a task name.
      • i. Click Save to save the webhook. Example below:
        w13.png
    8. If you chose to go with something other than a task for your webhook trigger, make sure to change the task complete filter or remove it depending on your use case.

    9. In the Set API module, add your Claravine API Key and Secret. Click Ok.
      w14.png

    10. In the Get Custom Form Details module, click Add and select the SystemAdminUserClaravine connection created in step 7b. In the Get Custom Details module, you must pick the custom fields (example fields in the screenshot below) that align to your template in Claravine from your custom form in Workfront.
      • a. Make sure to pick all fields.
      • b. Pick the project name.
      • c. Workfront custom form fields will appear as DE:Form Name.
      • d. Click OK. Example fields pictured below:
        w15.png

    11. Note that in the GetDataset module where you will be making your API call to retrieve your Claravine template UUIDs (Datasets ID) if you have multiple IDs, you will need to properly map them.
      • a. Right-click and Run This Module Only.
        w16.png
      • b. Enter the Claravine API URL (https://api.claravine.com/v1/datasets) as well as your unique Key and Secret created in Claravine on hand.
      • c. In the Key field, enter “x-claravine-key” and in the Key Value field enter your unique key generated in Claravine.
      • d. In the Secret field, enter “x-claravine-secret” and in the Secret Value field enter your unique Secret generated from Claravine.
      • e. A successful completion will allow you to see the data in the bubble that appears above the module.
      • f. Clicking into this bubble under OUTPUT and in DATA and DATASETS you will be able to see all the different Datasets and their corresponding template names once you expand the collection(s).
      • g. You will need to make sure you map the correct dataset for each scenario and select the correct custom form details that match to the dataset we are pointing to in Claravine.

    12. In the Set Rows module, you will define the rows as they line up according to your Claravine template schema to match in the same way the example Module is set up. Rows must be input in quotations and separated by commas. Example below:
      w17.png

    13. Link your Data Store to the Data Store you created in step one and click add.
      • a. Map your newstate:project Id from the webhook module to the project id spot. 
      • b. Map the dataset UUID to the datasetUUID and transaction UUID to the transaction UUID.
      • c. You will be able to map datasetUUID after running the module in step 11 however you will have to wait to map transactionID until you do a test run after setting everything up once that is done you can go in and map transaction id from “GetTransaction” under data and in datasets you will select the UUID to map.

    14. In your Unauthenticated Message module add your connection which you set to connect to your Workfront.
      The Unauthenticated Message should be mapped to the same custom field where your Status will go.

    15. Set up the Error Message Connection with the same connection to your Workfront as well.

    Once set up, run the scenario once so that you can get some of the required metadata which will map to your dataset.

    1. Logout of your system administrator account and log in as a different user for this step.
    2. Run a project making sure all custom form details and the correct “Push to Claravine” task are set up.
    3. After running the scenario successfully you can update the transactionUUID field in your data store.

Comments

0 comments

Article is closed for comments.