Configure converted Adaptive Form

So on successful conversion of a PDF document into an adaptive form, you will get an email notification, if you have configured the email service, or you can go into this - folder, the DHCS Folder, which contains your original PDF document. And here, if the form is - converted successfully, you’ll see us converted labeled - on the top of the form here as you see, and the converted form is - placed in the Output Folder.

So this is our converted - form from the PDF document, and it has the same name as - your original PDF document. And there’s also another - folder called Schema, which contains a schema. So this folder Schema and - the schema are created by the Automated Forms Conversion service. And the schema is used to merge data back into your PDF document - from the adaptive form. So typically you will not - interact or do anything with the schema so leave the schema as is. So let’s go back to our - form that was created by the Automated Forms Conversion service. So this is the form. Let’s take a look at some - of its properties here.

So the form is associated - with a team called . So this is the same team that we uploaded when we converted the PDF - document into the adaptive form. And the configuration - container is left blank because when we converted our PDF document into adaptive form, we did not have an option to specify a configuration container. So let’s specify an appropriate - configuration container. So if you remember, we had created a configuration - container called Adobe rocks and the cloud services - configuration that we created to integrate AAM with - Adobe sign was placed in this particular - configuration container. So by associating our adaptive form with this configuration container, we make sure that any cloud - services configurations that are presenting the Adobe - Rocks configuration container will be available to you when you’re configuring - your adaptive form.

The next thing we need - to do is take a look at the form model. So there’s a schema, so the form is by default - associated with the schema. So this is all done by the Automated Forms Conversion service. So don’t touch this, don’t - change any of these things here. And then if you scroll down, there’s a document of record, - template configuration. So our form is associated - with the PDF document that was uploaded. So since our adaptive form is based on the underlying PDF document. So this is our PDF documents. Our adaptive form is based on - this underlying PDF documents. So we have Automated - Forms Conversion service has associated that PDF - document with the adaptive form and that PDF document - will be used as the basis for our word document of - record template, right? So again, don’t change any settings here, leave them as is.

So once you have done that, the next thing is to open - the form in the Edit mode and take a look at the - form that was created by the Automated Forms Conversion service. So to open the form in - that it mode select this, and click on Edit to open - the form in the edit mode.

So we have opened our - adaptive form in edit mode. The next thing we need - to do is to configure this adaptive form with Adobe Sign. But before we do that, I wanted to show you certain things which our Automated Forms - Conversion service has done. So it created two tabs and - placed them under the root tunnel and those two tabs are - called page one and page two. And each of these tabs - contain some fields. For example, page one, - contains descendant’s name, social security number and so forth. And in the similar manner, page two contains some fields here.

So typically the customers - would rename the titles of these particular tabs here. So if you want to rename - that you will rename it by opening up the page once - configuration property sheet and changing the title.

You can also rearrange the fields. For example, the descendants - name field is taking up the entire width of the form. If you want, you can resize the field by - going to the Layout editor and changing the width - of this particular field by dragging this field here. So it occupies half - the width of the panels and in a similar manner, you can do it for the - social security field, so that those two fields - appear next to each other. So this way you can rearrange the fields as to your preferences - or as per your liking. So let’s go back to the Edit mode, I want to show you one important thing. So when we create an adaptive - form from a PDF document using the Automated - Forms Conversion service, as you noticed earlier, it creates a schema - and this field is bound to that element in that schema. So for example, the - descendants name field is bound to an element in the schema. And that element is also for - the descendants name here and there’s an acro form data binding. So what we recommend is do - not change these two settings unless you know what you’re doing. So don’t change these two - settings, leave them as is, and also don’t change the - name of the field here. You can change the title, you can add some placeholder text, you can mark this field required or not, but do not change the bind reference and the acro form data - binding and the name of this particular field. So the next thing I wanted to show you was our original PDF document - contains a signature field and the Automated Forms Conversion service was intelligent enough to identify that signature field, and it placed a signature - field on page two of our form here. So if you go to the bottom, here is the signature field here.

