Choose application-specific vs universal form views

If your source or destination application has an application-specific connector, Celigo developers have organized a connector form that contains all relevant connection criteria to integrate with that platform specifically. If you are integrating with a service that does not yet have an application-specific connector in integrator.io, you can still create a connection with the platform using a universal connector form. 

Universal connectors have the following types:

• AS2
• FTP
• HTTP
• REST API
• Wrapper

Any application that can sync with integrator.io relies on one of the above universal connector types, but application-specific connectors only display fields relevant to a given application's connection protocols. Application-specific forms are based on universal connector forms, but they exclude any fields that are irrelevant to integrations with their specific service.

Form view options

The General section of export and import configuration pages have a Form view drop-down menu that allows you to switch between an application-specific form (if available) and a universal form. The following image displays the form view options available for an Acumatica import or export.

You can use the application-specific form view or the REST API universal connector form view. Since Acumatica's platform uses REST API protocols, only the REST API universal connector form view is available.

Reasons to switch from an application-specific form view to universal connector form view

Most configuration forms in integrator.io (application-specific or universal) are dynamic because they add, change, or remove fields based on your selections. For example, the fields you see on a form that’s using a GET method display different fields from those you see on a form using POST.

Since universal connector forms are not specific to any app or system, they display more fields and settings than are required by any single platform because they must account for various systems that use those protocols. Whenever possible, you should rely on an application-specific connector form so that you don't have to navigate or ignore fields that are irrelevant to your integration; however, a universal connector form can occasionally be helpful for API updates that have not yet been accounted for by an application-specific connector form. If the app or system that you’re working with has updated its API, you can keep up with those changes in cases where the app-specific form does not yet include the expanded functionality. For example, if the API gives access to an expanded menu of resources or pagination capabilities, you can use the universal connector form view to work with those changes in your export or import.