This topic contains 5 replies, has 0 voices, and was last updated by randmname 8 years, 7 months ago.
-
AuthorPosts
-
June 1, 2015 at 6:33 am #4167
rudlerAdobe has combined EchoSign with Acrobat and called it Document Cloud. How does this affect the Adobe EchoSign for NetSuite v3 ?
This is a cached copy. Click here to see the original post. -
January 12, 2016 at 12:27 pm #4168
randmnameThe honest truth is, it’s just a new licensing/branding/login mess. You can buy some Echosign functionality thru Adobe Document Cloud subscriptions, but Echosign also still has a separate sales team that sells the type of account you’ll need for the integration. The naming of these accounts is clear as mud (Adobe DC Premium eSign services P2 is what we ended up with, good luck finding that on their website).
Furthermore, the Echosign (Adobe eSign Services) website has a separate login from your adobe ID. It’s very confusing. You might be able to buy Adobe eSign thru Adobe sales, if so I’d do that and not try messing with the Echosign salespeople (who are borderline incompetent).
-
January 12, 2016 at 2:38 pm #4169
randmnameSecond update – you ask about bundle v3, but there’s now a v4.0.0 available called Adobe eSign services. The main thing it looks to have updated is the authentication between NetSuite and Echosign to go from a key to OAuth based authentication. My initial testing indicates not much else has changed.
If you do test the eSign 4.0 bundle in a sandbox, you will get an error saying the suitelet’s not installed; just look at the URL and you will see that the NetSuite production URL is present; switch to the sandbox url and it’ll complete the install. Sloppy code.
-
January 20, 2016 at 6:09 pm #4170
rudlerThanks. One of the nice thing with e-sign services is the ability to host a document somewhere and then get notification when someone has signed it. BTW, our company never purchased it. As a workaround, I’ve used Survey Gizmo to do this (it has e-sig functions)
-
February 11, 2016 at 5:22 pm #4171
randmnameYeah e-signing has done very well for our business, I just wish Adobe/Echosign did a better job documenting what their plans are and how eSign is different from Acrobat/Document Cloud… because they are very different.
Also, as noted before, the Echosign plugin for NetSuite generally works, but IS a bit buggy. At some point I might consider rolling our own integration, but for now it works.
-
April 4, 2016 at 10:59 am #4172
randmnameOriginally posted by randmname
View Post
Second update – you ask about bundle v3, but there’s now a v4.0.0 available called Adobe eSign services. The main thing it looks to have updated is the authentication between NetSuite and Echosign to go from a key to OAuth based authentication. My initial testing indicates not much else has changed.
If you do test the eSign 4.0 bundle in a sandbox, you will get an error saying the suitelet’s not installed; just look at the URL and you will see that the NetSuite production URL is present; switch to the sandbox url and it’ll complete the install. Sloppy code.
Also Adobe has recently removed access to view your account’s API Logs on the eSign website… so when something bad happens, you really have no way of troubleshooting. I raised a support ticket for this and they told me it is now being provided to developers only, and to contact Support if I need to view my own logs. It took them a full month to give me that answer after I asked why they disappeared.
This is a huge disappointment.
-
AuthorPosts
You must be logged in to reply to this topic.