Staging Release 2.126
Incident Report for Cloud Elements Changelog

Highlights (Staging - 2.126)

Added new APIs for the TaxAgency resource in the Quickbooks Online element

The following new endpoints have been added to the Quickbooks Online element:

  • GET /tax-agencies

  • GET /tax-agencies/{id}

  • POST /tax-agencies

Made customer ID available in 'customers' event payloads

  • Customer ID is now available in the otherId field of the event payload for the customer-create and customer-update event types.

  • This feature has been added for the customers resource only.

Abridged elements and instances for UI search

  • Now, new element instances will return a list of created tags in the JSON response.

Added ability to provision Facebook Social using an Application Access Token

  • You now have the ability to provision an instance of the Facebook Social element using Facebook's Application Access Token. Try it out!

Limited access to formulas that are none of your business

  • We've introduced a few new rules which limit which formulas a user can access in their organization

    • Admin users can see every formula without any restrictions.

    • Non admin users of the main account can see any formula owned by any main account user, but can't see any subaccount formulas.

    • Subaccount users can see any formula in their own subaccount as well as any formula owned by the organization's admin users, but can't see any formulas owned by a different subaccount.

  • Note that this doesn't change the rules regarding who can edit or delete a formula.

Updated element name and logo for Freshbooks

  • The Freshbooks name and logo have been updated to Freshbooks Classic

Enhanced element object metadata

  • Added method to each field to define where the field is used. For example:


"type": "string",
"vendorPath": "first_name",
"method": [
"response": true,
"name": "GET"
"request": true,
"response": true,
"name": "POST"
"request": true,
"response": true,
"name": "PATCH"

  • Added method in JS transformations where the possible values can be GET, POST, PUT, PATCH and BULK. You can use this along with from vendor to determine the method call and direction.

  • This is available for all Element Builder based elements.

screen recording 2017-07-06 at 07 37 pm

Fixed password validation on Pardot element instance creation

  • You can now create an instance of Pardot with a password that contains special characters such as:

> ( ` ,^ and " )

Added new documents and attachments functionality to the Salesforce Sales Cloud element

  • You can now retrieve all of your Salesforce Sales Cloud documents & attachments using the new GET /{objectName}/{objectId}/data resource.

Improved Salesforce Sales Cloud bulk querying

  • A finite list of objects/resources in Salesforce Sales Cloud support "primary key" (PK) chunking for large data sets.

  • The Salesforce Sales Cloud element's bulk query API now checks if PK chunking is supported for the requested object/resource, and applying the same.

  • The list of resources/objects for which PK chunking is supported is as follows:

    • Account

    • Campaign

    • CampaignMember

    • Case

    • Contact

    • Lead

    • LoginHistory

    • Opportunity

    • Task

    • User

    • All custom objects

Convert an XML response to JSON if the response content type indicates XML content

  • Some vendor endpoints require a Content-Type of application/form-encoded or some other non-JSON content type, but return XML content. In this case, using the request Content-Type to determine if the response needs to be converted to JSON from XML will result in an XML string being returned for the response.

  • Added a mechanism to check the response Content-Type header, and if set to text/xml or application/xml, convert the response body to JSON

Posted Jul 24, 2017 - 08:37 MDT