Admin & Settings Ideas

Zuora-Community · ‎01-13-2016

Feature Request: Require Audit Trail Status: under evaluation Reference Number: DE5826/PMT-876 Business Need: There are business requirements that are looking for the ability to have an audit trail for all fields and records. The requirement is to have an audit trail on all - Account fields (including all custom fields) - Subscription Fields (including all custom fields) - Contact Address Fields (including all custom fields) - Settings changes - Users' actions

rdeloach · ‎01-21-2016

It would be most helpful to be able to export a tenant configuration to a file, like meta-data or similar, and have the ability to import it into a tenant. There are 2 use cases for this: first, to back up and archive configurations to satisfy auditor requests to validate no unapproved configurations have changed. Second, in ensuring environment integrity in API Sandboxes or Services tenants to your source/production tenant.

S_Mizu · ‎02-03-2016

The custom fields are currently displayed in the order in which the custom field was created. If I want to add a new custom field that is related to existing custom field, I would like to position it around the related custom field, but the new custom field is displayed at the bottom of the custom fields. I would like to control the display order of each custom field.

Zuora-Community · ‎01-13-2016

Feature Request: Read-only user account (Z-Billing and Z-Payments) Status: Under evaluation Reference Number: DE3850 Business Need: Read-only user account (Z-Billing and Z-Payments) Currently, user can create new role for Z-Payments and uncheck all the Z-Payments permissions making it a read-only user but on the Z-Billing side, even though we uncheck the Z-Billing permissions, user can still create: *create account *create product *create report *create BR *create subscription Making it not a full read-only user role.

Zuora-Community · ‎01-28-2016

One issue I saw with leveraging the Zuora SPF record, it tossed my SPF over the RFC limit of 10 lookups (it alone is over 10)...many folks have either done subdomains for items like this or started to leverage DKIM...with such a large SPF, I would like to see a DKIM option to ensure email delivery if possible...

Zuora-Community · ‎01-13-2016

Feature Request: Ability to delete old invalid values from pick list in custom field Status: under evaluation Reference Number: DE7566 Business Need: Currently in Zuora, the design of pick list in custom field is that once it is saved, one can only edit the values in pick list and cannot delete the values. However, some customers have old and invalid values that need to be cleaned out, therefore, they are asking for the ability to delete old invalid values from those pick list custom fields so that their end customers will not choose the wrong value.

bolaurent · ‎09-23-2016

I typically have multiple tabs open to the UI. All the tabs have the same, not helpful, name. I really want these tabs to be named with the record that is displayed (a product, an account, an invoice, etc).

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.

dmdaniel · ‎05-11-2016

There are a couple of issues with the delete permissions, so this idea is a combination of a number of different ideas. - By default delete permission are enabled in the "Standard Profiles", they should not be - giving delete permission should be a more active task by an administrator. - Customising the default profiles is not possible, so you need to add a new profile to remove delete privledges. - In an active system you then need to identify the users to change to this profile, unfortunately there is no report. So its a matter of clicking on each user and changing (easy to make a mistake) - There is no way to remove the standard profile, so new users may get assigned to the wrong profile quite easily. (As this would be the detault option). Ultimately it is very difficult to robustly control and remove delete permissions - to address this a couple of things need to be done:- - make the default profile editable. - remove delete capabilities from the out of the box profile. Even with all of this, mistakes can happen, and ultimately there needs to be a capacility to un-delete mistakes (or even malicious actions) which could otherwise risk the survival of a business. There really needs to be an un-delete capability or a recycling bin (simiar to salesforce) that would allow object that have been deleted to be restored.

bolaurent · ‎05-25-2017

I have credentials associated with Zuora: Community Connect Support Subscribed University This is kind of a pain; how about a unified auth system?

Kyle · ‎06-03-2016

I think it would be a great idea to allow the ability to create/read/update users in Zuora via the REST apis. Is this something that is being prioritzed at this point?

Zuora-Community · ‎01-13-2016

