To effectively use this article, you’ll need to first:
Things you’ll need to have to follow along with this tutorial:
As with all journeys, we have to start somewhere. This will be an “end-to-end” tutorial of a very basic process flow using the Adobe Sign REST V6 API. …
What are these cookies that everyone is so concerned with? Well, they started as a way to track the current user so that profile preferences or other individualization could be saved to the browser for current or possibly future session use/reference on a website. Nice and convenient right? The concern is that like most things that make life “convenient” on the internet, these cookies can also be used to collect info about web browsing behavior and possibly other details about you and your internet habits, sometimes across a number of sites and locations across the web.
One of my favorite new features, available now in our Adobe Sign plugin for SharePoint, is what we call “Web Form Mappings.” This feature gives you the ability to create a web form (what in Adobe Sign parlance used to be called a widget), which is a “self-serve,” sign-enabled agreement, then use that as an entry point for internal or external customers. This will feed the data from that form they fill out and sign quickly, easily, and directly into SharePoint. …
One of the few things that separate us humans from the “lower animals” (not that I really really feel we’re so much higher on some imagined ranking) is our ability, in fact our innate nature to abstract our thoughts as some sort of set of symbols and write it down. This gives us a real leg up, allowing us to communicate our experiences to each other without needing to be there in person and make a record of these things that other people may “learn” from.
While this is not really a great reason to want to write, it’s a…
Techno-Geek | Father | Jack of many IT related trades | Customer Enablement Engineer — Adobe Document Cloud