Skip to main content

Best Practices for Using Order Builder

Zuora

Best Practices for Using Order Builder

  1. Last updated
  2. Save as PDF

Overview

This article provides best practice information about using Order Builder.

Since the Apex methods in Order Builder use Zuora SOAP API calls, you may find helpful information and insight by reviewing the related SOAP API documentation.

Salesforce Callout Limits

  • 10 Total number of callouts (HTTP requests or Web services calls) in a request
  • 120 seconds Total request time for all callouts (HTTP requests or Web services calls) in a request
  • 10 seconds Default timeout of callouts (HTTP requests or Web services calls) in a request
  • 60 seconds Maximum timeout for custom callouts (HTTP requests or Web services calls) in a request
  • 3 MB Maximum size of callout request or response (HTTP request or Web services call)

ZOQL Limitations

  • Only 50 items can be included in a zObject list in API calls.
  • GROUP BY, LIMIT, AND, ORDER BY, BETWEEN are not supported in the zquery call.

Custom Field Definitions

You can define only custom fields of type "string" in the Schema Setup. However, this type can also be used to map to Zuora custom fields of type "picklist".

Creating a User Interface Component

If you want to create a user interface to use with Order Builder and Salesforce, you must create Visualforce pages and controllers.

If you are creating a trigger without a user interface component, you must write the code for the trigger, for example, to use Order Builder to call the Zuora API, but you do not need to create Visualforce pages.

Writing Test Code

If you are using Order Builder, Force.com requires that you create your own Apex classes and test code.

Optionally, you can also create VisualForce pages, if needed.