Adobe Acrobat Sign vs. Drupal

Acrobat Sign isn't quite as user friendly as other E-Sign platforms I have used. However, it offers a wide range of features that provide convenience and efficiency. For example, I can have multiple people receive the same document separately, or I can have multiple people receive and review the exact same document. I also like that I can choose to set a signing order or not, this is important for when I send Offer Letters and other things that require order of approvals.

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

• Adobe Acrobat Sign tracks whether or not a signer has viewed a document
• Adobe Acrobat Sign tracks when a signer has signed, and the document has been sent to the next signer
• Adobe Acrobat Sign sends you confirmation emails and progress update emails along the way
• Adobe Acrobat Sign provides a "confirmation of signing" page at the end of the document package you put together, to prove the signatures are authentic

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Builds on Adobe platform so it is easy to utilize, but many features require enterprise subscription.
• Integrations available but your CRM integration is only available with enterprise license.
• Lots of templates but there are additional templates with enterprise only and there was no drag and drop editor.
• Adobe captures some analytical metrics but many of the analytics we required were not available - specifically metrics related to how the tool converts and reduces use time by our team and the impact on clients.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

It is by far the easiest service we have used to obtain digital signatures from employees. In the past we had done it by hand (a process I would not recommend for 1500+ employees) and with another company that would not allow us to create our own forms and would charge us for each form.

Incentivized

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

I've had very little trouble with it in all my uses with it. I do wish the text boxes you add wouldn't cut off the text if you entered too many words and that it would adjust it's size to fit within the space you've provided. However, that just takes a little refining in the initial set up of the document before you send it out.

Incentivized

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

I would have rated this a 9 or greater had they not had had such critical outages. They have taken steps to resolve this so I may come in and revise this

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

The Adobe Acrobat Sign's performance are excellent.

When we send electronic document by email for signature all the customers receive it regularly, nobody has any issue to open it and the signature phase was very easy. The user-friendly aspect of this product reduce or reset the call for IT support

Incentivized

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

It is a great tool to get signatures from the client and has reduced a lot of overhead that was caused before resulting in very long delays. With the integration of Adobe Acrobat Sign, we have reduced this delay making the process much smoother and more efficient.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The best types of training are well integrated into the product and Echosign does this well. As mentioned earlier in my review - there are some areas of functionality that can be difficult to understand ("only I sign") for the novice user. Other areas such as macro usage, bulk signature and so on were easily learned and understood via the online tools.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

We did not use it in the manner that most companies do, so I am pleased with how our company handled implementation. We will be pushing the full company over into Echosign for various processes which will incorporate more of an implementation effect.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

They are just different. Adobe's number one feature that puts it above it's competitors is that your document, the signing process, all of it exists within Adobe. There is no need to go from Word, to Adobe, to DocuSign. It saves you time and makes life easy for you (and for your clients).

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

At the beginning we assigned Adobe Acrobat Sign just to Purchase Office Department because at that moment we needed a tool that supported us to avoid manual signature and was compliance with remote working.

Now we are using it also in other situation because it help us with time and we can also reduce cost

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Significantly reduced the time required for document signing processes reducing wasted time and effort
• Cost savings since there is no longer any need to print and post/scan traditional signed paper-based documents
• Faster decision-making since time-sensitive decisions and approvals can now be processed much more quickly by using e-signatures.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs