Adobe Livecycle Server - Sharepoint integration

Please read our functional requirements below on how we plan to integrate LCES with Sharepoint. LiveCycle will be treated as a ‘black box’ to provide SOAP web services to SharePoint. The LiveCycle processes below will read the input document(s) from SharePoint, and the resultant PDFs will be written to SharePoint. The four LiveCycle processes will be: 1) Reader Extend a PDF The input PDF will be read from SharePoint, reader extended and written back to SharePoint. Input: a. SharePoint URL of input PDF. b. SharePoint URL of result PDF to be created. c. Metadata to be stored in the PDF. (This should be changed in the requirements document because it only makes sense to store this information with and in the coversheet which adds the buttons to submit it back to SharePoint – this metadata will contain review ID, submit URL etc.) Output: a. Error status. 2) Add a coversheet to a PDF This is for multiple internal reviewers to read and approve/reject the document. They will also type comments into a field, and add PDF mark-up comments. The input vendor PDF document will have a static AcroForm page (‘cover sheet’) inserted as the first page for the internal reviewers, and will contain: a. A multi-line text box for a top level comment/reason for approval or rejection. b. A combo-box: i. Approved / reviewed ii. Approved / reviewed as noted iii. Not approved / not accepted c. Buttons to submit the entire form back to the SharePoint server via a SOAP web service: i. Save document back to SharePoint so that they can re-open and complete the review ii. Submit document to complete the review for that reviewer Both of these buttons should be disabled as soon as the form has been successfully submitted. d. Reader Extend for commenting, saving offline, form filling and submit. The resulting PDF document will be written back to SharePoint. Input: a. SharePoint URL to retrieve Vendor PDF. b. Metadata for SOAP web service call (hidden fields in the AcroForm). c. SharePoint URL to store the result PDF. Output: a. Error status 3) Merge comments and mark-ups This is for the lead engineer to prepare the comments in the PDF so that it can be sent to the vendor. Construct a PDF for the lead engineer with a static AcroForm page (‘cover sheet’) inserted as the first page, and the comments field comments from all reviewers in the comments field. The comments from each reviewer need to be separated with text that can be easily removed with a search/replace when anonymising the document in (4). PDF markup comments from all reviewers will be merged from multiple PDF documents and applied to the document as well. The resulting PDF document will be written back to SharePoint. Input: a. SharePoint URL for the base Vendor PDF. b. List of SharePoint URLs for each of the PDFs contributing comments. c. SharePoint URL for the result PDF to be created. d. Metadata for SOAP web service call (hidden fields in the AcroForm). Output: a. Error status 4) Anonymise the PDF (See 3.4 in attached document) Take a PDF from the lead engineer and prepare it for delivery to vendor. This includes ‘anonymising’ (Names removed) comments from all reviewers and setting ‘read only’ permissions, which includes not being able to edit, add or remove comments. Reviewer names and other marks will be removed from the comments field in the coversheet. The resulting PDF document will be written back to SharePoint. Input: a. SharePoint URL for the lead engineer merged and edited PDF. b. SharePoint URL for the result PDF to be created. c. (Metadata to identify the document when sent to vendor)? Required? Output: a. Error status Notes: 1) The coversheet page will need to be a static, AcroForm PDF page to enable the comments to be included in the PDF. Requirements 1) The PDF comments should not be editable by the vendor, but they should be readable. 2) The vendor should not be able to see the name of the reviewers, just the comments that have been selected by the lead engineer.