Feature Request: Ability to remove/delete Pending Active and Inative users Status: under evaluation Reference Number: PLAT-4082 Business Need: Some customers are looking for the ability to remove/delete users in "Pending Status" and "Inactive", because some people have not responded to their activation email or were setup with the wrong information. Those accounts that are in "Pending Status" / "Inactive" are causing some confusion.

bolaurent · ‎03-03-2017

It's a significant source of friction that I can't search for an object until I click on that object name in the sidebar, then the search window on the right. Please give us a unified search field, displayed on all UI pages in the same location, that searches all objects. So, for instance, if I enter "INV0000123" it gets me to an invoice, and if I enter "Foobar" it displays accounts and subscriptions named foobar*. Also, if there is only a single hit (as for instance, "INV000123" would produce), then take me directly to the record.

sae · ‎06-27-2016

It would be great if there could be a search field on an aggregated level. So that when being on a customer account page, I can search for a new customer without going back to the Customer Accounts view. So a search field next to settings/ help/ log out menus to save a few clicks

Baotl · ‎03-30-2016

We strongly want to have a capability that we can choose the custom field's visibility -- 'show' or 'hidden' on UI. All cusom fields are showed on the page related to the custom field's object. E.g. Account Custom Fields are showed on New Customer Account or Edit Customer Account page, and are editable. We have a lot of custom fields, and some of the custom fields will not need to be displayed on UI because those were created for the integration purpose to use only in Z-API.

CecilieS · ‎06-17-2016

It should be possible to rearrange page layouts in Zuora for the different objects. Similar to the page layout functionality you find in Salesforce. This way you can create/add custom fields and show those fields where you would like on the Objects.

Zuora-Community · ‎01-13-2016

Currently, only "Invoice Posted" notifications are sent to ALL e-mail contacts including contacts in the "Additional Email Addresses" field. The notification "Payment Processed" is set up so alerts can be sent ONLY to Key Contacts listed on the right panel. This option to include additional emails should be consistent across all notifications. This "Additional Email Addresses" syncs with our internal system to allow customers to enter emails that they want to include on these updates. Without this option on the the Payment Processed notification customers are not able to have any control over who receives these emails. Any time they wish to change or add somebody we need to do this manually, this is not efficient.

Zuora-Community · ‎01-13-2016

There is already the ability to define whether a user can create accounts / contacts and add subscriptions, however by default this user can also cancel bill runs and cancel and delete draft invoices. It would be beneficial to lock down the access to Bill runs and other functionality. There are most likely other functions a user with basic Z-Billing permissions can access as well. Provide the ability for a user to upload usage files without accessing other key billing areas such as bill runs and invoices. Rationale for this: the ability to create a user that can create accounts / contacts and assign subscriptions, but does not have access to other critical billing area functions. The ability for the Ops team members to add usage files reported out of production systems without affecting

Zuora-Community · ‎01-13-2016

Support parenthesis like every other query language that has ever existed. For fun google "query language that does not support parenthesis".

Zuora-Community · ‎01-13-2016

We often get an UNKNOWN error when calling APIs. Recently we ran into a case where we were passing a custom field value that was too long for the value. It would be a simple thing to return that we exceeded the length. Instead the API returned UNKNOWN error. This is less than helpful. Improved error reporting would reduce customer development time. Also, since we ended up opening a support ticket it will reduce number of support issues raised.

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

Require Audit Trail

Export / Import configuration

Display Order of Custom Fields

Read-only user account (Z-Billing and Z-Payments)

DKIM implementation

Ability to delete old invalid values from pick list in custom field

Give UI tabs useful names

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

Recycling Bin

Too many credentials!

REST API CRUD Users

Ability to remove/delete Pending Active and Inactive users

unified search in Zuora UI

Search from home screen

Show/Hide settings of custom fields on Zuora U/I

Customazation of page layouts in Zuora

Support "Additional E-Mail Addresses" field for all notifications (specifically Payment Processed)

More granular Z-Billing Permissions (especially around Usage uploads, Bill Runs and Invoices)

ZOQL: Support Parenthesis

Better error codes for APIs

Notification callouts for significant account-level events

API Idea: Please support OAUTH

Usage related permissions on custom role