General

About yourself
Trevor is a native Chicagoan and joined Neosavvy at the beginning of 2013. Over the course of his career he has participated in development efforts for Keyser Group, Bloomberg Sports, Pearson, Morgan Stanley, RunEnergy, and others. He is a graduate of Northwestern University where his combined study of computer science, film production, and history informs his diverse background and dynamic ability to facilitate communication and lead engineering efforts among various project team members and stakeholders. His past software experience begins with Adobe Flex and extends to Java Enterprise development, as well as Ruby on Rails and Python. As a developer, he is also proficient in Angular JS and other HTML5 technologies.

Trevor lives with his wife in Queens and enjoys concerts, cowboy boots, and barbeque.

Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
Our signatures are shrinking significantly when signed on a mobile our touch device. Attached is a PDF example of one of our contracts.
Hi - We're developing a new feature where our auto dealers can issue new versions of a priorly issues document. We were wondering if there was a good way to void the old one, but not delete it?
We are reviewing documents we have received back from E-Sign.
Receiving this error as we just switched our app over from sandbox to production.
There is a disclaimer at the base of the silanis E-Sign emails. Is there a good way to remove that via a flag in the API? Attached is an image. Thanks!

Replies Created

Reply to: Document already signed

0 votes
Hey Michael - Thanks for all your work. I just want to clarify that this will support our process. Our application is an auto insurance quote application. We write and sell the policies. Users create PDF contracts using our online system. The actual insurance is purchased through their auto dealer, so when I say 'dealer' below, I am referring to that dealer (not us). The contract, though issued by us, is between the dealer and the customer. The dealer 'always agrees', so that is the signature we would like to have on file. Here is the flow: 1) Document is created on our server with no human intervention. 2) At the end of our 'bid' flow, the document is uploaded to E-Sign. 3) Dealer signature is already there, but we have around 100 different dealers, so we would have to choose the specific one. 4) Document is sent out only to customer for E-Signing. Sorry about the complexity of the flow, but I just figured I would cover the bases. The big issue is that a human intervenes at no part of this process. We can have all the dealer signatures loaded on the server, but we need to have those ready in advance, and then have a way of knowing which one is which.

Reply to: Auto Signing

0 votes
I imagine if the feature is in the sandbox, it will be added to production eventually? Is this true? If not, I guess we need to make plans to go the other direction on this one.

Subscriptions

Topics Replies Freshness Views Users
Our signatures are shrinking significantly when signed on a mobile our touch device. Attached is a PDF example of one of our contracts.
3 7 years 3 months ago 14
Profile picture for user trevorewen
Profile picture for user harishaidary
Hi - We're developing a new feature where our auto dealers can issue new versions of a priorly issues document. We were wondering if there was a good way to void the old one, but not delete it?
1 7 years 4 months ago 45
Profile picture for user harishaidary
We are reviewing documents we have received back from E-Sign.
1 7 years 5 months ago 34
Profile picture for user harishaidary
Receiving this error as we just switched our app over from sandbox to production.
3 7 years 7 months ago 205
Profile picture for user trevorewen
Profile picture for user mwilliams
There is a disclaimer at the base of the silanis E-Sign emails. Is there a good way to remove that via a flag in the API? Attached is an image. Thanks!
1 7 years 8 months ago 8
Profile picture for user harishaidary

Code Share

one-span-sign npm module

Submitted on
This project is an open source node module for interracting with the popular One Span Sign (formerly eSignLive) REST API.
159 views
37 downloads

Subscriptions Release Notes

This user is not subscribed to any release notes.