Adobe Sign Connector

[weissreto]

Hi, I'm in need for a connector or product for Adobe Sign

Customer

Implemented for one of our customer project

Use Cases

Sign Documents (PDF) using the Adobe Sign

Integration

https://www.adobe.com/de/sign.html Open API: https://secure.eu1.echosign.com/public/docs/restapi/v6#!/transientDocuments/createTransientDocument

[ivy-rew]

juergeplohn is already building this

[ivy-sgi]

Let's go ahead with the approval and market integration of https://github.com/axonivy-market/adobe-esign-connector/tree/master

[ivy-sgi]

---

⚠️ do not remove this section, but leave it to track the reviewer's work.

Review Tasks

Product Domain

• [x] product successfully installs into the Axon Ivy Designer
• [x] product parts are marked as Connector or Demo
• [x] the product projects contains documentation to explain the functionality or use-case: e.g. Process-Notes, Input-Parameter descriptions, Meta-Comments on variables.yaml definitions ...
• [ ] the product readme fits into the market landscape @andreasbalsiger
• [x] all mandatory setup steps to run the Demo are documented in the setup section of the [myProduct]/product/Readme.md .

Technical Solution

Coherent

• [x] Common group-id for all artifacts <groupId>[org.arcme|com.axonivy].[util|connector].[product-name]<groupId>
• [x] Common artifact-id prefix: <artifactId>msgraph[-product|test|demo]</artifactId>
• [x] Html-Dalogs depend on suggested 'frame' template
• [ ] Github actions + maven-build runs as outlined in market-product template

Maintainable

• [ ] Dependent third-party infrastructure (e.g. Database, MavenRepos) is available: public accessible instance or shared as code (e.g. Docker, docker-compose)
• [x] Tests are implemented that verify, that the product actually runs
• [ ] Additional libraries (e.g. Maven dependencies) are lightweight: not duplicating libaries of the Axon.ivy Classpath Container.
• [x] Depends on standard Axon Ivy features and does not light-heartedly re-introduce forks of existing solutions (e.g. Job-Framework). Our goal is to integrate also third-parties into existing: Enginge-Cockpit-View, Log-Channels, Monitoring features, ...
• [ ] Uses latest ivy-environment: e.g. process-files and used project-build-plugin match the ivyProject version.
• [ ] Product is re-usable without the need to unpack and customize it for standard use-cases: crucial settings can be overriden with well documented config/variables.yaml