The language the extension supports. The default and mandatory locale code is "en" (English). View the list of other locale codes supported here.

The product for which the extension is created. For example “ORCHESTLY”. 

Enable or disable data storage for the extension. By default, the value will be false. 

The domains specified in this array can be accessed from the extension. API calls, which is established with a connection, to other domains will not be handed from the extension. If your extension does not use any third-party service, then this array can be empty.

Supported modules: 

Zoho Projects

https://www.zoho.com/projects/help/configure-plugin-manifest.html#modules

Orchestly

https://orchestly.zoho.com/developers/plugin-manifest.html#pluginlocal

When 'type' is "org", only an administrator can fill the configuration parameters on a first-come-first-serve basis. 

connectors 

Connections allow the extensions to integrate with third-party applications using a one-time set up. Connections, once configured and authenticated, can commonly be used in all extensions. For example you have an ongoing task in your Zoho Projects portal and its corresponding ticket in Zendesk is mapped to this task . Whenever the task is updated or a comment is added to the task, the comment should be added in the Zendesk ticket as well. In the same way, if a resource updates the Zendesk ticket, it should reflect in the Zoho Projects' task.

 

In this case functions and triggers can be used to sync the Zendesk ticket whenever there is an update in Zoho Projects task but on the other hand when an update happens in the third party app (Zendesk ticket) then a web hook should be configured to sync that update to the task (Zoho Project). Connectors come handy for this purpose. Click here to see how to configure connectors for various services.

 This key is used when you need customised inputs from the user. For example, the user's domain name in the third party service can be obtained using this key.