-
Type: New Feature
-
Status: Done
-
Priority: High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Integration with CBAT
-
Labels:None
-
Company:All Clients/Multiple Clients
-
Epic Link:
-
Sprint:DMS - Sprint 2, DMS - Sprint 3
Below is the workflow for signing:
- Introduce a field in DMS field mapping for signature
- While creating the document, map this field to document field
- On displaying the pdf this field will be replace by signature of the user
- Once user lands on the “Review and Sign” page, in this case if document required signature than user will be prompted for signing
- This signature will be stored as an attribute with the user data
- Signature will replace the Signature mapped field in the document
- relates to
-
DMS-672 Signature | signature draw/upload > intermittent server error
- Done
-
DMS-692 Signature | Submit | Taking more time to load and throws server error
- Done
-
DMS-658 Signature control | Additional alignment
- Done
-
DMS-659 Signature | Uploading PDF document
- Done
-
DMS-661 Signature | Signature library is missing as per actual requirement
- Done
-
DMS-662 DMS | E Signature | Add Fullstop
- Done
-
DMS-663 Signature | text not adjusting n signature text box
- Done
-
DMS-664 Signature | Once signature is written , not able to edit
- Done
-
DMS-665 Signature | When document is signed and submitted , signature is not visible
- Done
-
DMS-667 DMS | E Signature | Clear button functionality
- Done
-
DMS-668 DMS | Signature | Draw Signature | Submit Button
- Done
-
DMS-669 DMS | Upload Signature | Browse
- Done
-
DMS-670 DMS | Review and Sign | Signature Library
- Done