Zuora CPQ Ideas

  In Zuora Quotes, if you create or update New Subscription Quote, Amendment Subscription Quote and Renewal Subscription Quote, following fields are displayed in the roll-up feed in Opportunity .   - Name - Opportunity (name)  - Status - MRR (Delta MRR) - TCV (DeltaTCV)   Client would like to use chatters, but would not like to see the above fields in roll-up feed in Opportunity when New Subscription Quote, Amendment Subscription Quote and Renewal Subscription Quote are created and updated.   According to the Knowledge Center, it is able to control On/Off of chatters. However, it is not able to control which fields to show in roll-up feed. Should have a capability to select which fields to show in chatter's roll-up feed. ... View more

Customers have requested the ability to sync the "Today's MRR" field from the Zuora UI to SFDC via 360 sync. Is this a possible future enhancement? ... View more

 It would be nice to have a PDF quote template for cancellation quotes. Some customers need them so they can get a customer to sign that they agree to cancel. ... View more

In Zuora it is possible to configure charges to end after x billing periods but that option isn't available when configuring the product catalog in Salesforce and using it on Salesforce CPQ quotes and contracts. It would make it an option to have a negative recurring charge that ends after x billing periods instead of a discount line item which Salesforce CPQ does not support. I understand this may cause an issue with the quote calculations on the Salesforce CPQ side but it's easier to push that as an issue to them but still have Zuora and the connector support it. ... View more

It would be great to have the ability to have a Salesforce CPQ quote contracted using an automated process. Currently the code to create the billing account in Zuora when the quote is contracted is not exposed. If this could be exposed to automate this process this would be very helpful to save manual steps during the quoting process. ... View more

The existing button on quote 'Update Zuora Account Details' works well for Payment fields and contact fields but there is no possibility for us to add the Account Name ... View more

Recent changes to callout processing and history have caused us a few issues, most of which have now been resolved, at least one of which (display of the HTTP response code) will be addressed in the December patch.   We use callouts to provision our services; that is, the licenses we provide to our customers for our server based software are created and maintained by callouts from Zuora.  This makes callout functionality critical to us.  In the past, we've had some issues with callouts that have caused us to monitor them on a daily basis, which in some ways may make our use of them different from most customers.   With that in mind, here are some ideas we think might be helpful in improving callout functionality.   Timeouts and retries are an issue in our environment. In the history display, it would be useful to be able to group attempts under each transaction, to see quickly and easily how many times a transaction was attempted and whether it finally succeeded. After a timeout occurs, it would be useful to "stagger" the retries, for example 2 minutes before the second attempt, 5 more minutes before the third, 15 minutes before the 4th, and an hour before the 5th.  This is in case other processes are consuming bandwidth or server resources. 15 seconds is rarely enough time for our callouts to complete if the service being called has been idle for some time.  Being able to configure the first attempt at a transaction to allow longer would be helpful. If the planned custom action by result type could be configured by HTTP response code and attempt number, we could perform custom actions only when a 5th response 408 was received (or whatever number we've set as the retry limit). The parse flag shouldn't determine whether a 408 response is correctly detected as a timeout. Our environment may encounter issues if sync processing is delayed or encounters an error. A manual re-attempt button from the callout history, perhaps only shown when the transaction has not succeeded on any attempt, would be useful. The ability to see the parameters and the responses as tooltips by hovering would be helpful to us. Our study of daily callout results could be more efficient. If callout history were a valid data source for reporting, we could construct custom reports to scan quickly for problems, and make those reports part of admin dashboards. With a report, attempts could be grouped under transactions (this could also be provided at the API level). Using a report, we could filter out multiple callout types and display multiple types, allowing, for example, a report featuring all subscription event caused callouts, but no others. 201 is a successful HTTP response code.  Although we've programmed around this issue, it would be preferable if Zuora could recognize 200 or 201, possibly even 202, as a success, and display the response codes for Pass as well as those for Fail.  Even better, allow selection at run time between showing Pass/Fail, actual HTTP response code, or HTTP response short description. ... View more

Invoice line item required as part of the Z-360 sync process ... View more

Requirement for the PaymentMethod.TokenID in ZFSF Z360 Sync, to allow customer to pull-back summary of card details. Reference/search within gateway. ... View more

I would like the support of Lookup fields to work properly on charges in the Product Selector when using  zqu__DisplayChargeFields. ... View more

Zuora has a character limit of 500 set for the charge description field, however, in Salesforce the Product Rate Plan Charge and Quote Rate Plan Charge Description fields are text area (255) meaning that any descriptions saved in Zuora will be truncated when sent to Salesforce.   We already think that a maximum character limit of 500 is too low but in reality the limit is set at 255 as we generate all quotes in Salesforce and it uses the truncated values.   The Product Description and Product Rate Plan Description fields both have Text Area Long fields (still capped at 500 in Zuora) so surely this can be modified for the Product Rate Plan Charge Description.   Failing that the ability to create a custom text field that is greater than 255 characters that we can sync to Salesforce would be much appreciated. ... View more

Save Opportunity Id to Zuora Subscription object when Quotes are Sent to Zuora.   This will be helpful to enable downstream reporting and billing/accounting audit. ... View more

Every night there is a scheduled process that runs to sync the status of the Entitlements and Hosted Payment Method Pages into salesforce. These tend to error a lot (about 25% of the time) which generates an unhandled exception email to our admin monitoring.   Since this error is not terribly impactful (waiting 36 hrs instead of 12 hrs for a new feature to show up), it would be helpful if these errors were handled more gracefully. We monitor the unhandled exceptions and generate support cases whenever we get one and it's we're constantly getting asked whether this is something that's broken.   It appears that the error is because a callout to Zuora is returning HTML instead of JSON. So things could potentially be fixed by ensuring the API returns JSON in error cases instead of html   == zqu.RefreshCustomSettingSchedulable.refreshEntitlementPermission() ==   Failed to invoke future method 'global static void refreshEntitlementPermission()' on class 'zqu.RefreshCustomSettingSchedulable' for job id '7071300002M2Qhs' caused by: System.JSONException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at input location [1,2] Class.System.JSON.deserializeUntyped: line 11, column 1 Class.zqu.RefreshCustomSettingSchedulable.refreshEntitlementPermission: line 67, column 1   == zqu.RefreshCustomSettingSchedulable.refreshHpmPermissions() == Failed to invoke future method 'global static void refreshHpmPermissions()' on class 'zqu.RefreshCustomSettingSchedulable' for job id '7071300002M2Qht' caused by: System.JSONException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at input location [1,2] Class.System.JSON.deserialize: line 15, column 1 Class.zqu.PermissionCheckService.checkPermission: line 26, column 1 Class.zqu.RefreshCustomSettingSchedulable.refreshHpmPermissions: line 29, column 1 ... View more

For a Renewal Quote, the object "Quote Product Feature" does not contain any values for Quote Rate Plans that have the field zqu__AmendmentType__c = Renewal.  Because there are no changes it doesn't list the features already assiciated with that product.  When a Quote PDF is generated, the feature table is empty for that product.     It would be better if the object Quote Product Feature contained the existing features.  Then the QuoteFeatures table would display features for new products, updated products, and renewal products (original). ... View more

We run into data issues in Salesforce because when we run the 360 sync, it syncs ALL products, rate plans, charges, ever...even if we have deleted them.  It would be extremely helpful and make our Salesforce data much cleaner if there were either global settings in Zuora Commerce that would allow us to check "Don't sync deleted products" (and/or rate plans, charges, etc.) AND/OR be able to manage it on a record-by-record basis.  The latter would also be helpful during the development of new products.  We could mark them as "Do Not Sync" until it is complete.   This caused us the biggest issue when we paid to have our API sandbox rebuilt.  The products didn't get created correctly the first few times so the services team deleted them and recreated them.  Since Zuora maintains deleted records in their DB, those too get synced.  Although the deleted records get marked as such in Salesforce, it creates hundreds of records that we'll never use.  Deleting them from Salesforce is futile because the next sync will re-add them. ... View more

 Zuroa API returns "Operation failed due to an unknown error" for different scenarios. This error message is returned via the API, which is also displayed in Salesforce when the Quote is generating the preview metrics.   This error can arrise from different reasons. One is Avalara has an error due to configuration issues, but the user does not know until a Zuora Support agent looks into the error in the backend.   Another reason for this error could be the Payment Gateway is not properly set up. You can view existing tickets where this confusion has occured due to vague error messages. Time can be saved if we identify the issue in the beginning. Thanks.   See Ticket # Avalara 63513 85128 66062 66492 67048 81386   Payment Gateway 77230 ... View more

Currenty, a Charge Option relates to a single currency and pricing. It is cumbersome for a user to be creating multiple Charge Options manually for every currency. Can we either make this object structure similiar to Product Rate Plan Charge and Tiers to support multiple currencys and the Charge Table that is displayed for the Product Rate Plan Charge, OR create a UI to similar to the Charge Table but have it support Charge Option?   Another ask is to support an in-line discount override instead of only being able to specify the price override. ... View more

If a user clicks the Generate Quote button from the Quote Detail page a pop up opens, and takes upward of 10 seconds to generate the quote. And then once the quote is generated the message is very plain - can we have the abliity to customize this message. The Quote is attached to the Quote Detail page - but the page needs to be refreshed before the user can access it. If at the very least the 18char ID could be a hyperlink to the quote so that the user could download or view it that would be helpful.   ... View more

Core Zuora has a setting that can be enabled to allow up to 20 amendments in one call but even when that setting is enabled Zuora for Salesforce doesn't use it and the quote metrics cannot be correctly calculated.  ... View more