Workfront: Sync Claravine Data into Workfront

Rebekah Garner
Rebekah Garner
  • Updated

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: 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:
    mceclip0.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.
        mceclip2.png 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.
    mceclip1.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.
    mceclip2.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.
      1. 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:
        mceclip3.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.
      1. 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:
        mceclip4.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.

Comments

0 comments

Article is closed for comments.