In some extreme scenarios, after a policy or an endorsement is issued, it is necessary to modify the information related to the policy, but this information has nothing to do with the policy coverage, such as the print history of the policy.

At this time, it is obviously not appropriate to use the endorsement to change it, so we designed the PolicyOtherInfo model to save the additional information of this policy.

At the same time, in the separate API we provide, we will set the additional information to the Policy object. So when the additional information is modified, the ES information of the policy will also be updated, so as to achieve the effect of reusing the policy ES of the supplementary information.

Throught this document, we will use an printing information field to provide example.

Configuration

User can configure and extend new field in data dictionary.

Policy Other Info API

We have designed 3 APIs to maintain the additional information on the policy:

Save API

/proposal/v1/policyOtherInfo/save

In the request body of the API, the PolicyId is required. If the OtherInfoId exists then updating the object, others create a new one. The PolicyOtherInfo entity has OneToOne relation to Policy entity.

{
    "PolicyId": 855001601,
    "DocumentPrintNo": "D855001601",
    "LastPrintDate": "{{NowDate}}",
    "PrintCount": 2
}

Response body:

{
    "DocumentPrintNo": "D855001601",
    "LastPrintDate": "2020-04-21",
    "OtherInfoId": 23855183401,
    "PolicyId": 855001601,
    "PrintCount": 2
}

Load API

/proposal/v1/policyOtherInfo/loadByPolicyId?policyId=855001601

Because the PolicyOtherInfo object is OneToOne relation to Policy object, so we use PolicyId to load it, and it will return null if PolicyOtherInfo does not exist for this PolicyId value.

Response body:

{
    "DocumentPrintNo": "D855001601",
    "LastPrintDate": "2020-04-21",
    "OtherInfoId": 23855183401,
    "PolicyId": 855001601,
    "PrintCount": 2
}

Delete API

/proposal/v1/policyOtherInfo/deleteByPolicyId?policyId=855001601

If we don’t need this PolicyOtherInfo, we can delete it. It should be noted that unlike the liability information of the policy, physical deletion is adopted here.

Response body:

{
    "Status": "OK"
}

Endorsement Other Info API

Unlike the policy model, the additional information on Endorsement model uses dynamic fields to store, and it can be modified at any point in time. From business perspective, however, only some special fields can be modified after issue, and updateEndorsementAfterIssue API is used to modify those fields. Only field name starting with “OtherInfo_” can be modified.

/endo/v1/updateEndorsementAfterIssue

API Method: POST

Request data：

{
    "EndoId": 855039631,
    "EndoStatus": "300",
    "EndoType": "1",
    "OtherInfo_PrintStatus":"Y",
    "PolicyNo": "POTBTI00000270"
}

Response data：

{
    "AfterRevisionId": 855039630,
    "ApplyDate": "2020-03-30T08:38:33",
    "BeforeRevisionId": 855039513,
    "BeforeVatPremium": 0,
    "Commission": 0,
    "DuePremium": 0,
    "EndoEffectiveDate": "2020-03-30",
    "EndoId": 855039631,
    "EndoNo": "POTBTI00000270-001",
    "EndoStatus": "300",
    "EndoType": "1",
    "EntryOperId": 17312387,
    "IndexNumber": 0,
    "IsAdminChange": "Y",
    "IsLockedByRi": "N",
    "IssueDate": "2020-03-30T08:38:34",
    "OtherInfo_PrintStatus": "Y",
    "PolicyId": 855039506,
    "PremiumInterest": 0,
    "ProductCode": "TBTI",
    "ProductId": 351925022,
    "SubEndoType": "11",
    "TaxInterest": 0,
    "TotalInterest": 0,
    "TotalPremium": 0,
    "Vat": 0
}