Even though a one time charge is not technically renewed, it remains on the latest renewal version after sending to Zuora. It appears that the user in Salesforce has to drop the One Time Charge even though it cannot be renewed before sending to Zuora. Is that the expected behavior or should the system not have it in the latest version of the subscription after sending to Zuora and post renewal?
... View more
See more ideas labeled with:
On a Renewal Quote, the Quote Rate Plan Charge (QRPC) Sub Total fields do not update when they are straight renewals. Rather we just see the Subscription Sub Total update. I am expecting the sub-total on the QRPC to populate. The reason this is important is that we report on the impact by product which would be reporting on QRPC sub totals.
... View more
There doesn't appear to be a way to capture the Quote Rate Plan Charge (QRPC) sub totals that impact the cancellation. Rather we just see the Subscription Delta TCV. I am expecting the sub-total on the QRPC to populate and roll up to a sub total amount. The reason is that we report on the impact by product or service cancelled and that is the QRPC.
... View more
Status:
New Idea
Submitted on
02-15-2017
11:44 AM
Submitted by
njcolletti63
on
02-15-2017
11:44 AM

Scenario: Account currently has a subscription that is Evergreen. Upgrade to a new product tier along with a move into a termed subscription is being proposed. Quote created that sets the Initial Term to 12 months, and old tier product removed and new tier product added. Delta TCV shows as $0.00, Delta MRR has a value of $1235.00. Zuora support indicates that the Delta TCV is $0.00 because the original subscription does not have a term end date since it is Evergreen so no calculation can be made for the Delta TCV. My understanding of a Delta TCV is that is should show the difference between the original subscription and the quoted subscription changes. If the current subscription is Evergreen, and the Quote results in the subscription being Termed, why wouldn't the Quote Metrics calculation take this new term into consideration. Additionally not including the discounts that are recurring in the Delta MRR and Delta TCV is also misleading and should be part of this calculation as well. My sales team are paid on the Delta TCV when amending/renewing a subscription. To have the Delta TCV to remain at $0.00 requires that someone else now has to do the work of what the computer should be doing by manually calculating the Delta TCV value. Has anybody else had issue with the Quote Metrics and the calculations that are being done.
... View more
Hi, Since the default Zuora Perimission set provided in the package Zuora for Quotes is required for all Zuora Enabled users we have it enabled for all people but unfortunately we would like to restrict it so people are not able to delete quotes but since the permission set is overriding the profile settings we don't have any ability to do so.
... View more
When renewing a subscription that had a recurring charge with specific end date prior to the subscription term end date, the renewal experience appears to allow you to renew the specific end date even though the Specific End Date is hard coded and technically you can't renew an expired charge. Would rather the behavior be that the end user cannot renew the product rather than have to drop and add a new one. Similar behavior to the One Time Charge. It won't let you do anything to the One Time Charge. In this case, our sales reps would just add a new charge rather than dropping and adding the same charge. Let me know if you need more information.
... View more
See more ideas labeled with:
The Edit Features dropdown option is still displayed even when Features is not enabled in Zuora or in Salesforce. This should be removed when Features it not enabled.
... View more
It is a best practice in software development to not catch all generic exceptions as in try{
// apex code that calls zqu global methods
}
catch (Exception e) {
// handle and/or rethrow, etc.
} However I find with many of the methods I call non-global exceptions are thrown which I am unable to catch such as try{
// apex code that calls zqu global methods
}
catch (zqu.zApi.zApiException e) { // Will not compile
// handle and/or rethrow, etc.
} It would be best if the Zuora for Salesforce code handled it's internal exceptions and exposed a global exception that developers can catch when necessary.
... View more
Sometimes a quote contains charges that do not need to be shown to the end customer, particularly for usage charges, but filtering them out if very difficult and not user friendly using mailmerge. Would be great to have a way to do this by not showing charges with a certain custom or standard field value.
... View more
In the Salesforce Invoice and Payment object it would be great to have a field indicating if the invoice or payment is related to a renewal, a new customer, an upgrade, etc. This field is very typical on opportunities but we lose track when we look into invoices and payments.
... View more
See more ideas labeled with:
Since this field defines the vat calculation that appears on the invoice it should be a standard Zuora Quote package field in the Zquote. That way, when sending quote to z-billing, it will sync to the Zuora Sold to contact before the subscription and invoice is created. That way the invoice will be created with the correct tax code
... View more
When using the Salesforce CPQ connector, for each pricebook that a product has a price defined, a new product rate plan is created in Zuora, however there is no way to identify which rate plan is for which currency or location or region apart from using the pricebook name. From a web portal perspective that makes it difficult to rknow which price to return based on the customers location. It would be good if we could have a custom field, possibly on the price book, that could sync to the Zuora PRP that could be ued by a web portal to filter the correct rate plans.
... View more
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
See more ideas labeled with:
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
See more ideas labeled with:
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
Status:
New Idea
Submitted on
12-01-2016
02:53 PM
Submitted by
Michael_Summitt
on
12-01-2016
02:53 PM

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