SharePoint 2010 Collect Signatures workflow - no digital signatures?

Hello, I configured a "Collect Signatures" workflow for the content type "Document", then uploaded a MS Word 2010 (.docx) document as content type "Document". This Word document as 2 empty Signature Line in it.
I then start the workflow, basically 2-stage with 2 person from my Active Directory. However, what I found is that when I go to my workflow task and click on the "This document requires your signature" link, it pops up a "Workflow Task" box in the
browser. There is a "Sign" button which I can click to sign but it does not sign on the signature lines inside my Word document.
What am I doing wrong here? Or does SharePoint 2010 Collect Signatures workflow no longer work with digital sigantures? Thanks.

Hello ,
We have chceked by setting up a repro at our end and its not possible to complete the workflow without opening the document . Also below are some additional findings that I have and would like to share :-
1) In Office 2007 (Word and Excel) you can click on the office button from the respective application while you have the concerned document open in it. This triggers the collect digital signature workflow and the users signs
it immediately as he can see the popup on the screen. Still he has to go to the task list to complete the task which I would say is a manual process following the workflow task is 100% completed.
2) In SPS2010 with Office 2010 we do not have an option to trigger the workflows from within the Office document. Instead you directly go to task list to open the task and click on sign button to complete the task. Here you
still need to open the document again and digitally sign it. The difference is workflow here is not triggered in Office document. Even here it is a kind of manual process except that you don’t see a popup to sign document immediately from Office document
due to the fact that workflow is triggered from SharePoint task list.
Thanks,
Manas
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread."

Similar Messages

How to REpublish Custom Task Forms (InfoPath) to SharePoint 2010 State Machine Workflows

I am new to SharePoint. Sorry if answer to my question is obvious.
I've create Custom Task Form in InfoPath and publish it (File/Publish/Network Location [Form Template Path and filename='MYPROJECT/Forms/ApprovalForm.xsn'; Form template name='ApprovalForm'], in the next window I've cleared Public URL according to the articlehttp://www.codeproject.com/Articles/195348/SharePoint-2010-State-Machine-Workflows-with-Custo).
After it I've added module Forms, and added ApprovalForm.xsn from the existing items.
My xml files: Elements.xml
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Workflow
Name="Order New Server"
Description="My SharePoint Workflow"
Id="482cbc86-b717-4981-a49a-3cf4c89e9399"
CodeBesideClass="Myproj.OrderNewServer.OrderNewServer"
CodeBesideAssembly="$assemblyname$"
TaskListContentTypeId="0x01080100C9C9515DE4E24001905074F980F93160">
<Categories/>
<AssociationData><Data></Data></AssociationData>
<MetaData>
<AssociationCategories>List</AssociationCategories>
<Task2_FormURN>urn:schemas-microsoft-com:office:infopath:ApprovalForm:-myXSD-2012-03-09T14-11-55</Task2_FormURN>
<StatusPageUrl>_layouts/WrkStat.aspx</StatusPageUrl>
</MetaData>
</Workflow>
</Elements>
Feature.Template.xml:
<?xml version="1.0" encoding="utf-8" ?>
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" ReceiverAssembly="Microsoft.Office.Workflow.Feature, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Receiverlass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver">
<Properties>
<Property Key="GloballyAvailable" Value="true" />
<Property Key="RegisterForms" Value="Forms\*.xsn"/>
</Properties>
</Feature>
My form work fine, but when I make changes and republish it, it doesn't update (I see old form). What I tryed:
IISReset
Clear all cookies and cache in IE
Retract solution, restart VS2010, reboot computer.
Change assembly number, guid.
I have no ideas, what can I try for republish my form with changes.
Thank you in advance for any suggestions.
PS: sorry for my writing. English is not my native language.
PPS: when I save new Form to new location and add it to the project, it works.