So the next thing we need - to do is to configure this particular form with Adobe Sign, so that the user filling this - form, we’ll be able to sign this form using the Adobe - Signature integration. So to do that, let’s open - up the phone container here, open up its configuration property sheets, and go to the electronic - signature section here, make sure enable Adobe Sign is checked and select the appropriate Adobe Sign cloud services configuration. If you notice our cloud - services configuration that we created was placed - in a configuration container called Adobe Rocks. And our adaptive form is - also configured to use the same configuration container. Hence, we are seeing this Adobe sign cloud - service configuration, then the other two clouds, Adobe sign cloud service - configurations are coming because they were placed - in a configuration container called Global. Hence, we are seeing those, select the appropriate cloud service here, and since our form has only one signup, it’s going to be sequential, and by default, the signer one is added. So let’s configure the signer one. Since the person filling - out the form and signing is the same. We need to specify this option here, Yes, and every person who signing the form, needs to have an email - address associated with it. So the way you specify an - email address is either by choosing one of these three options. In our case, we are going to say, use the email address - specified provided in the form. And that email address is - in this particular field, and that field can be selected - from this drop down list. This drop down list, lists all the fields - in that adaptive form, you select the appropriate field which contains the email - address, select that, there is no authentication method here and leave this field blank - and save your settings. So the next thing we need - to do is to configure a submit action with the form. Every form needs to have a submit action. So in our case, we have specified the - forms portal submit action. So here it lists the - various submit actions that can be configured - with an adaptive form that is configured to use Adobe Sign. So, in our case we’re - going to select the forms for the submit action and - save that setting here.

So if you notice we are not using a signature step component in form, without using the - signature step component, you can still fill out the form and sign, but the experience will - be slightly different. We will show you this - experience in the next video.

So I’m now ready to fill - out this form and sign using the Adobe Sign interface. So let me open this form in - the preview mode as HTML, that active form is rendered - and there are two tabs page one and page two, and each of these - tabs have some fields here. For example, page one - has a descendant’s name, social security number, date of birth, I can enter some values here. Date of death here, will the estate be - probated I can click on Yes and then go to page two. And this is an email - address filled in here if I want like an enter - some additional values here. So this is the email - address that is associated with the person filling - in signing this form. And once I’m satisfied - with all the information that I’ve entered, I can click on the Submit - button to sign the form using the Adobe Sign’s interface. So when I hit the Submit button, the data from the active form is merged with the underlying PDF document. And the PDF document will - be presented to me to sign, using the Adobe Sign interface. Give it a couple of seconds more, the document will be - presented in this tab here.

So this is the PDF document - with the data merged from the adaptive form so the descendants name is - here, social security number. If you notice, I’m not able to change - any value in this field that is because my underlying PDF, those fields were marked as read only. We will take a look at - how to map those fields in the next video. Some of these fields are - not marked as read only, hence I’m able to enter some - values here in this fields. And if I’m ready to sign, I can scroll down to the - bottom of the form here and click on this field, which is identified by Adobe - Sign as a signature field. And I click to sign. Here I can type in my name to sign, and click on apply to apply - the signature, click on Sign. So once the signing ceremony is complete, I can download a copy - of what I just signed.

And this is the signed - document here, with the data and my signature has been - placed in the correct signature field that was specified - in the PDF document. So this is how you can take - an existing PDF document with the signature field on it, convert it into adaptive form, present that adaptive form - for the user to capture the information and use - the Adobe Sign interface to capture these person’s signature.

So when we were signing the document using the Adobe Sign interface, we noticed that some of these - fields were not editable, meaning they were read only while some of these fields were editable I could enter values or select - some appropriate options. So the reason for that is because in my - underlying PDF document, this is my original PDF form. Some of these fields - were marked as read only, and some were not. And to Mark certain fields as read only, we need to open the document - in using Adobe Acrobat and select what we call here as an Edit prepare form options, select this option, do not select the read PDF option, select Edit prepare form option, and that identifies the fields and you can open up the fields properties and mark it as a read only. So that means after the user has been presented this document using the Adobe Sign interface, he or she will not be - able to enter any values because that field is marked as read only. In a similar manner, we had the descendants date of death, mark it as read only. And the other thing I - wanted to show you was, the format of the date here. So this is the date - format here, MM/DD/YYYY. And that’s the same - date format that we see when we are presented the - document for signing here that’s the same date format here.

So this way you can control - what fields the user will be able to enter values into - using the Adobe Sign interface. But as a best practice, we would recommend that the - entire data capture is done using the adaptive forms interface and the Adobe Sign interface. It’s only shown for the user to sign at the designated location. -