We decided to create a more powerful Adobe Sign workflow experience in a new ProcessMaker I/O use case. You can see the use case and how it was built by clicking here. The objective of the use case was to improve the performance of the Adobe Sign Web Widget. This is a very useful widget. The classic use case for the widget is a real estate rental company or equipment rental company that wants to put a copy of its contract on a website so that users can come to the website, fill out the agreement, and sign it with the rental company. This is a common "one-to-many" scenario. In this scenario, one company offers one contract type which can be signed with a single user. We can imagine another situation which adds a little bit of complexity. What if we need to allow for two signers? Well, this scenario is also very easy to handle. I simply need to route it to a second signer after the first signer and then back to the company.
The Next Level of Complexity
So far these use cases are not too special. However, let's imagine a third scenario. In this third scenario we will need a more powerful adobe sign workflow. The third scenario is one in which I may or may not have a second signer. It is conditional. This means that my routing engine has to be smart enough to handle the addition of a co-signer and only route the document to the co-signer when and if there is a co-signer. If there is no co-signer, then the signature procedure should occur as usual. This is a scenario that cannot be handled today in the Adobe Sign widget. So, if we want to do this we will need a way to make a more powerful Adobe Sign workflow.