I've found how can I republish changes. But it seems more like crutch than solution, but it works:
After republishing InfoPath form, I delete file from project (DEL on ApprovalForm.xsn in Solution explorer) and after it add it again. (Add/Existing Item). And then redeploy! Hurray!
Is there any way to redeploy a Task Form directly on the server without importing it in Visual Studio again? I am using some data connections in my task form which are different for different environments (staging, dev. etc.). Seems like I've to create a separate
Workflow WSP file for each envrionment. Any comments?

DMS & Workflow - Handling Digital Signatures

Hello,
I have set up a DMS status network, and I'm controlling this network using workflow.
My workflow listens to "DRAW" for changes, and when a particular status is seen,
workflow starts.
This workflow sends out work items to several users, prompting them to review.
At this point, users can go into the DIR from their Inbox, and either select Approve or Reject Status.
Both Approve and Reject status are set up to require a Digital Signature. Workflow controls moving the status back to a "ready" state for the next reviewer. It also keeps track of the number of reviewers, in order to know when all reviews are done.
When everyone behaves in timely manner, this works great. Workflow has no issue with setting DMS statuses - in most cases.
However, I also have deadline monitoring set up on my workflow. After 3 days pass with no action, I want to "auto-reject". System id WF-BATCH is what I use to set statuses through workflow, and this works fine in most cases. However since the status "Approve" and "Reject" are set to require digital signatures, this system initiated status change FAILS. The system does not provide a digital signature for itself.
My question is - is this possible through configuration - to set it up in some way that a system ID can promote to a status and either pass a password or simply not require a digital signature?
My network is kind of stuck at this point because one of the 2 statuses MUST be selected for it to proceed.
Edited by: Bill Bessette on Jul 24, 2008 9:40 PM

Hello Niranjan,
That's an interesting suggestion... I'll investigate. Any additional detail you can provide on how to implement this User/Pwd hard coding in WF would be appreciated.
In the meantime, here is some additional info.
Imagine a status network as follows:
Draft
Initiate Workflow
In Review - Reject/Approve
Active
Document starts in draft. The author selects a status of (Initiate Workflow) at which point the workflow starts.
Workflow moves the status from (Initiate Workflow) to (In Review)
and puts a work item in the reviewers mailbox. Reviewers can change the status to (Reject) or (Approve) and each requires a digital signature. After each reject/approve, Workflow moves the status back to (In Review) so that the next person may act. When everyone has reviewed and approved, workflow moves the status to (Active). If anyone has rejected, workflow moves the status back to (Draft.)
This is a simplification, but that's the scenario. WF-BATCH is our workflow ID that has SAP-ALL authorization. Problem occurs when deadline monitoring is in effect. If a reviewer doesn't act within the designated deadline, the monitor fires and the work item is flagged as obsolete. Due to the status network, the only valid path is to either move to (Approve) or (Reject). But since both of those statuses have been set up to require digital signature, they fail. We end up stuck in (In Review) with no way out.
If hard coding the userid WF-BATCH and the password in some table will solve this problem, then we'd be thrilled.
Bill
Edited by: Bill Bessette on Jul 25, 2008 6:00 PM

Removing signatures in a digital signature field

Hi all, I have a question relating to the topic above that i hope
you guys can help me with;
1) Is it possible to remove digital signatures from form? For instance
if you have a form going thru several approval steps that requires
signatures, and then one step happened to reject, it would be nice to
remove the previous signatures so that they could be re-signed.
2) And finally is there a simpler way to combine digital signatures
and rights management then what was listed in the pdf provided by
Duane (second post from the bottom of the thread)? When creating a policy there is
a checkbox for "Filling in form fields and signing". Is this forsomething else?
Thanks!
Billy

