CPE Monitoring Integration-3 - Beware of duplicated requests

Video Transcription

There is a second caveat with CPE monitoring. When Oasis make the API call to CPE monitoring, and let's say I submitted a correct UAA number that is valid in their system,  I submit the correct user information because I know my information, and the activity date, either today's date or the date that you have entered in the system  is within the CPE monitor's registration, the first API will work. However, the second time I submit it, using the same information will fail. And the reason it will fail is because  it is very important here. CPE monitoring will reject a duplicate credit request. And the duplicate credit request is defined as the same user with the same UAA number  on the same activity date. So this is very important. When you're testing your integration, the very first API call will work, but if you're using the same UAA number  in multiple activities, you are going to run into a failed API call on the second activity credit claim because CPE monitor will consider that as a duplicate request,  and CPE monitor does not allow the same user claim under the same UAA number on the same activity date. And that is a constraint within CPE monitor that OASIS cannot work around.  Thank you.

Video Summary

CPE monitoring has a limitation regarding duplicate credit requests. When making an API call, if the user submits the same information (UAA number, user details, and activity date) that was previously submitted, it will fail as CPE monitoring rejects duplicate credit requests. The system considers it a duplicate if the same user with the same UAA number claims credit for the same activity date. This constraint cannot be bypassed by Oasis. So, it is crucial to be mindful of this limitation when testing the integration to avoid failed API calls on subsequent activity credit claims.

Meta Tag

Creation Year 2023

Keywords

CPE monitoring

duplicate credit requests

API call

UAA number

activity date