I've created an email signature which is built using tables as per advised, and looks great when opened in a browser.
However when I paste the code into the email signature section, it stays as just that, code.
I can create a signature in Word, and when pasted in to Gmail, this works, but this does not give me the control over the styling that I am after.
What am I missing here as I believe I should be able to do this?
Thanks
Related
We have a requirement where we want to send an invoice that hosts a link that would direct a customer to pay the invoice being emailed to them via standard Acumatica Email delivery mechanism. When previewing the invoice we can click on the link without issue. However, the invoice that gets sent does not have a clickable link.
I Found this article on the subject which describes the same use case we are looking to achieve.
https://feedback.acumatica.com/ideas/ACU-I-1344
The discussion commentary points out that 2018 R2 has resolved this issue and I have indeed confirmed it works as expected on that release. We need to figure out what to do with the R1 version. Is there anything that can be done to get this link to work on 2018R1 and prior?
I fear this may not be plausible and if so I may end up looking into getting the link into the email template itself.
Acumatica versions prior to 2018R2 will not render the control as a PDF link object, it will render it as a standard text box.
As a workaround, you can exploit a behavior that most consumer friendly PDF client implements. They make any textbox whose text content is a valid URL a link control. Since it is still a text box control it doesn't apply the link font styling that PDF link control does by default.
Notice that while the font styling doesn't look like a link both Edge and Chrome PDF client make that text box clickable and act as a link because it's content (http://google.com) looks like a valid URL:
You can style the textbox to make it appear like a link:
The limitation of this approach is that the link description (text box Value property in report designer) must be in the form of a URL. It will work as a link in most general public consumer centric PDF client. Some PDF client geared towards professional printing might not implement this behavior but it's unlikely to be an issue for your client base.
For versions prior to 2018R2 there's no way to display a proper link control in PDF as it requires re-compilation of Acumatica report module with code for that feature. If you absolutely need it, you could open a support ticket to assess whether or not Acumatica could retro-fit that change as a hot-fix for previous versions but there's no guarantee it will happen.
Our customers would like us to include fields from the SO Lines in our Sales Order confirmation email, which we are making available to be sent as part of the MailSettings Body for the Sales Order Confirmation report created through ReportDesigner.
Hypothetically, we are able to loop SO Lines like this for an Email Notification by using a foreach loop in the HTML, but I have been unsuccessful with this approach. (The GUI insists on translating my <> symbols into the ascii codes when I try save the directly edited HTML.)
I do not see a way of doing this at all in the MailSettings Body. How can I loop the data here?
EDIT: I found the instructions for linking to the email notification template from within the report so I can use one for both, so if anyone can help solve the mystery of using the within the Email Notification HTML without it automatically replacing the <> characters with ascii that will also solve my problem.
I used html comments to get <foreach> to work correctly inside of a table:
<table>
<!-- <foreach view="Transactions"> -->
<tr><td>Column 1</td><td>Column 2</td></tr>
<!-- </foreach> -->
</table>
I was able to solve this using the Notification Template; my error was in trying to do the loop in the HTML code instead of pasting directly into the Visual page. Functionality is quite limited in terms of being able to add headers for the table outside of the loop, but I got it working by adding another table outside the loop and setting width percentages for both tables. Ugly, but functional.
I need create documents from my software to api integration but I would like of mark the place of signature for client.
Its possible?
Sure, easy-peasy. When creating the DocuSign envelope, include a sign here tab with the create call. And use anchor text to tell DocuSign where the signature request should appear.
Here is the recipe. And here is example software that you can run on Heroku for free.
Note: in order to run the recipe on Heroku, you'll need a free developer account on DocuSign, plus a free integration key.
When creating envelopes in the DocuSign system there are generally three different methods for placing signature and other tabs.
Absolute (or fixed) positioning.
Relative positioning (aka Anchor Tags or Auto-Place).
PDF Form fields.
(1): With absolute positioning you can set the (x,y) coordinates of where you want to place tabs through your documents. You can set that manually by dragging and dropping through the DocuSign Website, or you can set those locations through the API. See Larry's API Recipes links.
(2): The anchor tagging (aka Auto-place) feature places tabs in your documents based on the actual document content itself. For instance, you can place a signature tab anywhere the text "Please Sign Here" is found in your document(s). However please note that it will place a signature tab for each and every instance of that string it finds, not just the first.
(3): The third option for placing tabs only work with non-flattened PDF files. If you have a PDF with form fields in it, DocuSign can read those fields and locations and place tabs there. This is easy and powerful, but of course only works with PDF files.
Learn more about all these option at the DocuSign Developer Center.
What I've found is that it will place a signature tab for every document in an envelope, even if the other documents are using a different server template.
I am using .net to integrate with DocuSign however I have a requirement to take a pdf/word/html file and send it via docusign but before add a few fields to the document. I believe adding the fields should be possibly from what I have read but I am unsure how to send the pdf / word / html file directly? Please note, I will not be using a template stored in DocuSign and filling in the fields.
Other question, if I do use a template, I see you can attach other documents but can I merge the template doc and my doc I am uploading into one or will it send two different files?
Thanks,
Alex
Yes what you want is to send a Signature Request on a Document (as opposed to on a Template) which is easy to do, you just need to make a multipart/form-data POST request. Have you gone through the DocuSign Developer Center and subsequently the API Tools page? One of the tools is the API Walkthroughs, which shows 9 of the most common API use cases, and you'll see that the 4th one (the middle left square) is titled "Request Signature on Document".
That code walkthrough shows in 6 different languages how to send a signature request on a local document- not sure what stack you're using since you didn't tag a language. You can copy the source for you're stack and fill in the variables (or mimic the code if your language is not listed) and that will request a signature on a document.
NOTE 1: These samples place one signature tab at location (100, 100) to just show how to use absolute positioning. You can alternatively use relative (or anchor) positioning, see Dev Center for more info.
NOTE 2: Most of the code samples send a PDF and therefore use a Content-Type of application/pdf. You will have to change that for your various document types.
To answer your question on if you can merge template documents with a local document(s) and send in one single request- Yes, you can use Composite Templates to accomplish that.
We have a system that creates pre-filled PDF contracts that we then need to send to the customer for signature and also allow the customer to update fields that may contain erroneous information.
I have reviewed the API extensively and understand that I can use text tabs placed on the document to allow customer to edit those fields. However this approach is not replacing the value already on the PDF, rather writing over it. See attached screenshot of sample document: DocuSign Overwrite text field
What is the alternative or any tips on how to get around this issue will be highly appreciated.
Here is one workaround or option but I hope there is a better way
1) Instead of using the templating engine that generates this PDF, move this burden to Docusign. We can then use the text tabs within Docusign to pre-populate fields and leave it editable.
When you send a PDF with form fields DocuSign can convert those PDF form fields into DocuSign data tabs which I believe is the workaround you've mentioned. This is definitely the easiest approach and should work.
You can do a quick manual test by uploading a document into the DocuSign console (ie login to your account through the website) and if you feed it a PDF with form fields the system will ask if you'd like to convert them to DocuSign tabs. To achieve this through the API you can use the transformPdfFields property in the document object.