A string to identify the connector
OMC option could be proceeded by selecting OpenG2P Registry.
MTS Field mapping as required by the API. Please refer to MTS Documentation. Format of Mapping would be JSON.
MTS-C only supports JSON output type of MTS.
Output format is a JQ string 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 provide both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS.
Mosip language setup. Default is eng.
Interval at which the MTS-C job runs.
Filters to apply to Registry
A domain filter can be used to identify the records for tokenisation. For. eg. Only records which have VID associated with it and are not tokenised need to be picked for tokenisation.
List of fields to be used
List of fields which will be supplied as auth data. This field list may be a superset of fields required for auth as it may contain data required by the callback API. This list should be a valid JSON string array.
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.
URL Endpoint that would be called to perform authentication for the callback.
DB instance used by Odoo.
Username to access callback API
Password to access callback API