Thanks for answering.
Unfortunately we are not sure that we can understand what exactly you want to achieve. It seems (but we can be wrong) that what you want is the exact workflow of the sample “MVCPrepareFieldsFluent”, which we mentioned in the previous post.
After starting that sample project you will see the next screen. This screen is what we called a “Prepare screen”. When you click the “Save fields” button, you don’t create or save a “prepared document”, but rather all placed fields are saved to the local JSON database (“groupdocs.signature.documents.json” file).
The workflow that is present in a “MVCPrepareFieldsFluent” project is exactly like this:
1) setup document and recipient in code behind
2) then the user is redirected to a prepare screen where he can add and setup the fields he need
3) once “Save fields” is clicked, the fields that are already setup are saved
4) the user is redirected to a sign screen where he can see the original document with fields he has set up on step 2
"FluentSignature.Document()" method returns a new document instance, like an object-oriented wrapper around the document and its fields. If you want to obtain exact coordinates of the fields from the “prepared” document, you should get this existent document using the next line of code:
Groupdocs.Data.SignatureDocument doc = Groupdocs.Web.UI.Signature.GroupdocsSignature.GetDocument(documentGuid);
This “doc” document has all the properties, including list of fields with list of locations. And on this screenshot you can see where exactly are located document coordinates.
But, as we stated before, maybe we don’t understand something, or your vision, how it should work, is not identical with our vision. So, Sam, please, describe what you want to achieve, step by step, in detail. How you see the workflow, what exactly you require.
Thanks and waiting for your reply.