Currently i am sending out email using MAPIEX but the sender will be referring to mine. I have an exchange account to use for this bot. How can i apply in blue prism? is it possible?
MAPIEx allows you to target actions to specific Outlook Profiles that are installed on the Runtime Resource executing your Process. The overarching idea here is to maintain at least one Outlook profile on each of your Runtime Resources that's tied to the bot's dedicated Exchange account that Blue Prism can leverage to send and receive messages as the dedicated account.
On each of the Runtime Resources that will need access to the bot-dedicated Exchange account, create a new Outlook profile in accordance with the associated Outlook support article "Create an Outlook profile" (support.office.com). Configure that new profile with a unique name and with the credentials of the bot's dedicated Exchange account. When dealing with scaled processes (>1 bot requiring access), you should be naming the Outlook profile the same across them all.
Once the profile's been created on all the Runtime Resources, re-configure your "Send Mail" actions to pass the string name of the new Outlook profile in the "Profile" input field (emphasized below):
Related
I'm providing a service for many different clients.
I'm using the DocuSign APIs.
I'd like to customise the user name and the account name displayed at the top left of the signature ceremony web page (the part surrounded with a red line in the screenshot below)
It looks like it needs a new account each time the account name needs to be changed and a new user each time the user name needs to be changed.
Is it possible to do this without creating new account and new user, and how can I do this via the API?
I hope my question is clear enough.
The sender Account Name/User Name cannot be changed per envelope. Once they are set during account creation they will be applied to all the envelopes sent from the account.
If your integration is supporting multiple clients, then you will probably have to authenticate differently. DocuSign supports various authentication mechanisms. Consider using oAuth or SOBO based on your application needs.
I'm only mildly technical and not the web lead for my company, but I am the membership lead and I'm hoping to use your API for my workflow. This is what I need:
A web form on our website that asks for Name, e-mail, age, and a drop-down box of predetermined locations.
Using the above, I'd like the age to decide whether the requestor receives the Over 18 or Under 18 version of my form. Then I'd like the name to be auto-filled into the correct form. I'd like the form to be then e-mailed to them for a signature, and I'd like the signed, returned form to not only come to my primary e-mail address, but also to use the location to send a carbon copy to their local representative.
Can it be done? Thank you all for your help!
Yes you can use DocuSign to easily achieve the workflow you've stated. There's probably several ways you can implement this, I'll focus on the first that comes to my mind which is using DocuSign Templates.
Using Templates you can upload documents into your DocuSign account at design time, add workflow, tabs, routing, etc, then at run-time your app can reference these templates and match specific recipients to placeholder roles configured in the template.
For example, your flow would be:
Create 2 templates in your DocuSign account, one for 18+ case and one for Under 18 (note: you have unlimited templates in your account).
Add a Carbon Copy recipient as the second recipient for each template, make sure to give a routing order = 2 by setting the signing order.
Once your web form receives all input data from the user (ie Name, email, age, and location) use the Envelopes: create API to create an envelope with the form data populated in various tabs.
By default, once they are done signing the platform will email them a copy of the signed document (you can control this through account settings).
The Carbon Copy recipient will also receive a copy of the signed document once signing is complete, you can store a static email in the template or provide new recipient information at run-time when making the API request.
For more info see the DocuSign Developer Center. I also recommend you have a look at the Tabs section and Templates section for some highly useful information.
We're using the DocuSign API to integrate DocuSign functionality with our application. We are using the 21 CFR Part 11 compliance module, so we aren't able to do embedded signing.
During our process, we're creating a DocuSign account for the user based on the credentials they use to register for our application. However, currently they have to go outside of our system to their email to verify their DocuSign account, then they return to our app.
I'm curious if there's any way to retrieve that Account Activation URL for that specific user, so at least we could save them a trip to their email inbox and just show them the link so they could jump straight from our app to DocuSign to verify their account.
I'm thinking there may be some security holes there, so maybe this isn't even an option. Thank you.
I'm not sure if you can create a unique account activation URL for user (don't think that's possible) but what you CAN do is use a DocuSign Distributor that does not have the verify email option set.
A Distributor is basically a "package" that lets you span new DocuSign accounts that have whatever settings you want set. Within each distributor is an open that lets you skip the email verification part, that way you can create new users and accounts instantly and avoid the context-switch to email you're trying to avoid.
Only official DocuSign Partners have access to distributors (since a business relationship is required with DocuSign to span new accounts) but also for security reasons it's not available to all. You'll need to reach out to your DS Account Manager to have your distributor modified and/or have a new one created.
A 3rd party website is offering our service to their members. When they sign up, members have to agree to our contract. Currently this is handled manually, with envelopes being sent through email. We want to streamline this process allowing members to enter their information into the web site, and then immediately be presented with a contract to review and sign.
The 3rd party web site will collect the member information, then use the REST API to create a draft envelope based on a Template and information the the member enters on the website. The application will then display the contract in the web page so that the user can review and sign it. The document workflow will ensure that signed copies are routed to appropriate parties within our company via email for completion.
We want the 3rd party web site to have access to an account to which we can share templates. We want the 3rd party application to have very limited capabilities trhough the API:
Submit requests using a User ID and Integrator Key that we provide. These credentials need be different from other User Ids and Integrator Keys under our account
Create a draft envelope based on the templates we provide
Post a Recipient View allowing the application to display the document for review and siganture (in an IFrame)
Receive the signing status via the return URL provided in the Recipient View post
Possibly request status for an envelope
The external application should not have access to other templates, documents, or unnecessry API calls.
We want to be able to cancel the application's access at any time.
Question: Permissions and API Limitations
Is the above scenario feasible with respect to establishing limited access to the DocuSign REST API? How would we set this up?
Do account user permissions limit API use, if the API is enabled for the user? I found these settings in the user permissions section of the documentation. I can make guesses as to how to set them, but I need guidance on the actual implications of some settings.
Submit DocuSign API Requests: true
Manage Account: false
Send Envelope: true
Manage Templates: Use
DocuSign Desktop Client: false
Transfer Envelopes to User: false
Allow sender to set email language for recipients: false
I assume "Account-Wide Rights" should be false, but under that option in the documentation, it lists RequestStatus as one of calls covered. Will an application embedding the signing process still have sufficient permissions to complete the tasks listed above if "Account-Wide Rights" is false?
Are there other settings or issues I need to consider?
Firstly, thanks for using DocuSign. The answer to your question is in a few different parts. To clarify, I am answering assuming:
1.) You are a current customer (or about to be one) of DocuSign.
2.) You have a plan that is set up to allow integration (IE you aren't trying to do all of this with a personal plan, or something like that).
There are a couple of terms I will use... Sender and Recipient. In this scenario, the THird Party Website is "the sender" and they are Sending the documents through YOUR DocuSign account, using the API. The people who are signing up for your service are going to be Envelope Recipients.
Just like with the post office, someone has to send, and someone gets the envelope.
So far so good.
So what will happen is that the third party website will write some code that knows how to talk to the DocuSign API, and you will need to know:
-DocuSIgn Account ID (this is your DocuSign account)
-The Integrator Key (this is the key that you will need to certify before going live, which identifies all those API calls as coming from them)
-Credentials to access your account (this can be either the actual creds, or a token, etc).
Now, there are two ways to do it. You can either have the third party website make the and send all of the envelopes as if they all came from a single "user" in DocuSign (likely) or if you know that a particular user should send out things, you can do that too.
I am going to assume that all of the sign up packets will be sent as if they came from something like Signup#company.com.
So you will make sure you have a user in your DocuSIgn account with that Email address and name, and make sure that user has the ability to send via the API (there's a setting in DocuSign admin), and all envelopes will be sent as if that "person" sent them.
You will need the settings for that user (the one that will "send" all the envelopes), set as you showed above. You would need the Account Wide access if you wanted to send "on behalf of" a different user. But you aren't doing that, so you should be cool.
The last thing is that you will need to make sure you have an envelope based plan (as opposed to a seat based plan) because otherwise, that one mega-user will look suspicious (sending hundreds of envelopes in an automated fashion).
I hope this answers the question?
-Dan
I have enterprise account and we are using it to send envelope signing requests via email to our users. Currently it shows "From" in email as "XYZ Ltd via DocuSign". As we have multiple brand profiles, I want this "From" to be displayed as per brand(like "LineOfBusiness1 via DocuSign") - Using same integrator key though. Is it possible to do so? If yes, how?
We resolved it as below.
We have created 4 different users each for 1 brand.
Now while sending request to docusign api for creating envelope- we are using brand specific email in authentication.
Name corresponding to this email will come after "via" in email.
This solution allows us to use sme integration key - and we can easily change/add/delete brand by adding/modifying users.