ЕСОЗ - публічна документація
RC_Сomplete Device dispense
Purpose
This WS is designed to complete Device Dispense
Key points
Only authenticated and authorized users with appropriate scope can invoke Complete Device Dispense
Device Dispense is completed in async way. Successful result of the job should return a link to the existing Device Dispense (look at Get Device requests by search params )
Complete request must be signed with Digital Signature. So, all the Device dispense data must be signed and submitted.
Specification
Authorization
Verify the validity of access token
in case of error - return 401 (“Invalid access token”) in case of validation fails
Verify that token is not expired
in case of error - return 401 (“Invalid access token”)
Check user scopes in order to perform this action (scope = 'device_dispense:complete')
return 403 (“Your scope does not allow to access this resource. Missing allowances: device_dispense:complete”) in case of invalid scope(s)
Validations
Validate digital signature
Validate request is signed
in case of error - return 400 (“document must be signed by 1 signer but contains 0 signatures”)
Validate that DS is valid and not expired
Validate that DS belongs to the user
Check that DRFO from DS and party.tax_id matches
in case of error - return 422 (“Does not match the signer drfo“).
Validate legal entity
Extract client_id from token
Check legal entity status is ACTIVE
In case of error - return 409 ('client_id refers to legal entity that is not active')
Validate Device dispense
Get Device dispense identifier from the URL
Check Device dispense exists in DB (ME DB)
in case of error - Return 404 ('not_found')
Check Device dispense belongs to the same legal entity
in case of error - Return 404 ('not_found')
Validate payment_amount
Check it is present if program was set
in case of error - Return 422 (Required property payment_amount was not present)
Validate payment_id
Check it is present if program was set
in case of error - Return 422 (Required property payment_id was not present)
Validate Device request
Validate value in the field $.based_on ($.based_on.identifier.value), Reference on device request, required.
Сheck that Device request is_active = true and status == 'ACTIVE'
in case of error - return 409 error ('Device request is not active')
Validate User
Extract user_id from token
Check that device dispense is completed by the same user who created it
User from token must match with device_dispense.inserted_by
in case of error - Return 404 ('not_found')
Validate signed content
Check that signed content is equal to device dispense stored in DB
Do not compare:
payment_amount field
payment_id field
status
status_reason
performer_legal_entity
inserted_at
updated_at
signed_content_links
in case error return 422 ("Signed content does not match to previously created dispense")
Validate transition
Get status of Device dispense by $.id in ME DB. Check that Device dispense is in status ‘IN_PROGRESS’
in case of error - return 409 ("Can't update device dispense status from {status} to COMPLETED")
For more information look at RC_Device dispense status modelarchived
Service logic
Save signed content to media storage, in bucket pointed in MEDIA_STORAGE_DEVICE_DISPENSE_BUCKET chart parameter
Fill in the following fields:
signed_content_links. Add string item in the array with a link(s) to saved content in media storage
status = COMPLETED
updated_at. Set current date and time
updated_by. Set current user from token
Save (update) data to device_requests collection in MongoDB according to RC_Device request data modelarchived : set device_requests.status = COMPLETED (as all its quantity has been provided by Device dispense)
Send
StatusChangeEvent
to Event Manager for Device Dispense and related Device Request
ЕСОЗ - публічна документація