Optimization and visualization via Kanban Board
In the last step of your development, you should optimize your tables and, for example, add groupings by status or feature requests. You should hide unnecessary columns and create additional views such as a roadmap that only contains feature requests with the status “in planning”. You can also restrict which users can make which changes in your tables. For example, you should use column permissions to ensure that only you or selected people can change the status of individual feature requests.
Table permissions optimize your low-code application
Table permissions optimize your low-code application
As a final step, I recommend activating the Kanban usa rcs data plugin, as this provides a nice visual representation of your feature requests in their respective status. This means that as the creator and administrator of this table, you can also quickly and easily change the status using drag and drop.
Publishing your low-code application
This brings us to the end of the development of your low-code application. Your new feature request app offers two web forms for generating new feature requests and comments and a simple button for upvoting individual feature requests. On the other hand, your first application still offers a lot of potential for improvement. Be creative and just try it out. Of course, you can also find this application in our templates area.