Hi all, came accross a few other problems and hopefully someone can
help me out,
I've managed to place digital signatures on a form and I used a custom renderer to apply a policy for rights management. I used a Document
Form type variable in the process and specified that the form should only be rendered once. Now at some point in my process I wanted to
remove a signature so I tried to use the Clear signature field service. When i run it however i get a stall and an error in my logs
saying "The input PDF is encrypted using APS and could not be opened, hence the operation clearSignatureField can not be performed on Signature Field ConsultantSig. (in the operation : clearSignatureField)"
So figure, ah well, thats cool, i'll just remove the policy as I figured thats what was encrypting it. So i threw in a Remove Policy service and then i get another error in my logs saying that
Cannot coerce object:
<document state="passive" senderVersion="3" persistent="true"
senderPersistent="false" passivated="true" senderPassivated="true"
deserialized="true" senderHostId="127.0.0.1/10.37.129.2/192.168.0.143"
callbackId="0" senderCallbackId="54" callbackRef="IOR:
000000000000002849444C3A636F6D2F61646F62652F6964702F49446F63756D656E7443616C6C6261636B3A3 12E30000000000200000000000000D8000102000000000E3139322E3136382E302E313433000DC8000000114A4 26F73732F00160C034D230F2B012B02000000000000050000000000000008000000004A4143000000000100000 01C000000000001000100000001050100010001010900000001050100010000002100000050000000000000000 10000000000000024000000200000007E00000000000000010000000E3139322E3136382E302E313433000DC90 00000000000000000000000000000000000000000000000000000000000002000000004000000000000001F000 0000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000 003"
isLocalizable="true" isTransactionBound="false"
defaultDisposalTimeout="600" disposalTimeout="600"
maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="0"
contentType="null" length="85284"><cacheId/><localBackendId/
><globalBackendId><DocumentFileID fileName="C:\Adobe\LiveCycle8.2\jboss
\server\all\svcnative\DocumentStorage
\docm1247766543265\66d5bdad216c55badc57fc5b86f44086"/><globalBackendId/
><senderLocalBackendId/><senderGlobalBackendId/><inline/
><senderPullServantJndiName>adobe/idp/DocumentPullServant/
adobejb_server1</senderPullServantJndiName><attributes/></document> of
type: com.adobe.idp.Document to type: class
com.adobe.idp.taskmanager.form.impl.binarycontent.BinaryContentFormInstance
ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException:
Cannot coerce object: <document state="passive" senderVersion="3"
persistent="true" senderPersistent="false" passivated="true"
senderPassivated="true" deserialized="true"
senderHostId="127.0.0.1/10.37.129.2/192.168.0.143" callbackId="0"
senderCallbackId="54" callbackRef="IOR:
000000000000002849444C3A636F6D2F61646F62652F6964702F49446F63756D656E7443616C6C6261636B3A3 12E30000000000200000000000000D8000102000000000E3139322E3136382E302E313433000DC8000000114A4 26F73732F00160C034D230F2B012B02000000000000050000000000000008000000004A4143000000000100000 01C000000000001000100000001050100010001010900000001050100010000002100000050000000000000000 10000000000000024000000200000007E00000000000000010000000E3139322E3136382E302E313433000DC90 00000000000000000000000000000000000000000000000000000000000002000000004000000000000001F000 0000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000 003"
isLocalizable="true" isTransactionBound="false"
defaultDisposalTimeout="600" disposalTimeout="600"
maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="0"
contentType="null" length="85284"><cacheId/><localBackendId/
><globalBackendId><DocumentFileID fileName="C:\Adobe\LiveCycle8.2\jboss
\server\all\svcnative\DocumentStorage
\docm1247766543265\66d5bdad216c55badc57fc5b86f44086"/><globalBackendId/
><senderLocalBackendId/><senderGlobalBackendId/><inline/
><senderPullServantJndiName>adobe/idp/DocumentPullServant/
adobejb_server1</senderPullServantJndiName><attributes/></document>
of type: com.adobe.idp.Document to type: class com.adobe.idp.taskmanager.form.impl.binarycontent.BinaryContentFormInstance
Oh great, a conversion problem when i try to remove the policy! Incidently i get this same conversion problem when i try to remove a signature using the Clear Signature on a form that has NOT had any policy placed on it at all.
So basically, to sum up these are the main issues
1) Can digital signatures be removed from a form that has a policy placed on it, or do i have to remove the policy first?
2) Why am i getting these coercion errors? As i understood it using a Document Form variable is the correct way to go. What should i do to resolve this?
So can anyone shed a little light on this?
Thanks
Billy

