Environment: Production
API: api/candidate/custom/document/create
Send document: 3
Cache is ON

Points verified:
1. Able to run API successful
2. Link generated
3. Able to open link
4. Able to Save changes for new user
5. Able to Save changes for existing user

Environment: Preprod
API: api/candidate/custom/document/create
Send document: 3
Cache is ON

Points verified:
1. Able to run API successful
2. Link generated
3. Able to open link
4. Able to Save changes for new user
5. Able to Save changes for existing user

Refer screen capture. So, marking jira done on Preprod.

Rohan J Khandave Samir Hrishikesh Deshpande Sachin Hingole

Below are 3C's

Concern: Cache key is not getting removed.

Cause: There issue with config key. We have provided proper key.

Correction: There issue with config key. We have provided proper key.

Environment: Production
API: api/candidate/custom/document/create
Send document: 3

When Cache is ON, getting issue. So, reopening jira for the same.

Refer screen capture.

Samir Rohan J Khandave

Verified on Preproduction
Verified document Link through API
Verified Custom document create API.
Now we are able to create Custom document API.

PFA :

Hence closing this ticket

Thanks
Jayshree

Hrishikesh Deshpande Sachin Hingole Priya Dhamande

Below are 3C's

Concern: System can not fetch sign details error coming when opens link created by create custom api with send document = 3.

Cause: This issue is for new candidates. In create custom api system adds new candidate if not exists. Due to that zero added into cache. When system try to get candidate from mail address get zero. Document saved with zero candidate id. Due to that while fetching signature details system throwing an error.

Correction: We have handled this scenario in code.

CC – Samir