Hi Molly Ronovsky

Can you please review the attached "Edit PDF"

Regards,

Samir

Dinesh Arora Ravi Banda

Hi Samir,

Couple of questions:

For the applicable user rights - we are saying there are two types of users, an admin and a regular user, correct?
Yes, Admin and CandidateShould there be one more? Because I was thinking it was just a regular DMS user, not candidate. For example, salary - maybe could be editable by admin but not regular dms user. Let me know your thoughts.

DMS Fields - are these the only fields under consideration, or will all fields have the same security around this? I believe it will be any mapped fields, but want to be clear.
Yes,Any mapped field

If a field is not mapped, but in the form, what is the behavior for this? For example, I have a field that asks 'Mother's Maiden Name' that as a candidate, I should be able to fill out. This field is not in CBAT, therefore, I have not mapped it. However, it needs to be mandatory. What happens in this case?
As of now only mapped fields can be assigned rights. Let us think on this Thanks this will be important.

Rights - mandatory - does this mean it has to be completed before candidate can sign? If a user has setup that it is mandatory when creating the form in Adobe PDF, will the DMS know this, or does user have to check that here again, as well? Do the Adobe PDF preferences get acknowledged at all? If there are check boxes, choice fields in the document, will they still work the same? As discussed on call - you said Adobe PDF settings will not be taken into account, so we should tell clients not to set up there.

What does 'No rights' mean? When would you use this? Per our call, you all were going to go back and make the labels clearer to avoid confusion
Let me know if you need me to clarify anything!

CC: Samir, ShashiKant Mishra,
Hi Molly Ronovsky,

Can you please let us know priority for this ?

Thanks,
Swapnil p

Swapnil Pandhare High - this would need to be available with what we first release. Email templates, etc. aren't as important as the behavior for forms, etc.

Hi Samir,

I'm done with the UI integration and also done the changes as we have discussed.

Also, put the validation message on pop up and changed the logic for submitting the form.

Thanks

Narendra

Hi Samir,

I have integrated fields rights for already mapped fields coming through GET API but its not saving right now as update service is not functioning for this.

cc - Ganesh Sadawarte, Ramya Tantry, Komal Barde

Thanks

Narendra

Hi Narendra Kumar,

We have verified on preproduction.
When we change the rights for fields while creating template, at the time of preview changes are not reflecting.
Eg : field mapping : First name is view only, then while preview document with admin first name should not be able to edit

Actual : we are able to all the fields in case of preview

Not working as expected

Re-opening this ticket

Thanks,
Jayshree

Priya Dhamande Hrishikesh Deshpande Sachin Hingole Satya Samir

Hi Jayshree Nagpure,

In this ticket we are just setting the fields rights, we are not implementing it in preview and review and sign page. For that functionality, we have another task that is DMS-948.

If you are able to set rights and getting the same rights during the edit of the same template, means it good to go.

Thanks

Narendra

Ok Narendra Kumar.

We will close this ticket once DMS-948 will deployed and tested.

Priya Dhamande Sachin Hingole Hrishikesh Deshpande Satya Samir