Trigger a Signature Date when Digital Signature Field is Signed

I'm looking for a way to have a date field populate when a digital signature field is signed on my Adobe Designer Form. The signature technology I'm using does not work seamlessly with Adobe LiveCycle Designer and is unable to add the date when the document is signed. So I was thinking I could call a function to add the date to the date field when the signature field is signed. I just dont know how to do it.
Please help!
Thanks!

Here is some code that will allow you to check the signature field:
// check to see if Claimant signature field is signed.
var oSOM = claimsign.somExpression; // Returns the full SOM expression i.e. xfa[0].form[0].form1[0]...
var truncSOM = oSOM.substring(15); // Truncating 'xfa[0].form[0]' from SOM to get acroforms name of the field.
var oState = event.target.getField(truncSOM).signatureValidate(); // Get the current field's signed state
In this case the signature field is called claimsign. After running this code the variable oState will conatin a value ....if it is 0 then the field is not signed. So you can add code like this:
if (oState == 0 ) {
     // signature field is not signed
     app.alert("You must sign the form before submitting")
} else {
     //The signature field is signed
     go through your submission process code
Hope that helps
Paul

Digital Signature and SharePoint 2013

Dear Expert,
My company has a plan to do digital signature and sharepoint 2013. Now, we focus for internal use that I know use AD CS. and in near future we use for external use. We plan to buy 3rd party certificate.
My question
1. How to implement this solution? Please suggest
2. If I implemented AD CS, can we use public certificate in near future.
3. Can we use public certificate with SharePoint 2013?
Thank you

Hi,
Based on your description, my understanding is that you want to use Digital Signature in SharePoint Server 2013.
You can use digital signatures in forms ,then use these forms in you SharePoint site.
In InfoPath form ,you can change the form to allow signature here: File>Info>Advanced form options >Digital Signatures .You can choose to sign the whole form or a field .
https://social.technet.microsoft.com/Forums/en-US/0ed54d57-d67d-41cd-bd1b-9e5a4be10d0c/use-of-digital-signature-in-sharepoint-2010?forum=sharepointcustomizationprevious
besides, here is a similar post, you can take a look at:
http://sharepoint.stackexchange.com/questions/78058/custom-digital-signatures-or-hash-on-list-items
For more information about implemented AD CS, refer to the following link:
http://technet.microsoft.com/en-us/library/hh831574.aspx
Best Regards,
Lisa Chen
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Lisa Chen
TechNet Community Support

Digital signatures and wet ink signatures

HI all,
I am in the process of converting our paper checklists into fillable pdf forms. Everything is working well, but Im trying to get my head around digital signatures.
Ideally I just want to click the signature part, choose a user from a list, enter the password and the 'wet ink' signature that is scanned in gets added to the form.
So on my laptop I setup a new appearance for my signature, scanned my signature and added it to my digital signature. Perfect.
Problem is, I want to be able to use this on other computers. I copied the digital signature .pfx file and imported it on that new computer, which worked, but it drops the 'wet ink' signature and appearance.
It also appears that anyone can create a digital ID on my laptop and choose my wet ink signature appearance, and sign the document which makes it appear as if I have signed it. I was hoping the wet ink signature was locked with the digital signature but it appears this isnt the case.
Im trying to find the best way to store our signatures (we are all on a network), so that any user can use any computer and ideally lock the wet ink signature to the digital signature.
Many thanks
Chris

It doesn't work for everyone, but if you are considering moving to the world of digital signatures, it's best to forget the signature appearance ("wet"). This is just a distraction to the actual signature, and it encourages a deeply flawed workflow: one where people look at the picture on the page rather than learning about digital signatures and how to verify them. Since digital signatures are (if done properly) unfakeable and (in some places) legally recognised, it is best to completely change workflow, rather than trying to give the illusion it is just an electronic version of a paper workflow.

Digital Signature prevents submit via email and print

A form works perfectly well until I insert a digital signature into a digital signature box. So if the digital signature box is empty the buttons still work but sign the wrecked thing and nothing works anymore. I have created new signatures but nothing seems to work. Can you shed any light on this?

The problem is that the "Lock Fields After Signing" property is enabled (see attached screen shot). Buttons are considered fields, therefore when the signature is applied, the buttons are locked and can no longer be clicked. To fix this you can disable the property, or better yet create a field collection and select the specific fields that you want to lock if a signature is applied.
Regards
Steve

Making Multiple Digital Signatures Read-only in Form (Acrobat 9)

I have created a form which includes two (2) digital signature fields. What needs to occur with the form is Person1 fills the form and then digitally signs it thereby making the form fields read-only . Person2 then digitally signs the form which should make Person1's digital signature read-only.
Here's what I've done:
1) For the Person1 digital signature field, in Digital Signature Properties, under the Signed tab, I have selected Mark as read-only <all fields except these> and selected the Person2 digital signature field.
2) For the Person2 digital signature field, in Digital Signature Properties, under the Signed tab, I have selected Mark as read-only <all fields> since once Person2 signs the form I do not want Person1 to be able to clear the digital signature and make changes to the form.
Here's what actually occurs:
Step 1 above works fine. Once the signature is applied all the form fields are read-only except for the Person2 digital signature field.
The problem is that after Person2 digitally signs the form, even though I selected all fields as read-only, Person1 can 'clear' their signature which leaves all the form fields available for editing and leaves Person2's digital signature still on the form.
I honestly don't care about 'validating' signatures on this form since it's going to be printed but I cannot allow Person2's signature to remain on the form and allow Person1 to edit the form.
--Mike.

