Function: submitOrder

The outsourcing of a task involving a claim or policy to a third party.

Usage: submitOrder

The submitOrder function is used to outsource a task to a third party. The request contains essential and relevant information with regard to the party, policy and/or claim. It is recorded with AFD attributes, and complies with the AFD structures for party, policy and claim (see also chapter AFD structures).

# Variant Description
1 riskAssessment Evaluate risk exposure of a (potential) client, insured person or object.
2 appraisal Establish the value of a (potentially) insured object.
3 medicalExamination Assess the medical condition of a person.
4 lossAdjustment Determine recovery/repair or replacement cost of an insured object.
5 repair Repair or partially replace a (damaged) insured object.
6 salvage Salvage a damaged insured object.
7 repatriation Transport a person, object or vehicle back to the place of residence of the insured.

Technical specifications: submitOrder

Input: submitOrder

Name Variant Type Description
orderStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
entityType all string Set to ‘default’.
dataCatalogVersion all ADNAFM Version of the data catalog on which the message is based.
functionVariant all APIVAR The function variant is used to determine the additional set of required and optional input and output data.
order all Request for a service by a third party.
entityType all string Set to ‘default’.
jobTypeCode all string Job type, code.
jobTypeDescription all string Additional information about the job.
desiredExecutionDate all date Desired date of execution.
party all With entityType principal.
party all With entityType contractor.
Other attributes of the order entity.
partyStructure 1
policyStructure 1, 2, 3
claimStructure 3, 4, 5, 6, 7
loanStructure 1
pensionStructure 1
Other available AFD structures.

Output: submitOrder

There are three basic types of output which are described in the Output section of the Design principles chapter.

A positive response for the submitOrder function may contain a dataset. The minimal result is a reference to the transaction with the number, the expiry date and the offer amount plus possible taxes and costs.
In order to simplify processing it is advised that the input data is returned in the output for reference. Any additional information that was collected during the transaction may also be added to the output for reference purposes.

Name Variant Type Description
orderStructure
commonFunctional Entity for general information with regard to structure, handling and processing.
entityType all string Set to ‘default’.
dataCatalogVersion all ADNAFM Version of the data catalog on which the message is based.
functionVariant all APIVAR The function variant is used to determine the additional set of required and optional input and output data.
order all Request for a service by a third party.
entityType all string Set to ‘default’.
jobTypeCode all string Job type, code.
jobTypeDescription all string Additional information about the job.
statusType all string Indicates how to process the entity.
Other attributes of the order entity.

Errors

When a negative response is generated, it follows the general rules as described in the Error section of the Status codes and error handling chapter.

Click below to see the Open Api Specification (3.0.0)

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment