Kleeen's instant prototype function generates a code repository that is human readable and well commented. This also includes the patented ability to generate a specified API that makes a connection to production data easy and efficient, what we call the KAPI or Kleeen API.
This is a process with the following steps:
- Locating the folder in the code repository for the widgets in the application.
- Identifying the data needed to feed the widgets.
- Generating the needed webbooks to provide the data.
- Coding the connection to the data and making any necessary transformations
In this series of articles, we will explore the process of wiring up a Kleeen authored application. This will include a sample application and code that will use a single endpoint to feed multiple widgets. At the end of this you should have a solid understanding of this process and be able to wire up a remaining widget in the sample application and understand the requirements you will need to build the connections to your own applications.
For step 3, the number and source of the webhooks is up to you and the architecture of your system. You can choose to make one endpoint for multiple widgets. For this you will probably start with a table that feeds the workflow and identify all the fields needed in one endpoint. You can also use endpoints from multiple systems if you would like. Kleeen is agnostic to data sources as long as JSON formatted data is returned or transformed.
You should also take note that any connections you make will be inside the source code you own. Kleeen will not see the wiring or any of your data passed in these connections.
Additonal articles are referenced to show:
Please reach out to firstname.lastname@example.org if you need assistance.