Our latest example app is an Equipment Tracker. This is an online database of available equipment that employees can log in and view. They can then “check out” an item, which sets that item as unavaliable for anyone else to checkout.
We used “Equipment” but this app would also work well for libraries, rentals, and any resource tracking where items need to be removed from availability.
This is a good example of using form rules to add connected records. In this case, whenever an item is borrowed or returned, it adds a log of the transaction to the item’s history.
This enables Admins to view a complete checkout history of each item, tracking when it was checked out and returned:
This is type of logging could be used for a variety of scenarioes including versions, history, change logs, and more.
It’s also a good example of establishing “work flow” in Knack, where you can use a form rule to set a “status” field and then filter your views to only show records with certain status values.
In this case, we’re only showing equipment items where “status” equals “available”. Checking out an item uses a form rule to set the status to “unavailable”.
You could use form rules to set a status from new to pending to approved and have different user roles see the records for each status.