Hi Samir,

Please find below details.

Current Implementation:

• On sent form preview will save mapped field data to database.
• On review and sign page will update data for mapped to database and non mapped fields & JSON attribute along with mapped fields.

Questions:

• If we are showing data of document when it was sent. So should we considered this in all places like.
  • DMS preview after completing document by candidate[Admin and Candidate]
  • DMS download completed forms.
  • Integration API Viewer screen
  • Integration API Preview.
  • Integration API Download [CBAT & CBES].
  • Embedded UI.
  • Document completion email thumbnail.

• If we are implementing this in all place, then when latest data get shown.

Samir Please provide details on above so we will proceed further.

CC-Rohan J Khandave,Priya Dhamande

Thanks,
Ganesh

Adding scenario to on above if JSON attribute not present then will show the data from database.

CC-Rohan J Khandave,Samir

Implementation details :
1. Document when sent through Send forms from UI, all form data will be saved as JSON against that document.
2. When document is opened by candidate,data will be populated from saved JSON. On Submit or decline, form data (JSON) will be updated for that document.
3. Document when sent through Custom API's by Admin (senddocument as 0,1,2), form data is not saved in this case. When candidate opens the link, latest data from DB will get populated on PDF. Data will be saved once candidate clicks on Submit or decline.
4. Form data will be saved when document is saved by Admin when it is sent from Custom API with senddocument as 3 and same will be populated when candidates opens the document.
5. Signature will always be fetched from DB. 

Basic Scenarios:
1. Send document from Send forms -> Candidate opens the document -> Candidate Declines -> Admin changes the document and send through send form -> Candidate accepts
When document is opened/downloaded from Review/Sign or Completed Forms Library, data of that particular document will be downloaded.
 2. Document sent with Custom API's (api/candidate/custom/document/create and api/candidate/document/create) 
When senddocument = 0,1,2 => DB data will be fetched when candidate opens the document
When senddocument = 3 => Admin opens the link to make changes ->changes saved -> data is saved against that document -> candidate opens document -> recently saved data will be displayed.

Files Affected :

1. DMS\Databases Objects\04_Stored Procedures\DMS_SP_GetTemplateFormMappedDetails.sql
2. DMS\DMS.App\src\DMS_AppLogic\BuisnessLogic\DocumentData.cs
3. DMS\DMS.App\src\DMS_AppLogic\BuisnessLogic\PersonData.cs
4. DMS\DMS.App\src\DMS_AppLogic\IntegrationLogic\GenerateDocument.cs
5. DMS\DMS.Web\src\DMS_WebApp\ClientApp\src\app\admin\send-forms\forms-preview\forms-preview.component.ts
6. DMS\DMS.Web\src\DMS_WebApp\ClientApp\src\app\candidate\document-review\document-review.component.ts
7. DMS\DMS.Web\src\DMS_WebApp\ClientApp\src\app\Shared\Components\modals\modals.component.ts

Environment: production
login: Admin and Candidate
Browser: FF and Chrome

Points covered:

1. Able to send document to different candidate with different data
2. Different candidate should reflect data as per added by Admin on Completed Sent Forms Library
3. Data updated by Admin should be saved
4. Checked Candidate 1 for its respective data
5. Checked Candidate 2 for its respective data
6. Two same document send to same candidate - latest saved
7. Two different documents send to same candidate - latest saved
8. Send documents 0, 1, 2 and 3 through API

All scenarios worked as expected.

So, marking jira done.

Samir Rohan J Khandave Hrishikesh Deshpande Sachin Hingole Ramya Tantry