Admin & Settings Ideas

usaluz · ‎08-29-2019

It would be very helpfull if it would be possible to define global header and footer elements and maybe even more elements that might be used on different E-Mails. It would also be great to have a default base template, so if you create a new e-Mail notification the design and layout will be pulled from that base template.

nmartelliere · ‎11-14-2019

Hi, Emails and callout (available in Notification History) of Zuora customer account are not available in z360, it is important to have in SFDC a really 360 ° view of all the exchanges with our customers (invoice sending, sending reminder for example). Best regards, Nicolas Martelliere VIDAL SA

senorstanley · ‎12-28-2018

For high volume and transactional business, there needs to be a lot of AR specialists working in Zuora to process orders. We need to create a lot of one-off account Bill runs to collect initial payments. However, a specialist may create a bad bill run and accidentally select multiple accounts which could create a lot of problems. I think it would be created to add another security permission to "Allow multiple account bill runs". We could give AR specialists the ability to run a single account bill run and leave the multiple account bill runs to administrators.

sgangal · ‎08-27-2019

Hello, I will like put forth a suggestion related to Credit Memos. (1) Please consider implementing a mechanism to limit Credit Memo creation by "Amount" e.g User role "A" should be permitted to create a Credit Memo <= $100 User role "B" should be permitted to create a Credit Memo <= $1,000 User role "C" should be permitted to create a Credit Memo <= $5,000 etc. (2) Please consider implementing a mechanism to have approval hierarchy for Credit Memos e.g. All Credit Memos >= $500 and < $2,000 need approval by Supervisor "S" All Credit Memos >= $2,500 and < $5,000 need approval by Manager "M" All All Credit Memos >= $5,000 need approval by Director "D" etc. Thanks. ~ Salil

Yoshihisa · ‎11-27-2018

There are requests from customers that the functionality to resend notifications is needed. e.g. there are cases where email address is not correct and notifications could not be sent. And after the email address is corrected, the notifications need to be resent. One idea would be to implement "Resend button" in "Notification History" screen.

Renaldo · ‎06-10-2016

Allow a custom field lengths of 2k or 4k chars. Customers are finding they require custom fields that can hold more text. Un-indexed custom fields, or additional notes or description fields of 2 to 4k characters are being requested.

KerryMcD · ‎10-06-2017

We have hundreds of Zuora users and it can be a real pain finding a user on the user list, especially if their first and last names are in the middle of the alphabet. Would love the ability to: Search for a user by name Sort the list by other columns like role Filter the list (build list views like in Salesforce) so I could easily pull up a list of all Active users or all FinOps users for example. Be able to export any of the results of the above (so export only active users for example). This is a huge pain point for me as an admin. Thanks in advance!

zachmeyer · ‎12-04-2017

We would like the ability to pass parameters into the Callout Notification BaseURL. The URL is currently static. For example, instead of a hard coded URL like this: https://mywebsite.com/zuora/account We would like something like this: https://mywebsite.com/zuora/{AccountId} This is useful for REST APIs that expect specific information in the URL. We would like the parameter options to include custom fields as well.

Yoshihisa · ‎04-23-2019

If you set "Bill To Contact" in "To Email" and "All Account Contacts" in "CC Email", when email notification is sent, email address of "Bill To Contact" is included in CC as well as To. We have a request to implement the option to exclude "Bill To Contact" in "To Email" from "All Account Contacts" in "CC Email" so email address of "Bill To Contact" is only included in "To".

libertymcb · ‎11-21-2018

We send our customers notifications about upcoming renewal dates and other changes to their account (late payment notices, etc.) Currently there is no easy way to sync these email notifications to our CRM (Salesforce). This is vital information that our sales team should have access to when having conversations with their customers. Because they don't have access to Zuora, they have no way to know that there may be other communications with the customer around their subscriptions. We looked into building this out with a webhook, where authentication needs to be handled when calling the exposed apex endpoint. However, this can not be done with the Zuora callout functionality. What probably needs to happen is a new billing endpoint needs to be created, and that endpoint will do a callout to salesforce to create the note. TL;DR - we need engineers to help us implement this. We would like this to be a built out feature of Zuora's 360 sync or some other way to handle the communications through a configuration. Surely this is something that other businesses want to have available for teams that aren't in Zuora's interface?

Sanketh · ‎09-06-2019

We have CreatedByID , UpdatedByID on each object . But it is hard to map this into specific username via logic through any API and zObject of User. Helpful to have User fields fetched through API calls hence people doing changes on records could be tracked.