Hi!
I have the same problem. Have not been able to figure it out, although tried everything.
Hope somebody can help
- MackeMan

Digital Signature Text is too big, how to make it take up less room?

I added a digital signature to a PDF and part of it is a real handwritten signature. The digital signature text was also added but it is taking up too much room on the signature line. I would like to make the real signature large and the text part of the digital signature smaller. I cannot seem to find oout how to make this happen. Is it possible? If so, can someone please supply the steps?

hi Axl....
I've got tiger in ok, running fine - bought family pack and have done 3 installs without problem, so that's the good news ....
I did a major reshuffle and toss-out of files before I installed - bought 80gb mobile external hard drive - and did install with 5+gb free, so after it had about 3gb free, then all of a sudden I went down to less than 1gb
I've been in a hunt for more files to throw out (a nice find were the old ipod updaters that were eating 500mb) ....
If I want to throw out most of the language files (for instance) ... where are they ? (I did search for danois and found nothing, so .... buried ?)
any other suggestions for things to throw away .... I've pretty much eliminated 90% of all things classic, for instance ....
and - do you have ideas for why space seems to disappear so fast .... I'm not doing anything special, but wham, 2gb flies away to ???
thanks

How to create a digital signature in adobe reader

how to create a digital signature in adobe reader?

Adobe Reader Touch (Windows Store app with "modern" UI) does not support any types of signatures yet.
Digital Signatures with certificates
Electronic Signatures (that are legally enforceable)
Signature annotations (hand-writing annotations which may not be secure and legally enforceable)
Adobe Reader XI (traditional desktop app with classic UI) supports #1 and #3.
Adobe EchoSign supports #2.
Adobe Reader for iOS/Android supports #3.

Digital signatures with different versions of Reader

I have created a form which requires a digital signature for approval. Typically, an employee will complete the form in Reader and forward it to a supervisor for approval. The supervisor needs to sign it digitally and forward it to me.
The issue we are having is with those employees who are completing the form in Reader and the supervisor (or someone thereafter) has a more updated version of Reader and cannot sign the document. What can we do to stop this from happening? There is no practical way to keep everyone on the same version of Reader. We will have many more forms which require a signature, and we need this issue resolved. (I am using Adobe Acrobat 9 Pro to create the forms.)
Also, is there a way to verify the digital signature without using a third-party source? At this point, we know anyone can create a digital signature using someone's hand-written signature they found on another paper and we would like to prevent this from happening. We need to validate the person who used the digital signature is really that person.
Any help is appreciated! Thank you!

