Extend 2FA so that it doesn't just rely on the user having a mobile device, whether via SMS or authenticator app. This could be easily achieved by sending something by email.
The reason this is important is that in call centres, mobile phones are not permitted due to PCI compliance issues. It would be better to have a solution that allowed more rigorous security without a user requiring a mobile device/
Zuora Connect allows only 4 currencies to be activated at once. Increase number to 20. This will prevent having to split files and do multiple runs.
Per Zuora Support Request #106568:
"I've discussed the issue with our Product team and at present, the new REST APIs are not yet supported in our Production copy environments."
Our engineering team(s) use production copy (services) environments as a staging environment for the purposes of development. Without support of the new REST API in services environments we will be unable to complete any work using the new Zuora REST API
Feature Request: Require Audit Trail
Status: under evaluation
Reference Number: DE5826/PMT-876
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
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.
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).
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.
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
I like the new look with the new sidebar, however the sidebar does not appear to have clickable "links" like the rest of the page. I use this a lot in my daily work with Zuora to "open in a new tab" by right clicking on "Customer Accounts" or "Product Catalogue" so I dont have to leave the page I'm currently working on to go work on something else.
This would be great if this functionality could be integrated into the new look!
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.
At the moment we have about 10 customers who we administrate their Zuora/Salesforce environment for. We have configured Zuora to send out the Z360 sync notification (errors only) to our support e-mail address. However, because in the mail notification there is no mention of the tenant ID or the tenant name, we never know for which customer we have received an error notification and thus we don't know which Z360 sync fails.
Because of this we see sync errors normally way too late. We need to get those notifications with the associated tenant ID or name.
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
Feature Request: Ability to remove/delete Pending Active and Inative users
Status: under evaluation
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.
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.
It would be helpful for key individuals in our company to be notified when significant account events occur: Account cancelled, account deleted (this is a really big one for us) and autopay disabled with default payment method being a credit card (as opposed to "Credit Card"). Is this something that is practical and/or possible?
Feature Request: Today, the only options available for final users to import data into Zuora are: The import tool that is available in the UI or Zuora API Utility. The first option has many limitations, for example you can only import data related with some objects like the account, contact, payment method, etc. The API Utility works for final users with some technical background, a product manager or someone more business oriented can't use a tool like this one easily
At this point, an standalone application like the Salesforce Data Loader could be a great addition to the multiple tools that we can use to import data into Zuora.
Business Need: There is no easy way to import data into Zuora. This is major blocker to import data from legacy systems or new partners without the intervention of a technical resource from the customer side or from Zuora professional services.
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.