none
Contract Lifecycle Management in SharePoint RRS feed

  • Question

  • We have document library with approval workflow to capture and track contracts. Currently we do not have digital signature so users basically upload a contract, approver(s) review and if okay, prints-signs-scans and upload it back again with same filename and add signed copy as newer version. So we are looking for way to improve this and solution where user can upload as newer version without having to name file same as existing one. Something like adding custom button on ECB menu, which in turn will pick current (item) filename so regardless of filename (signed one) system automatically picks up the name, added file as newer version and maintains other metadata. Any idea or suggestion?

    Thank you in advance.


    MK Sin

    Thursday, September 4, 2014 6:29 PM

Answers

  • Eventually we hope to buy 3rd party e-signature tools but regardless we want make this work for inked as well as without e-signature capturing tool. We are planning to extend OOTB approval WF using SPD.

    Thanks

    KM


    MK Sin

    • Marked as answer by JasonGuo Monday, September 15, 2014 12:15 PM
    Wednesday, September 10, 2014 3:16 AM

All replies

  • Would versioning and a meta data column help you here?  So you would have a history of the file, and then when the final approved contract is uploaded you would just set a column to complete or some other status.

    Just a thought.....

    Brian

     

    Brian Hochgurtel
    My blog

    Tuesday, September 9, 2014 3:21 PM
  • KM,

    A custom workflow (SPD or VS, depends on your comfort) which tracks the approval system and controls the version might be what you looking for. There is a chance to grab eSignature of approver either using 3rd party or again custom.

    So, basically what you should do is try to extend OOB approval WF using SPD or VS. Explore the web for similar document management systems built using SharePoint.

    Hope this helps. 

    Tuesday, September 9, 2014 9:18 PM
  • Yes I plan to use versioning, metadata and workflow (SPD) to complete CLM. Pain point is when there are multiple inked signature required, then approvers needs to print-sign-and-upload it back to library plus approvers must ensure to name the file same as existing version.

    So I am looking for solution where approvers can upload file (in sequential order) without worry of matching filename; something like where they click (some custom ribbon item or ECB menu item) to upload their signed copy back to library by implicitly renaming this file and add it as newer version. With this in mind I think a solution could be creating custom upload form with custom action on ECB menu but wanted to get feedback if there is better and/or easier solution with same effect.


    MK Sin

    Wednesday, September 10, 2014 3:10 AM
  • Eventually we hope to buy 3rd party e-signature tools but regardless we want make this work for inked as well as without e-signature capturing tool. We are planning to extend OOTB approval WF using SPD.

    Thanks

    KM


    MK Sin

    • Marked as answer by JasonGuo Monday, September 15, 2014 12:15 PM
    Wednesday, September 10, 2014 3:16 AM