...
Please see attachedCRSM Integration Docfor details. As always, please feel free to contact with MOLE team for further help needed.
You are Done!
Enhancements/Updates: During the CRSM integration with Vessel Registry(LOB 001). We found some interesting stuff that would be helpful and avoid the hiccups for other lines of business to consider or implement. The following are the important to consider:
Payment event and expected values from LOB:
When you update or save payment details from your application before or after a service request is completed to generate remissions or invoicing on the CRSM side, WLM expects the following values to be provided to update the payment table in WLM. Once we receive the payment details, then the WLM forward the same to the CRSM side via service bus to generate invoicing.
...
If you are using WLM v2 endpoints, you might need to pass additional information like invoice number and transaction ID
How to add or edit new statuses:
First, find out the list of value types available in LOV by calling the endpoint:
...
For example: A list of value types for “VesselREgistryRequestStatus” is enabled.
You can now get the actual list of values for “VesselRegistryRequestStatus” using the below endpoint:
...
If you would like to add the new status to an existing one, you need to call the PUT endpoint.
You need to add the LOB status in “MTOAStatus” by querying it first as like below, once you get the list, you need to add custom properties as highlighted in RED below:
You need to pass the LineOfBusinessId, ListOfValueType, LOBStatusId and ServiceId:
| Code Block |
|---|
https://ncdlistofvalueapp01.azurewebsites.net/api/v2/ListOfValues?ListOfValueType=MTOAStatus |
How to evaluate service performance:
How to evaluate remissions:
How to evaluate invoicing:
Introduction of MTOAStatus mapping:
Implementation of using generic system id:
How to reach MTAPI platform in case of any issues/failures:
Need to update LOV values in ListOfValueService.