sending html content in email body(emailBlurb) docusign api - docusignapi

I am trying to send html content in my emailBlurb for sending email for document signature by using the following code portion :
DocumentSignatureRequest documentSignRequest = new documentSignatureRequest();
String blurb = "Testing html email content : <b>Bold content</b>";
documentSignRequest.setEmailBlurb(blurb);
But the emails I receive from this contain the whole string, instead of using the with the <b> instead of bold text. So, I looked at the docs provided by docusign and it indicated for looking at the 'email resource file' in the docusign account. In the file i found the portion :
<td class="MainStyle" colspan="2">
<p>[[EmailBlurb]]</p>
<p>[[RecipientNote]]</p>
</td>
I am guessing the 'emailBlurb' I am setting is being used simply as a string and thus the html tags are just being displayed as is.
So my question, what are my options with finding a way around this. I know an option is to edit the resource file, but are there any other better options. For instance, any settings or tags in the resource file around the [[EmailBlurb]] or if it can be done from my code? Please help.

It's possible to insert raw html into the notification emails however this is not a self-service option. You need to reach out to your DocuSign Account Manager or their Support to have the option enabled in your account.

Related

Show email in web application from gmail api

Developing an application which will show mails from Gmail.
Fetched messages from Gmail api with the help of following links
https://developers.google.com/gmail/api/reference/rest/v1/users.messages/list
https://developers.google.com/gmail/api/reference/rest/v1/users.messages/get
Got mail body in base64 encoding. Decoded the mail body and got HTML.
can you please help to show this HTML in div and not get affected by previous css.
Tried css property from https://css-tricks.com/almanac/properties/a/all/
all: unset;
But it didn't work.
When you decode the mail body, it returns a string. You need to convert this string to HTML. There are various npm packages available for the same. Try node-html-parser once, it should solve your problems.

How to sign an XML document in a specific Tag with DocuSign SAPI Local

The repository I'm using: Sign-XML. In the moment I can only sign a XML document in the most external Tag. I need to know how to sign a XML file in a specific Tag. You can see an example bellow:
<Tag1>
<Tag2>
<Signature>...</Signature>
</Tag2>
</Tag1>
As you cannot create an empty signature field in XML you need to use the SAPISignatureFieldCreateSign function for creating and signing the XML file.
I'm not sure you can sign inside a specific tag,SAPI Local supports attaching a digital signature to XML.

How to fetch a specific inline image using OWA REST API?

I'm developing OWA add-in using OWA REST API
When fetching the message item, I can see in the body if there's an inline image added which is looks like
<p style="margin-top:0; margin-bottom:0">
<img class="EmojiInsert" src="cid:773570bf-3178-41a4-97ac-4e3eddef859f" style="">
<br>
</p>
in the src I can see the contentId of the attachment but the resource reference did not says if this property is searchable or filterable, and I cant $select it in the odata query params, therefore I cant get that attachment!
the alternative way was to fetch the list of the attachments by doing:
https://outlook.office.com/api/v2.0/me/messages/{id}/attachments
but that will:
1- fetch all attachments with their contentBytes which is too expensive!
2- if the admin increase the minimum upload to be more than 35MB I might got error with that request i single attachment >35MB, see this question that no one answer it yet
3- I alway got some attachments that I did not upload, sometime from outlook it self (VERY WIERD) other time if I upload an attachment(s) and remove it I still get it when fetching the attachments, so some time I have for example 3 attachments but I got 12!!
Is there a way to know the inline image attachment id? and then get that attachment?

DocuSign: Senders Complete-email always in english when using custom email-resource-file

I have a question/bug according docusign.
When I use a custom email resource file, the completed-email to the sender is in english (instead of german as defined in the senders administration). Other emails to the sender are still in german (e.g. Signer viewed envelope etc...)
When I use a brand without resource file, the completed-email is in german as expected.
Does anyone has the same problem or a solution? Is this a known bug?
Please update Brand -> Email Resource File, and update the delta change to the node (<data name="SenderEnvelopeComplete_HtmlBody">) which you are interested and upload just the delta changed xml.
If you want to customize the resource file text for German (de), you would set up the resource file as follows:
<language twoletterisoname=”de”>
[specific settings for German]
</language>
Please find the below link for guide to change email resource file
https://www.docusign.com/supportdocs/pdf/docusign-email-resource-file(v1.1).pdf

Which AMP extensions can fetch a response from an endpoint?

What AMP extensions can be used to get a response from the server in the form of variable that can be used later, such as in a template or as a parameter to an attribute?
amp-access
The authorization endpoint of amp-access can return "a free-form JSON object":
Here’s a small list of possible ideas for properties that can be returned from the Authorization endpoint:
Metering info: maximum allowed number of views and current number of views.
Whether the Reader is logged in or a subscriber.
A more detailed type of the subscription: basic, premium
Geo: country, region, custom publication region
amp-form
amp-form "allows publishers to render the responses using Extended Templates". The response is expected to be a valid JSON Object. Try the "Hiding input fields after success" demo in the amp-form sample to see it in action.
amp-list
amp-list fetches "content dynamically from a CORS JSON endpoint and renders it using a supplied template". The response must be a JSON object that contains an array property "items".
In addition to {{variable}} substitutions in Mustache templates, you can also use AUTHDATA(variable) elsewhere.
amp-live-list (not quite)
amp-live-list is a "wrapper and minimal UI for content that updates live in the client instance as new content is available in the source document". The page will re-fetch itself, giving the server a change to send new content. If new content is found, AMP will populate a <div items> element with the new (HTML) items. You can't use that as a variable.
It's name doesn't really suggest it, but I think you want AMP-list
https://github.com/ampproject/amphtml/blob/master/extensions/amp-list/amp-list.md
Fetches content dynamically from a CORS JSON endpoint and renders it using a supplied template.

Resources