Workiva Support Center

From Chain Builder, you can create a chain to download data from Enablon®, such as your greenhouse gas (GHG) emissions for Environmental, Social, and Governance (ESG) or sustainability reporting. 

Prerequisites

To build this chain, you'll use these core connectors:

• HTTP Request connector
• File Utilities connector
• XML connector
• Workiva connector, if you need to use the data in a spreadsheet or Wdata table

Note: All of this chain's commands use the default CloudRunner. No GroundRunner is needed.

To run the chain, you'll need details from Enablon to access the data:

• The Enablon Simple Object Access Protocol (SOAP) Application Programming Interface (API) endpoint to use to download the data
• The ID of the Enablon environment to access
• The user name and password to use to access the environment

Step 1. Create the chain

1. From Chains, click Create, and select Create chain.
   
2. Under Setup, enter a name and description to help identify the chain and its intent.
   
3. Under Variables, add variables for the Enablon details required to access the data:
   • Endpoint

     Tip: For the Endpoint variable, enter a default value of ExportData or, to download the data in a 64-bit encoding format, ExportBinaryData.

   • Environment
   • Username
   • Password
4. Click Save.

Step 2. Start with the Runtime Inputs trigger event

To filter the output each time the chain runs, start with a Runtime Inputs event to prompt for the criteria of the data to download.

1. Move Runtime Inputs from under Trigger Events to Start.
2. Select the Runtime Inputs event, and click Edit.
   
3. Add the inputs to request each time the chain runs:

   Display name	Type	Required?
   Report period start date	DateField	Yes
   Report period end date	DateField	Yes
   Campaign	TextField or DropdownField: TextField, for an open text field DropdownField, to select from a specific list of options	Yes
   Entities	ArrayField	Yes

4. Click Save.

Step 3. Add an HTTP Request connector POST command

To retrieve the data from the Enablon endpoint, set up an HTTP connector POST command:

1. Under Connectors, click HTTP, and move the POST command to the canvas.
2. Drag a link from Start to the POST command.
3. Select the POST command, and click Edit.
4. Under Command properties, select the HTTP connector to use.
5. Enter the command's properties:
   
   

   Property	Description
   User name	Select the Username variable under Chain.
   Password	Select the Password variable under Chain.
   Show response	Check this box.
   URL	Select the Endpoint variable under Chain.
   Content type	Enter text/xml.

6. In Body text, enter this Extensible Markup Language (XML) syntax:

   <soapenv:Envelope  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enab="enablon">
     <soapenv:Header>
       <UserInfo xsi:type="wsdl:AuthHeader" xmlns:wsdl="http://enablon/wsdl/">
         <EnaHomeSite xsi:type="xsd:string">[Environment]</EnaHomeSite>
         <EnaUserName xsi:type="xsd:string">[Username]</EnaUserName>
         <EnaPassword xsi:type="xsd:string">[Password]</EnaPassword>
       </UserInfo>
     </soapenv:Header>
     <soapenv:Body>
       <enab:ExportData soapenv:encoding:Style="http://schemas.xmlsoap.org/soap/encoding/">
         <Table>/sd/Entities/Data</Table>
         <FolderId>0</FolderId>
         <Fields>FolderPath|ReportingPeriod|Ref|IndicatorName|ValueNumber|LocalUnit|ValueList</Fields>
         <Filter>ReportingPeriod in ([ReportPeriodEndDate],[ReportPeriodStartDate]) AND Campaign in([Campaign]) AND Entities=[Entities]</Filter>
         <CSVSeparator>2</CSVSeparator>
         <FormatOptions>25</FormatOptions>
         <FormatType>3</FormatType>
         <ExportOptions>8192</ExportOptions>
       </enab:ExportData>
      </soapenv:Body>
    </soapenv:Envelope>

7. Update the XML syntax with the runtime input and chain variables:
   • In the header, replace [Environment], [Username], and [Password] with their respective variables under Chain.
   • In the body, replace [ReportPeriodEndDate], [ReportPeriodStartDate], [Campaign], and [Entities] with their runtime inputs under Trigger.
