SharePoint 2013: Saving attachments to DMS - sharepoint

We intend to store attachments for a list item on an external Document Management System (DMS). A SOAP web service exists for interacting with the DMS and we've received a WSDL for it.
How can I achieve the scenario where SharePoint is able to talk to the web service and send attachments to store them in the DMS automatically?
Will SharePoint be able to handle this itself or will it involve writing a client in the middle, and if yes, how will the pieces fit in?

Related

Send notification from Sharepoint and Power Automate

I have different content on Sharepoint online and whenever we create or modify any records then send notification to the PHP/Apache server.
I Created one Power Automated notification, but its sending on mobile, need to send to server to server.
Also need to check the Sharepoint REST API.
Create API on the server where you want notification from Sharepoint. Then open the Power Automate and create the flow, then
Select the trigger "When an Item is created or modified".
In next step search for HTTP and select it.
Fill the necessary parameters like "Method, URI, Headers, Body" etc.
Then save the flow and test the flow.

DocuSign Bulk Send w/ CSV User Portal

The current goal is to be able to send multiple files to multiple recipients through the user portal on our website. We want to make this process as efficient as possible because we will have lots of files to sign. Lastly, I would need a way to track and save all the users.
From what I know about docusign, I am able to send a file to multiple recipients in bulk using bulk send using just the website and not having to use the API at all. Is it possible to send multiple files to multiple recipients through the same CSV? Or would it be better to just send each file separately to multiple clients and do that for each file? Also, I'm wondering if it's possible to do that in the API as well. Previously, I achieved sorting clients ID & envelope ID using the docusign api with PHP and connected it to a database. Let me know which method seems optimal for my solution.
Steven, you can use the API to use Bulk Send.
In fact, with the DocuSign eSignature API v2.1 this functionality is much improved and allows you to do all of the above.
See here for more details: https://www.docusign.com/blog/dsdev-deep-dive-discussions-bulk-send-with-esignature-api-v2-1/

Integrating Docusign in our webapp

I am new to Docusign and we have a requirement to integrate Docusign in our web app. I have gone through all the links for integrating docusign into a web app using REST Api calls. After thorough read and watching youtube videos, I came to know that we can integrate docusign in our web app through REST API calls but for the same additionally we need to develop our own UI to upload documents and send it to the recipient. But basically we are looking something where we can be reidrected to docusign from our webapp to perform all the operations of sending document for signing and once document is sent then I will be redirected back to our web app.
Kindly help with the above query and let me know if my understanding is correct for integration of docusign and for the same developing our own UI in our web app. Also please let me know if there is any alternative to fullfill the requirement of directly accessing docusign from our web app and performing all required operations of sending a document to recipient.
Thanks in advance!
So you want a button on your web app that says "Sign with DocuSign" and then what?
Most customers who want to send from their web app already have the documents controlled by their web app.
They:
authenticate the user with DocuSign (OAuth Authorization Code Grant)
Upload the document to DocuSign from their app.
Add tabs (signing fields) to the documents programmatically. (This is not hard and it saves the sender a lot of work.)
Upload the recipients (signers, copy-only recipients, etc)
And then tell DocuSign to send the envelope (the transaction).
Applications can also monitor the progress of the envelope through the signing process and programatically act on the signed documents.
The above is not hard to do and provides a good user experience.
You can also redirect the user of your application to DocuSign to accomplish any/all of the above manually. But the more the user does manually, the less convenient the integration will be for them.
If you want the manual experience, check out the EnvelopeViews::createSender method.

Allowing users to upload a list of supporting documents using Docusign

Our company wants to use DocuSign API to allow its users to upload a set of documents. Once a user goes through our online application, our application will call the Docusign API in the end and display the list of documents that they need to upload. Once the user is done uploading all the documents, then the admin should receive an email about the completion.
Can anyone direct me in the right direction..where I can find documentation regarding it? Most of the documentation talks about ESignatures of already created templates.
Thanks.

WSS 3.0: Email notification/alert on download

Is there a way in WSS 3.0 to send an email notification when a list attachment is downloaded or when a document in a document library is downloaded?
The event listeners you can attach to list items in WSS only apply to add, update and delete events.
You'd have to map an HTTPHandler to the URL of the list/library storing the content.
This handler would be responsible for sending notifications when it's detected that a client is making a request for an attachment or document.
Another possibility is to leverage SharePoint Auditing. SharePoint auditing can log whenever someone accesses an item. If you had a process monitoring and querying the SharePoint Audit Log you could fire off your alerts.

Resources