The most valuable feature is APIs. Its integrations are very flexible, allowing developers to connect multiple applications like DocuSign, Salesforce, OpenText, and SEB. I particularly utilized this feature in a product called "agreements" under Pharma International. It's employed for contracts between Pharma International and any subsidiary or layer. It automates the cycle approval for Pharma International, reading any PRs (purchasing requests) and purchasing orders from SEB related to the agreement. It's also linked through NEDI between KiSSFLOW and SEB. Regarding the digital signature process it's completed by DocuSign. We've established a connection through an API between KiSSFLOW and DocuSign. We also use OpenText as our archiving tool and have integrated it into our flow. So, those are four systems connected through KiSSFLOW. The API begins by reading data, purchasing orders, and purchasing requests from SEB. When a user submits any contract or agreement on the KiSSFLOW form, it initiates its own automated workflow within KiSSFLOW. The signing process is then executed by DocuSign. To break it down, first, data is read from SEB, followed by an automated workflow. Once this workflow completes, the contract's signing process occurs via DocuSign, catering to both the users and the associated companies. For the third party and VIP, the contracts then go through Logistics. This entire process is primarily based on API integrations. Hence, the flexibility, scalability, and stability between those four systems with KiSSFLOW are noteworthy.
