-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Company:All Clients/Multiple Clients
1. /api/documents/
{sourceProductId}/document/
{id}/LatestStatus2. /api/documents/sourceProduct/{id}
/LatestStatus
Parameters :
sourceProductId-Onboard
documentId-173
personId-ABSSG
BASIC-dXNlcl9nb29kOnBhc3NfZ29vZA==
accountDid-A7F0PT78MTMZ470WBBT
userDid-dmsuserid4cmp1
Swapnil Pandhare Priya Dhamande Hrishikesh Deshpande Sachin HingoleSamir
- relates to
-
DMS-525 Getting Document status API
-
- Done
-
Hi Rohan J Khandave,
We have verified through postman.
Verified status and history status when no person ID exists.
History details are getting fetched.
PFA -
Working fine.
Closing this ticket
Thanks,
Jayshree
Priya Dhamande Swapnil Pandhare Samir Hrishikesh Deshpande Sachin Hingole
Jayshree Nagpure (Inactive)
added a comment - Hi Rohan J Khandave ,
We have verified through postman.
Verified status and history status when no person ID exists.
History details are getting fetched.
PFA -
Working fine.
Closing this ticket
Thanks,
Jayshree
Priya Dhamande Swapnil Pandhare Samir Hrishikesh Deshpande Sachin Hingole 
Hello Jayshree Nagpure,
As per our discussion can you please confirm with Postman.
Current Implementation :
If personid not provided then system use UserDid from header to find person. Provided document is not assigned to UserDid.
Due to that system throwing error as Document data not found.
Thanks,
RohanK