If you are creating your forms in Acrobat 9 Pro. and then Reader-enabling them for digital signatures, then recipients of the form will need to use at least version 8 of the Adobe Reader. Also, you'll need to do a few things during the authoring stage of your form, if your form changes by role (i.e., additional data is entered, annotations, or multiple signatures). Mainly you'll need to use a certification sig. for the first signature and set permitted changes after certifying.
You can find a lot more detail on best practices on developing forms for multiple signatures in the Digital Signature User Guide at:
http://www.adobe.com/devnet/acrobat/pdfs/acrobat_digsig_userguide_90.pdf
The guide also explains how to validate documents (authenticity validation and document integrity validation).

Acrobat pro dc windows 8.1 only digital signatures allowed when creating forms

When creating fill in forms, my only option for inserting a signature is a digital signature and then when it comes time to complete the form, it wants a digital signature and does not allow you to just insert one on the tablet you are using to complete the form,

Click to Run according to Microsoft:
https://technet.microsoft.com/en-us/library/jj219427.aspx
"Click-to-Run is a Microsoft streaming and virtualization technology that reduces the time that is required to install Office and helps you run multiple versions of Office on the same computer. The streaming technology enables you to download and begin to use an Office product before the whole product is installed on your computer. The virtualization technology provides an isolated environment for Office to run on your computer. This isolated environment allows you to run the latest version of Office side-by-side with an earlier version of Office that is already installed on your computer."

Digital Signatures in BIP

The limitations mentioned below come from the BIP Administrator and Developers Guide 10.1.3.4, I thought these were removed in 11g but I see the same limitations in the 11g doc. Can anyone confirm if these limitations still apply for 11g and when will they be removed?
Limitations
Use of digital signatures with Oracle BI Publisher output documents has the following limitations:
•     Only a single digital ID can be registered with BI Publisher. Future releases will support multiple digital IDs.
•     Only reports submitted through BI Publisher's Schedule Report interface can include the digital signature.
•     The digital signature is enabled at the report level; therefore, multiple templates assigned to the same report share the digital signature properties.

Regarding #1, the short answer is no. Every time the file is digitally signed it necessitates it being saved. That's what allow "View Signed Version" and signature roll back to work.
As for # 2, it depends on the version of Acrobat. Versions 6 and 7 allowed anyone to remove a signature as long as it wasn't a certifying signature. In the case of the certifying signature on the signer could remove. Beginning with version 8 you can only clear if you have access to the digital ID that was used to create the signature.
Steve

Message level security: difference digital signature and certificate

Hi everybody,
could anybody please explain the difference between <b>digital signature</b> and <b>certificate</b>?
Thans
Regards Mario

Mario,
A digital signature is an electronic signature that can be used to authenticate the identity of the sender of a message or the signer of a document, and possibly to ensure that the original content of the message or document that has been sent is unchanged. Digital signatures are easily transportable, cannot be imitated by someone else, and can be automatically time-stamped. The ability to ensure that the original signed message arrived means that the sender cannot easily repudiate it later.
A digital signature can be used with any kind of message, whether it is encrypted or not, simply so that the receiver can be sure of the sender's identity and that the message arrived intact. A digital certificate contains the digital signature of the certificate-issuing authority so that anyone can verify that the certificate is real.
where as
A digital certificate is an electronic "credit card" that establishes your credentials when doing business or other transactions on the Web. It is issued by a certification authority (CA). It contains your name, a serial number, expiration dates, a copy of the certificate holder's public key (used for encrypting messages and digital signatures), and the digital signature of the certificate-issuing authority so that a recipient can verify that the certificate is real. Some digital certificates conform to a standard, X.509. Digital certificates can be kept in registries so that authenticating users can look up other users' public keys.
hope it helps u.
--Archana

SharePoint 2010 Collect Signatures workflow - no digital signatures?

Similar Messages

Maybe you are looking for