This article enables you to install a standalone Configurable Payment Retry app.
Before you can use an app, you must install the app on your Zuora tenant.
You must have a Zuora Connect account. For more information, see Link your Connect account to your Zuora account.
You must have purchased the app.
You must have created an OAuth login for your Zuora tenant. For more information, see Create an OAuth Login in Zuora Connect.
To install the Zuora Collections feature, you must have the Platform Admin role. For more information about platform roles, see Platform roles.
Log into your Zuora tenant.
Navigate to Marketplace > Purchases.
Locate the Configurable Payment Retry app to install, then hover and click Deploy.
In the New Configuration window that opens, specify the configuration details for the app:
- Name - A name is automatically populated. Modify the name if necessary.
- Run Mode -See the app's documentation to learn about how to choose a run mode.
- Execution - Select External unless otherwise specified in the app's documentation.
- Build Name - Select Production - US, irrespective of your environment.
- Source, Target, etc - Select the tenant login for the app. Some apps or functions require using OAuth. In this case, select the OAuth tenant login for the installation.
The app is installed and will be populated under Marketplace in Zuora shortly. You may need to refresh the page for the app name to display.
After an app is installed in the tenant, you can launch, configure, and use the app in Zuora.
After installing the Configurable Payment Retry app, you need to complete initial configurations before it is ready for use. For instructions about configuring the app, see Configure the Configurable Payment Retry feature.
Create required custom fields
When you create your Configurable Payment Retry application with Oauth credentials, Zuora will create the required custom fields. The custom fields will be created once the app has been launched and settings saved. For more information, see Custom Fields of Collections.
Custom fields may not be generated automatically if the quota has already reached 10 for indexed and up to 40 for non-indexed custom fields. If so, the customer must remove the existing custom fields and create existing custom fields manually. For more information on how to add a new indexed or non-indexed custom field, see How to manage custom fields.