Knowledge Center

Knowledge Center > What's New > Zuora 360 Q4 2016 Release Notes

Zuora 360 Q4 2016 Release Notes

This release notes provides a summary of new features, enhancements, and resolved issues in the Zuora 360 Q4 2016 Release (Version 4.0).

There are no steps required to upgrade the Version 3.4x to Version 4.0.

To upgrade the Version 3.4x to 4.2, see Upgrade Zuora 360 to Q4 2016.

New Features and Enhancements

The 4.0 release includes the following enhancement.

Support for Zuora REST API in Order Builder

A new global method was added to send REST requests to Zuora. The sendRequest global method takes in an Apex HTTP request, adds the authentication session header using the credentials set up in Connection Settings, and submits the request to Zuora.

See sendRequest Method for the detail information about the new method and code samples.

Maintenance Release 4.2

The 4.2 release includes the following enhancements and resolved issues.

Ability to View Inline or Download Invoice PDFs

Now you have two menu options on the Invoice detail page to download the invoice PDF or view inline. The menu options for invoice PDFs are available as buttons and custom links.

  • View Invoice PDF for opening the invoice PDF inline.
  • Invoice PDF to directly download the invoice PDF.

See View Invoice PDFs for how to configure the Invoice page layout and use the functionality.

Token Id and Second Token Id Synchronized to Salesforce

Starting in this release, the Token Id and Second Token Id fields on the Payment Method object are synched from Zuora to Zuora for Salesforce, enabling you to support custom use cases involving payments in Salesforce.

Typically, the Token Id is used for the customer identifier or profile on the payment gateway side, and the Second Token Id is used as the underlying individual payment instrument identifier. 

See PaymentMethod for descriptions of the TokenId and SecondTokenId fields.

Refer to Sync Field Mapping of Account and Related Objects to see how the TokeId and SecondTokeId fields are mapped to the fields in Zuora for Salesforce.

Maintenance Release 4.4

The 4.4 release includes the internal operational fixes. 

Communication Profile Id not Correctly Migrated 

A migration issue caused communication profiles not synchronized for some customers.

See Migration Settings for Zuora 360 how to use migration setting to trigger data migration after upgrading Zuora 360 packages.

Last modified
13:03, 20 Mar 2017

Tags

Classifications

(not set)