Review Guidelines

When you submit an extension for review, we (The Zoho Books team) will check the extension for vulnerabilities and assess compliance with our review guidelines.

If the extension does not violate our guidelines, it gets approved and you can publish it in Zoho Marketplace. If the extension violates our guidelines, we will send you an email mentioning the reasons for rejecting the extension and the changes that have to be made in the extension. You will have to make the changes mentioned in the email and submit the extension for review again.

The guidelines followed by our team when reviewing an extension are listed below:

Common Guidelines

• Check the components and scripts used in the extension to ensure that no unwanted or unused components are present.
• Check that no more than 5 custom fields are used in each module.
• Check the installation and uninstallation processes for the data collected and actions performed by the extension during these processes.
• Check that the extension name does not contain the name of the product of which it is developed. For example, Twilio instead of Twilio for Zoho Books.

Guidelines for Connections

• If an extension contains scopes, check that only the scopes that are necessary for the connection are used.
• If the authentication type is OAuth2, check that the authorize URL field contains access_type=offline.
• Check that the connection name is a combination of the service name and the extension name, separated by a hyphen in Pascal case. For example, ZohoBooks-Twilio.
• If individual users of an organization have to connect and authorize the connections used in the extensions, check that the value for the user access param is true.

Guidelines for Custom Scripts

• If the extension will be used in other Zoho Finance apps, check that internal SDK methods are not used.
• In the invoke URL calls, check where the data is being used, and what action is performed using the data.
• Check that the invoke call’s URL contains api_root_endpoint.
• Check that components are not created using scripts.
• If comments are used in the custom scripts, check that no personal or sensitive information are added as comments.
• Check that the script used is scalable. For instance, if data is being fetched, check that the data is retrieved only the necessary number of times.
• If the send mail param is used, check what data is sent to the developer.
• When comparing the name of a field with a string, use the API field name for comparison instead of its label name. For example, if a custom field’s label name is “Landmark” and its API field name is “cf_landmark”, compare using custom_fields.get(“api_name”)" == “cf_landmark” and not custom_fields.get(“label”) == “Landmark”.

Guidelines for Widgets

• If widgets are used, check that they adhere to the style used in the Zoho Books user interface.
• Check that the widget’s data is not displayed in the console tool.

Guidelines for Global Fields

• If a global field is used in a custom script, check that the “Allow use of Global fields in this custom function” option is checked.
• If the data type of the global field is Users or Roles, and notifications are sent to the users or roles, check that the value for the is_mandatory param is true.

Guidelines for Schedules

• Set the param User Access to false in connections if you’re using schedules.

Was this document helpful?

Yes

No

Let us know where we can improve

Enter your comments or feedback on this page

Enter your email address

Refresh

Type the characters you see in the image above

By clicking Submit, you agree to our Privacy Policy .

Submit Cancel

Submit

Submit

Thank you for your feedback!

Want a feature?

Suggest