jasong · ‎09-21-2017

Support confirmed with me that when a tenant is configured to use SSO and a user clicks the "logout" button, then it redirects users to the organization's SSO login page. However, session timeouts go to the ZUORA login page. This, in my opinion, is the wrong behavior. When a tenant is configured to use SSO, session timeouts should ALSO redirect users to the SSO page - that way if the SSO configuration still has an active token, the user can be redirected seamlessly back to zuora. Please upvote this. The lack of this feature is causing pains within my organization. :) Thanks.

ehavens · ‎06-21-2016

We use HTML format for our email notifications. On the Account page in the Notification History section, the email preview renders the HTML code instead of the actual email. This prevents our Zuora users from knowing exactly what was sent to the customer since they can't decipher all this gobbledygook. It would be a good idea to have a Pain Text option for email notifications so they render in a legible format. if this isn't the right section for this idea, please move appropriatly.

klee34 · ‎01-15-2019

Hello, We are trying to prevent certain users from accessing certain areas, even for View Only purposes, such as Billing or Payments. However, we have been told that this currently is not possible. it would be nice if this was possible. Thanks, Kevin

vkannan · ‎08-11-2017

Hi, Today when we execute AqUA, the only option is to get back a file with the data. Can we look at returning JSON for the same response. We can look at creating page sizes to restrict the size. Thanks, Vimal

wilcoschreurs · ‎11-12-2018

Currently we can only retrieve value of CreditMemoTemplateId a DebitMemoTemplateId of an existing Account by using the REST GET method for one account only. But we want these 2 fields to be available in query/export/aqua results to feed the DWH, so we are not limited to exporting 1 account at a time

Yoshihisa · ‎06-12-2019

When you use "BillRun.Batch" parameter in callout, the same value as displayed in the screen is returned from "BillRun.Batch". Therefore the value varies depending on the display language and custom name of the batch. We have a request from a customer that they would like to have a callout parameter which returns the same value of "Batch" field in "Get bill run" API so the value is not affected(not vary) by the display language or custom name of the batch. The purpose is that they would like to pass the value of "Batch"(which is not affected the display language or custom name of the batch) to the application which is called by callout.

roantondtt · ‎06-07-2019

Currently the aging bucket configuration is the unique for all system. But in our current customer the aging bucket depend on the customer type (public administration, wholesale accounts, retail...) I suggest to add a mandatory picklist field in the account entity, whose values are configurable in the billing configuration, to define the customer type. Then this new field will be a new parameter, a new liberty degree, in the configuration of aging buckets. There will be a single customer type by default, and will be selected by default in the aging configuration

klee34 · ‎01-14-2019

We have currently implemented Orders and would like to control the ability to impact Orders. However, there are no permissions available for Orders under User Roles. Can this be implemented? Thanks, Kevin

mgartner · ‎01-10-2019

There should be an API endpoint that can charge a specific customer's endpoint for the full amount, with having to only provide the invoice ID. The endpoint could be `POST /v1/invoices/payments` and it would charge the invoice for the full amount. This would be much simpler than using the `POST /v1/payments` endpoint, because that endpoint requires the most tedious minutia in the request body just to charge an invoice. For example, it requires you to provide the amount you want to charge, and the break down of the amount for each line item in the invoice. All that information is already available on Zuora's side, so there is no need to make the API users provide it. It makes integration unnecessarily complicated.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Admin & Settings Ideas

Using Partial Templates for E-Mails

Synchronize Customer Notifications History in SFDC (Z360)

Security Permission for Multiple Account Bill Runs

Credit Memo: Amount Limits + Approval Hierarchy

Ability to resend notifications

Allow a custom field lengths of 2k or 4k chars.

Search for a User and/or better sorting of user list

Allow parameters in Callout Notification Base URLs

Option to exclude "Bill To Contact" in "To Email" from "All Account Contacts" in "CC Email"

Sync Email notifications to Salesforce

SOAP & REST API Calls to fetch fields from USER record

Session timeouts should redirect to the SSO login page

Render HTML emails in Notification History

Prevent User Access to a Specific Area

Allow AqUA to return JSON response

Add Credit Memo Template ID and Debit Memo Template Id of an Account to query/export/aqua results

Callout parameter of "BillRun Batch" which is not affected by the display language or custom name

More flexible aging bucket configuration

Access Control for Orders

Make it easy to charge a specific invoice

Usage related permissions on custom role

Reset All Passwords Next To Add User Button - Insane Button Arrangement

Support new REST API in Production Copy (Services) Environments