Community - About VishG

VishG

Question: How to schedule a workflow to run on the last day of every month? For example, how to schedule a run on 1/31, 2/28 (2/29 in a leap year), 3/31, 4/30, 5/31, etc.? Solution: The workflow uses CRON expression for scheduling. To schedule the workflow to run on the last day of every month, you can use the 'L' flag in the Workflow settings as follows: For example: 0 12 L * * This means that the workflow shall run on the last day (30th) of April at 12:00 Pacific Time.

VishG

Error: Your subscriber portal customers might encounter the following error: "You do not have permission to edit your autopay settings. Please contact customer support to change your settings." Solution: Please make sure the AutoPay Account field is selected in the Subscriber Portal Configuration. Navigation: - Launch your Subscriber Portal Application. - Switch to the Configuration Tab - Scroll down to the Field Display Configuration and select Account Fields - Select the AutoPay field if you want your users to manage this field - Save Settings.

VishG

Problem: - Login Issues for Marketplace/Collect apps - How to install an App Solution: Please watch this video for a generic connect login issue or a process to install an App in the tenant. Supported links from the video: Link Connect Account Create a support ticket Create API user / API role Create OAuth Credentials Create OAuth Tenant Login (alternative to the step at 4:37 in the video)

VishG

Error: "Did not provide valid BAI data (does not start with 01 File Header record) or valid file name." Solution: Different banks call different file types differently. Zuora supports this type of BAI (Bank Administration Institute 2) file under Fixed Width Text - Multi-record (FWTMR). Please select Fixed Width Text - Multi-record (FWTMR) file format and try again.

VishG · ‎03-19-2021

Question: Why do I get 403 Forbidden Error when I try to access Workflow from my Services Tenant? Answer: Workflow is not supported in legacy Production Copy Environments (PCE) Please see the below limitations for PCE environments: https://knowledgecenter.zuora.com/BB_Introducing_Z_Business/D_Zuora_Environments/Legacy_Testing_Environments We have introduced a new environment called Central Sandbox that provides the functionality of Production Copy Environments (PCEs) and Enhanced Production Copy Environments (ePCEs) Please refer to this notice on the community for more details: https://community.zuora.com/t5/Maintenance-Notifications/Notice-of-PCE-ePCE-PTE-End-of-Life/ba-p/34487.

VishG · ‎03-12-2021

Error: "Invalid Login, please check username and password or URL endpoint" Solution: 1) Verify if you are using the correct endpoint URL API Sandbox: https://apisandbox.zuora.com/apps/services/a/80.0 US Production: https://www.zuora.com/apps/services/a/80.0 EU Sandbox: https://sandbox.eu.zuora.com/apps/services/a/80.0 EU Production: https://eu.zuora.com/apps/services/a/80.0 NA Sandbox: https://sandbox.na.zuora.com/apps/services/a/80.0 NA Production:https://na.zuora.com/apps/services/a/80.0 2) Verify if you are entering the correct username and password of the Zuora tenant you are creating a login for. 3) If all the above steps are exhausted, please check if your user is SSO enabled in the tenant: If this is the case, unfortunately, connect does not support SSO user credentials. The workarounds for the above scenario are as follows: a. Create a non SSO-enabled user and use it in connect. b. Create Oauth credentials against the SSO-enabled user in Zuora and then create Oauth Tenant Login.

VishG · ‎03-11-2021

Use Case: Create a comma-separated approver list (of email addresses) in global constants and use it in manual approval task.

VishG · ‎06-18-2020

Maintenance Window: 19:00 PDT - 21:00 PDT on Thursday, June 25th, 2020 Environment Affected: US Hosted Sandbox Environment This is a notice that we will be performing upgrade maintenance on our network Load Balancers on June 25th, starting at 19:00 PDT. During the maintenance window, a brief service disruption will occur for UI and API requests. We are reserving the 2-hour window where most time is in validation; actual work time is approximately 30 minutes, so we expect the total impact time to be considerably less than the window. Potentially Impacted services: UI and API requests A maintenance status message will be posted to this thread at the start of and upon completion of the activity.

