Use Case: When creating Notification Definition, we can only set one CommunicationProfileID at a time. it is a bit of task to create definition individually when a tenant has several Communication Profiles to manage and can this also result in a profile being accidentally missed.
we currently have 1 catalog that contains 1200 rate plans alone, we are expecting to leverage the translation profile capabilities to handle branding of names which are currently not only at the product catalog level, but also within the rate plan names. This limit will significantly affect how much we can leverage this tool, especially if we can not also delete translations that we no longer need going forward (which is already submitted as an idea)
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
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:
We would like something like this:
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.
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:
This is a huge pain point for me as an admin. Thanks in advance!
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.
There are API interfaces to manage most of Zuora except the users (not customers) of the organization. We would love to have our management systems and scripts to be able to update or change the status/role/etc of our users via an API. Part of this stems from the fact that user searching/sorting/editing in the web gui is painful when finding and editing users (no filtering/searching, limited results on one page forces multiple Next, Next, Next, when the users name is in the middle of the alphabet, etc).
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.
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.
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).
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.
I would love presets in Zuora! The way we provision access at my company is by job title. Finance Ops has one set of permissions while someone outside of FinOps may have some of those roles as "restricted access." Frequently, someone may click the wrong access level and then they have higher access than they need. I would love if there was a way for me to select a group of role permissions in one single pre-set. Say I enter in the users name and email and then select "IT Admin" and that would auto-populate all of their role permissions appropriately.
Let me know if that makes sense and if it's possible! That would make things way easier as well as more secure and accurate!
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.
We create custom documentation for various Finance processes in Zuora.
I would like to add links to these docs in my zuora instance.
Let us add labels to the menu and specify the urls ourselves.
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.
We have a critical custom field (that represents the customer's unique database id in our systems) that should be unique. It would be very helpful if we could set the custom field in Zuora to be unique, such that Zuora would not allow us to create multple objects (in this case, Accounts) with the same custom field value.
Our use case: When the customer converts (enters payment information), we send that to Zuora directly from their browser via the REST API. Our system then receives a New Subscription callout notification if the conversion succeeds. This is probably very standard.
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.