The upload file size is controlled by a NGINX parameter client_max_body_size, present in nginx.conf file . By default, this is set to 1 MB.
If the upload file size exceeds the value set for the client_max_body_size, then the Error 413 Request Entity Too Large is returned to the client/browser. Setting size to 0, disables the client request body size validation.
Restart NGINX after changing the default value.
For on-cloud customers, Zuora's Technical Operations team takes care of setting an optimum value for this parameter. On-premise customers can reach out to their respective infrastructure maintenance team to make the changes to this parameter value.
... View more
Zuora is going to merge the RevPro Zendesk Support portal with its unified Zuora Zendesk portal on April 18, 2020 and decommission the dedicated RevPro Zendesk Support portal. Hence all the customers post this date will be using the common unified support portal for all their support needs.
What does this mean?
As part of the unification project, Zuora Customer Support team is going to have a single unified Zuora Support portal. Beginning 18 th April, 2020, we will be decommissioning the RevPro Zendesk portal and you will be redirected to Zuora Support portal. You may need to follow the forgot password link and reset your password for the first time.
Why is Zuora merging the support portals?
Zuora will have (all under one-roof with) a single support portal for all its Billings, RevPro and Zuora Revenue (customers using both Zuora Billings & RevPro) customers for easy maintenance and reporting. After the unification, Zuora Revenue customers can access their tickets in the unified portal.
Who are all affected?
RevPro customers using RevPro Zendesk portal will not have access to it after the unification. Instead, they will be accessing the Zuora Support portal for all their support needs.
What is the migration window?
On 18th April 2020 , the RevPro Zendesk will not be available from 8PM PST. The expected duration for the migration of the data to the Zuora Zendesk portal is approximately 6 to 8 hours. Once the migration is completed, you will be notified on the completion along with the new URL to be accessed going forward.
How do I report an incident during the migration window?
You will not be able to submit tickets by accessing the support portal as it will be down during the migration window. Alternatively, you may send an email to email@example.com which will automatically create a ticket in the unified support portal and you will receive a notification on the ticket creation.
For urgent and critical Production issues, you may reach out to the RevPro support team on the hotline# 1 888 883 2821 for creating a new ticket or tracking the status of the open ticket. For escalations, please do not hesitate to send an email to firstname.lastname@example.org.
What is the impact of this unification/migration?
All active RevPro tickets and historical tickets will be migrated to the Zuora Zendesk. Post migration, the requesters of the current active tickets will be receiving a notification from Zuora Zendesk with the details of the new ticket number (along with the corresponding old ticket number) to be tracked, going forward.
RevPro Only Customers: All the customer accounts and the user accounts will be migrated to the unified portal; you can access your account with the same user name which you have been using for accessing the RevPro Zendesk portal, after the migration.
Billing and Zuora Revenue Customers: User accounts that do not exist in the unified portal will be migrated from RevPro Zendesk and mapped to the existing customer accounts. All your RevPro tickets will be migrated to the unified portal and will be tagged under the existing customer account.
... View more
The purpose of this article is to provide a quick overview on RevPro Log Retention Program along with the steps on “how to” schedule/run this program.
Concurrent Program Name: RevPro3.0 Log Retention
This program helps to completely clean up (truncate) the log records in RPRO_LOG_ACT_G table.
If truncate option is not preferred, then this program can also help to
retain log records created in the last X number of days (and/or)
retain log records related to a specified Revenue Contract (and/or)
retain the log records which were created when the log level was “n” [n ranges from 0 to 20]
and purge the remaining records. Below screen print depicts the program definition in RevPro and RPRO_LOG_PURGE_PKG.CLEAR_LOG_DATA is the procedure runs in the background if the program is submitted through the UI.
Did you know: RPRO_LOG_ACT_G is a database table which stores the system logs, written by various programs which are running within the RevPro. It also captures the log information related to any activities performed by a user through the GUI. RevPro provides a flexibility to set the log level through the configuration options – lesser the log level, lesser the records captured in the log table. To know, how to change the log level, read this article.
How to run/schedule the log retention program in the Angular UI?
Navigate to Reports >> Schedule Jobs.
In the Schedule Job screen, click the + link.
In the Schedule Job/Job Groups screen, click the down arrow available for the Program Name field in order to select the Revpro3.0 Log Retention from the list of available programs. Select the desired date & time for the Start Date if the program must run at a specified time in the future; otherwise leave the field with the defaulted date and time.
If the program needs to be scheduled to run in a desired frequency, then select the appropriate options under the Recurring Setup block. Below screen print depicts that the program has been scheduled to run on every Sunday at 8 AM.
Value Y: Program truncates the log table completely i.e. all the records in the log table will be deleted. When selected, do not pass values for the remaining parameters.
Value N: This should be selected if certain records in the log table have to be retained. If this option is selected, then value(s) have to be passed for one or more of the following three parameters so that the program retains the records meeting the criteria. For multi-org enabled customers, this program deletes only the records belonging to the org from which the program is run.
Log Retention: Enter the retention period. For example, if a value of 30 is passed then program retains the records created in the last 30 days and deletes the remaining.
RC Id: All the log records will be deleted upon retaining the records related to the RC Id entered.
Log Level: All the log records will be deleted upon retaining the records whose log level value matches the entered value.
Upon providing the desired value(s) for the program parameters, click the Submit Job button. You will get a pop-up message with the request id of the submitted job.
Did you know: Log retention program must be run on a scheduled interval as part of the application maintenance activity.
How to run/schedule the log retention program in the FOEX UI?
Navigate to Reports >> Schedule Jobs. Click the Schedule Job/Job Group button on the Schedule Jobs screen.
In the resulting screen, under the Schedule Program tab, click the down arrow available against the Program Name field in order to select the Revpro3.0 Log Retention from the list of available programs. Select the desired date & time for the Start Date if the program must run at a specified time in the future; otherwise leave the field with the defaulted date and time. If the program needs to be scheduled to run in a desired frequency, then select the appropriate options under the Recurring Setup block.
Click the Program Parameters tab and select the desired values for the program parameters and click the Submit Job button.
... View more