As many other employees, my colleagues and I have to do our expenses manually. Luckily, we have K2 and, therefore, we automated the process. We created an Expense Claim App with the workflow in the background. However, it still takes a lot of time to submit the request. That is why I have been challenged by one of my colleagues to add the OCR functionality. I accepted the challenge and here is the article, which will quickly guide you, how to integrate a K2 Expense Claim App with ABBYY OCR. As a result, you will get a tool, that can scan your receipts and auto-fill the rest of your fields with the recognized values. And before I proceed any further, this is the final result, how all this can work.
Posts tagged as “REST”
I already described how you can easily create a REST API to integrate K2 with a NoSQL database. However, in the demonstrated example you had to make a call to http://localhost:3000. This means that the application should be hosted somewhere locally, which might be a suitable approach when you use K2 Five. But it is definitely unacceptable, when using K2 Cloud. That is why I decided to explain to you, how you can quickly deploy your REST API to Azure App Service.
Such scenarios are not common, that you need to use K2 with NoSQL databases. However, I would still like to show the possibility of a K2 platform to connect to NoSQL databases to 'CRUD' data. Moreover, the REST API I am trying to show is kind of dynamic. The object schema as well as the collection you are working with completely depends on the swagger schema you use with K2 REST Broker. The current approach is also suitable for a K2 Cloud platform.
Azure Functions is a serverless application platform. It allows developers to host business logic that can be executed without provisioning infrastructure. Functions provides intrinsic scalability and you are charged only for the resources used. In the article below I will show how to integrate Azure functions with REST ServiceBroker in K2.