8. Click Save.

Step 4. Add File Utilities connector Find and Replace commands

To prepare the downloaded XML data, add File Utilities connector Find and replace commands to fix the angle brackets and pipes.

Tip: To easily differentiate the Find and replace commands, enter names to identify the character each command fixes, such as "Find and replace start angle brackets" or "Find and replace pipes".

1. Under Connectors, click File Utilities, and move the Find and replace command to the canvas.
2. Drag a link from the POST command to the Find and replace command.
3. Select the Find and replace command, and click Edit.
4. Under Command properties, select the File Utilities connector to use.
   
5. Enter the command's properties, and click Save:
   

   Property	Description
   Source	Select the Response output of the POST command.
   Find	Enter <.
   Replace	Enter a start angle bracket (<).
   Find syntax	Select Exact.

6. Under Connectors, click File Utilities, and move another Find and replace command to the canvas.
7. Drag a link between the Find and replace commands.
8. Select the new Find and replace command, and click Edit.
9. Under Command properties, select the same File Utilities connector.
   
10. Enter the command's properties, and click Save:
    

    Property	Description
    Source	Select the Replaced result output of the Find and replace command.
    Find	Enter >.
    Replace	Enter a start angle bracket (>).
    Find syntax	Select Exact.

11. Under Connectors, click File Utilities, and move another Find and replace command to the canvas.
12. Drag a link between the second and third Find and replace commands.
13. Select the third Find and replace command, and click Edit.
14. Under Command properties, select the same File Utilities connector.
    
15. Enter the command's properties, and click Save:
    

    Property	Description
    Source	Select the Replaced result output of the second Find and replace command.
    Find	Enter >.
    Replace	Enter a pipe (|).
    Find syntax	Select Exact.

Step 5. Add an XML connector Element List to CSV command

To convert the downloaded XML to tabular data, add an XML connector Element list to CSV command:

1. Under Connectors, click XML, and move another Element list to CSV command to the canvas.
2. Drag a link from the third Find and replace command to the Element list to CSV command.
3. Select the Element list to CSV command, and click Edit.
4. Under Command properties, select the XML connector to use.
   
5. Enter the command's properties:
   

   Property	Description
   Source	Select the Replaced result output of the third Find and replace command.
   Path to root	Enter //Document/Record.
   Preview result	Check this box.

6. Under Columns, add the column name and XPath for each element:
   
   

   Column name	XPath
   Period	/ReportingPeriod
   Indicator	/Ref
   IndName	/IndicatorName
   NumValue	/ValueNumber
   Unit	/LocalUnit

7. In Multi-value delimiter, enter a comma (,).
8. Click Save.

Step 6. Add a File Utilities connector Create File command

To create a comma-separated values (CSV) file from the tabular data, add a File Utilities connector Create file command:

1. Under Connectors, click File Utilities, and move the Create file command to the canvas.
2. Drag a link from the Element list to CSV command to the Create file command.
3. Select the Create file command, and click Edit.
4. Under Command properties, select the same File Utilities connector as the Find and replace commands.
   
5. Enter the command's properties, and click Save:
   

   Property	Description
   Text	Select the Converted file output of the Element list to CSV command.
   File path	Select the Chain.Workspace variable under Runtime, and append \test.csv.

Step 7. Add commands to use data in Workiva

To use the CSV data in the Workiva platform, add Workiva connector commands to use the Created file variable output of the Create file command with a spreadsheet or Wdata table. For example, to add the Enablon data as a data set in a Wdata table, add a Run chain event that uses a chain created from the Update datasets in a table template. 

Step 8. Publish and run the chain

To enable the chain to run:

1. Click Publish.
2. Enter any comment about its publication, and click Publish.

To run the chain:

1. From Chains, select Edit from the chain's menu.
2. Click Chain Settings, enter the variable values, and click Save.

   Note: For the Endpoint variable, enter ExportData or, to download the data in a 64-bit encoding format, ExportBinaryData.

3. Click Execute.
4. From Monitor, click Run with inputs, enter the runtime inputs, and click Start.