In the video below we will review how to get started in the Kleeen Authoring Tool. In the old days, you would sketch out an application on paper, a whiteboard, or something similar. In this video we show how using our Kanban view will let you skip that step and start building right in the application.
To get started we need to introduce Things. Things are the Nouns your product is about. When you describe your product you probably say things like "We help with x". X is probably the first Thing your product needs, like Stocks, Employees, or Devices. After reviewing the content below you can read more about Things in our knowledge base articles focused on Things.
Getting Started with Things
Having built our first few things in the video above we can now add details to the Thing "Recommendation" as shown in the video below.
Things can also be a type of another Thing and inherit attributes from them. In the video below we show creating a Position Snapshot that inherits the attributes of Position by relationship. This is useful for building relationships that share information but are unique. For example in a student database, we may create a Thing called Person, that will track contact information and other important details. We can then create things that are a Student, Teacher, and Parents that are a Person and get the attributes inherent to that data relationship but simplifying the model managed in that software is created.
In our next video, we will look at setting up the right company, branding, and product details inside the application. This includes the screens where you can build out onboarding and set up your Github repository. Exporting to Github does require enabling the premium Kleeen plan.
We can now work on building Workflows. Workflows are the Things of your product in action. They will include visualizations, tables, configurations, and actions. Workflows can be thought of as what your application needs to do. Workflows are the verbs that provide actions to your Things. We will do this by expressing requirements as user stories.
Workflows: Putting your Things to Work
In this next video, we show a prototype with some Workflows and discuss how to get from Things to Workflows. In later videos, we will show more detail into this process. There are a lot more details about building your workflows in that section of our knowledge base.
To continue on with our application and prepare for Workflows, we went ahead and added two groups of things off-camera. The first of these groups is Transactions used to describe the purchase of the thing Stock. These Transactions are then presented as a Position. A Position is the daily value of our collection of Stocks. We also added sample data to Things to improve the look and feel of our generated prototype. This leaves us with these views of Things:
The Kanban view can be scrolled through and provides a lot of value in understanding the organization our application. As the application grows it is also helpful to consult the Thing Overview view.
This view provides a great view of how the front end, or user interface, will see the data model. We often refer to this as a symantec or conceptual model.
This view is a useful snapshot of the inventory of Things and their type and ability. This view will allow you to sort and filter your Things.
In our next video, we will walk through setting up the user story that will define a workflow. After watching this video we will have built a Workflow that is ready to finish with tables, actions, and widgets. Keep in mind that the Persona and Verb are open fields where any word you find appropriate can be used to describe the user story. Outside of the Verb Configure, these fields will have no impact on the workflow functionality.
After creating a user story we need to set up the experiences that will provide our user's insights and activities inside that workflow page. There are three main types of experiences we will explore in the videos that follow: summary, table, and insights.