ODK MTS Connector
Overview
Features
Uses callback delivery type of MTS
Completely asynchronous execution
OpenG2P can schedule a daily job to fetch the delta for the day
Manual import feature (TBD)
Configuration
Property | Description |
---|---|
| A string to identify the connector |
| URL for MTS API |
| MTS-C connects over "ODK" which is the first option in this selection. OMC option could be proceeded by selecting OpenG2P Registry. |
| MTS Field mapping as required by the API. Refer to MTS Documentation. The format of Mapping would be JSON. |
| MTS-C only supports JSON output type of MTS. |
| Output format is a JQstring which will be used by MTS to format its output to suite the caller's requirement. |
| Currently supporting only "Callback". Callback feature can be used to make MTS do a submission of results onto an API within Odoo. The output formatting will help in making the desired input for the API. |
| MTS-C provides both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS. |
| Interval at which the MTS-C job runs. |
| MOSIP language setup. The default is "eng". |
| Base URL or the complete domain address for the ODK central installation |
| OData service (.svc) URL for the ODK form to fetch the submissions. |
| Email Id to authenticate MTS for accessing Odata URL |
| Password used to authenticate Odata URL |
| A URL endpoint which would be called upon successful processing at MTS |
| HTTP Method (POST/PUT/GET/PATCH) used while MTS makes the callback |
| Timeout awaited by the callback until acknowledged with a response. |
| Type of authentication expected by callback URL. MTS-C currently support Odoo type which uses the session-based authentication implemented by Odoo. |
| DB instance used by Odoo. |
| Username to access callback API |
Last updated