VishG · ‎05-06-2020

Solution 1 -> Clear Cache/Cookies of the browser you are using. Solution 2 -> Try to access apps from a different browser Solution 3 -> Please report to us at https://support.zuora.com

VishG · ‎05-06-2020

Getting HTTP 400 error when trying to access Apps from Zuora???

VishG · ‎04-06-2020

While configuring a Tax App, you may encounter issues where a c ustom field on Subscription object is not passed to the Tax connector when a credit memo is generated. To resolve this, you might want to refer the notes below: When a standalone credit memo is created, it will not pass the subscription's custom fields because a standalone Credit Memo is associated with ProductRatePlanCharge. Charges on Subscription are always RatePlanCharges. A credit memo generated from an invoice should be able to pass the custom fields on the subscription level. Thanks.

VishG · ‎03-16-2020

If Refresh Catalog still does not show the custom fields, please also do a Refresh Cache on the workflow Settings page and the custom fields should be available for export.

VishG · ‎03-02-2020

There might be cases where you see messages similar to the screenshot below when you launch any app in connect.zuora.com. Whenever support recommends updating your tenant login, please follow the steps below: Login to connect.zuora.com -> On the left panel Under My Connect -> Click on Tenants Find the tenant which is invalid and Click on Edit. Update the credentials and hit Save Login

VishG · ‎02-03-2020

Application : Tax App Error : "An error occurred in the parsing of the Tax Request! The request received was: No response received" Cause : T he tax vendor did not return a response so Zuora cannot make tax with it. Solution : Navigate: connect.zuora.com -> Under My Connect -> Tenants -> Go to the respective tenant where you have the tax app installed -> Launch the app -> Go to the Testing tab -> Click on the Details tab below Response Body. If the Details section is blank, reaching out to the tax vendor (example Vertex or Avalara) to understand why there was no response returned from them would be the best solution at this point.

VishG · ‎06-04-2019

A single batch of customer accounts can only have one billing preview run at a time. To know the status of any existing BillingPreviewRun you can use the following query on BillingPreview using Postman: https://rest.apisandbox.zuora.com/v1/action/query Request { “queryString”: “select Id, Status from BillingPreviewRun” } Response { “records”: [ { “Status”: “Completed”, “Id”: “2c92c0fb6446273101645dac042e51f7” }, { “Status”: “Completed”, “Id”: “2c92c0fb64c61d3e0164cf41aa8e6d54” }, { “Status”: “Completed”, “Id”: “2c92c0fb6a8c9811016ab08f0cf90941” } ], “size”: 3, “done”: true } You can also use Generic API Utility tool to query on BillingPreview Object The response is as follows: Hope this article was helpful! Thanks.

VishG · ‎06-04-2019

Issue: When trying to trigger a BIlling Preview, this error is received- "API exception while generating the Billing Preview Run: Error Reason Code:59880060 Message: There is already a billingPreview run scheduled for Batch1"

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Schedule workflow to run on the last day of every month

Subscriber Portal Auto Pay Permission Error

Marketplace/Collect Login Issues

Configurable Lockbox Error

Getting a "403 Forbidden" error while accessing workflow

Getting "Invalid Login, please check username and password or URL endpoint" error

Use Liquid Variable on Workflow Approval Task

SCHEDULED MAINTENANCE ON AMERICAS - US HOSTED SANDBOX ENVIRONMENT Thursday June 25th, 2020 19:00 PDT

Re: HTTP Error 400

HTTP Error 400

Custom fields are not passed to the Tax connector when a credit memo is generated.

Re: Custom Fields not showing up

Invalid Login in Connect

"An error occurred in the parsing of the Tax Request!The request received was: No response received"

Re: Developer Tools Error: Billing Preview

Developer Tools Error: Billing Preview