Now that we have a OneCloud Workspace setup and connections to Workiva, let's create a Chain.

Step 1: Create a Chain

  • From the OneCloud Home, select the "DEV" Environment.

  • Add a new Chain by selecting the green (+) button.

  • Name the Chain "Load data to Wdesk".

  • Add a variable "base-url" with the value:

    https://s3.amazonaws.com/onecloud-demo
    💡 Copy the above URL and paste into the variable field.

  • Add an email Chain Notification by clicking the message icon.

  • Set the condition to "Success".

  • Add recipients by selecting from the drop-down list.

    📓 Only receipts who have access to the chain can be added.

  • Save the Chain.

Step 2: Start with Command Group

  • Set "Command Group" as the starting Command.

  • In the Available BizApp section, select "Command Group".

    💡 Use the Find tool to search for "Command Group.

    • Double-click the icon, which will auto-load the Command into the Chain Start circle.

      📓 Alternatively, click-and-drag the icon onto the pallet. Then move the icon in the Chain Start circle. The Chain Start will show a plus (+) icon indicating that the command may be placed at the start of the Chain.

Step 3: Add a Command to Retrieve Data

Add a data retrieval Command.

  • In the Available BizApp section, select HTTP ➡️ GET.
    💡 Use the Find tool to search for "HTTP" and then search for "GET".

  • Add the Command GET by clicking-and-dragging the icon onto the pallet.

  • Connect the Commands.

  • Rename the Retrieve Data Command "Get Transactions", by double-clicking it.

    • Under "Basic Info", type "Get Transactions".

  • Scroll down to input the URL to be used in the GET Command.

    • Use the variable selector and choose the chain variable "base-url" by clicking on the icon (< >).

    • Add the character "/".

    • Next use the variable selector again and add the Workspace Variable "data-type".

    • Add the character "/".

    • Finally, add the filename "SAMPLE_TRANS.csv"

  • Click save.

📓 On String Concatenation:

To concatenate strings in a OneCloud field, be sure to have the field selected and simply add the characters or variables as required.

Step 4: Add a Command to Preview the Data

  • Add the command File Utilities ➡️ List File Content to the canvas.

  • Connect the two Commands.

  • Double-click the "List File Content" Command to make some changes.

  • Give the Command the name: "Preview Data".

  • Set the File Name to the Response

    • From the left-side panel, select the 🔽 to the right of "Get Transactions", then choose "Response" under "Command Details".

  • Set the Preview Lines parameter to 15.

  • Save the Command.

📓 If there is no Connection listed when editing the Command, back out to the Connections tab on the left-side panel. Select the File Utilities 🔽 , click "Edit", and enable the Connection Environment for Sample Workspace for Workiva.

Step 5: Create Workiva Spreadsheet

Create a Workiva Spreadsheet in Wdesk to load the retrieved transaction data.

  • Add the command Workiva ➡️ Create Spreadsheet.

    💡 Search for the Workiva BizApp, click it, then scroll down to the Spreadsheets subcategory.

    • Click-and-drag the Command to the canvas.

    • Connect the "Create Spreadsheet" Command to "Create Spreadsheet".

  • Rename the Command: "Create Workiva Spreadsheet".

  • In the Name field, enter "SAMPLE_TRANS_" and then use the picklist on left-side panel to variable picklist to concatenate the Chain.ExecutorId.

    💡 Runtime 🔽 Chain.ExecutorId

  • Save the changes.

    📓 Adding the system variable Chain Executor ID, guarantees that the creation of the spreadsheet will be unique.

Step 6: Create Workiva Sheet

Add a sheet to the Workiva Spreadsheet that was created in the previous step.

  • Add the command Workiva ➡️ Create Sheet.

    💡 Search for the Workiva BizApp, click it, then scroll down to the Spreadsheets subcategory.

    • Click-and-drag the Command to the canvas.

    • Connect the "Create Spreadsheet" Command to "Create Sheet".

  • Give the command the name: "Create Workiva Sheet".

  • In the Spreadsheet ID field, use the variable selection and the ID value under Spreadsheet Metadata.

  • In the Name field add a name. In the example, use "TRANSACTIONS".

  • Save the changes.

How do I get the Spreadsheet ID?

The Workiva spreadsheet ID is in the URL of the page when logged into Workiva Wdata.

Step 7: Load Spreadsheet Data

Add the Overwrite Sheet Data Command to the Chain.

  • Choose Workiva ➡️ Spreadsheets ➡️ Overwrite Sheet Data.

    💡 Search for the Workiva BizApp, click it, then scroll down to the Spreadsheets subcategory.

    • Click-and-drag the Command to the canvas.

    • Connect the "Create Spreadsheet" Command to "Create Sheet".

  • Use the variable selection tool on the left-side panel to:

    • Add a Spreadsheet ID value

      • Command 🔽 Create Workiva Spreadsheet 🔽 Spreadsheet Metadata 🔽 "Id"

    • Add a Sheet ID value

      • Command 🔽 Create Workiva Sheet 🔽 Sheet Metadata 🔽 "Id"

    • Command 🔽 Get Transactions 🔽 Command Details 🔽 "Response"

      ⚠️ Be sure to choose the correct IDs.

  • Use comma as the delimiter.

  • Save the changes

Step 8: Publish & Run the Chain

Publishing is an important feature in OneCloud. Chains must be published, before they can be run. A Chain and its respective Commands will not be executed otherwise. Whether making one alteration or many, the Chain must be published every time a Chain or Command is edited.

Publish ➡️ Execute ➡️ Run Chain.

  • To publish a Chain, click "Publish" near the upper-right corner.

  • Optionally, add a Publish Chain Comment. For this example, leave it blank.

  • Once published, the "Execute" button becomes active. Click it.

  • Once executed, the "Run Chain" button is activated. Click it.

  • The Chain will animated when it is running.

  • Click on the Anaplan Upload File Command.

  • When the Chain has been run, the outputs will be available to view.


📚 Related Topics from this Section:

Chain & Command Notifications

Chain Variable

Workspace (Configuration) Variables

HTTP Commands - GET

File Utilities Command - List File Content

Command Outputs

System Variables


Did this answer your question?