nuBuilder Forum

Hello,


Is there any place where I could find a todo list app example made with nubuilder working with Access Control List ?
If anyone has done that, I would highly interested for me and to learn how to build that with nubulder.

Many thanks,

Yves

Hi,

What are the requirement specification for the todo list? (functionalities, permissions etc.)

Hello,

I wouldn't be too specific because I would be interested to see if someone has got already something on this subject.
Ideally :

1.- Access Control List
3 levels :
Admin, Assistant, User

2.- ToDo List table
Task Label (Mandatory - Text), Task Description (Memo), Task Target Date Time (Mandatory, DateTime), Status (Mandatory, Text), Assigned to (Mandatory, List coming from user's list ACL), History (Read Only, Previous Value --> New Value, Read Only), Created by (Read Only), Creation Date(Read Only), Last Modified by (Read Only), Last Modified Date (Read Only)

Status should be managed dynamically. In a first approach, here is the list of status : Not Assigned, Assigned, In Progress, Done, Cancelled in this order.

3.- Features
Admin can see all tasks for all users, Assistant can see tasks for the users they work for, User can see the task assigned to them only.
We need to have a configuration screen in which we define : list of status, list of parent users for assistant (it could be several users)
Anyone can create a task and could assign task to any user. Everything is logged and we know the full history of any tasks.

Admin role :
Only admin could define list of status and its order, creates users and assistants. He will connect assistant with its related user(s).
Admin sees the full list of tasks. It could change the status, change the assignment, create, update and Delete records. It is the only one able to delete tasks.

Assistant role :
Assistant sees the list of tasks of its related users. it could create tasks, and update tasks. It cannot delete tasks.

User role :
User sees only its list of tasks. It could create and update tasks. It cannot delete tasks.

Search should work only with the list of tasks visible of the related role. For example if I am a user, I should be able to search only on my task list.

4.- UI
We need to be able to interact with this list with desktop mainly but also with mobile if possible (need to know the limits with nubuilder especially with grids)

Happy if anyone could help building this webapp, maybe almost responsive if possible.

Ideally, limit as much as possible the code in order to have a low code application, almost no code in it.

If you have one app closed to this one, more than happy to review it.

Any question, let me know,

Yves

I think it's feasible to create such an app.
However, it will not be possible to do it entirely without coding. Especially the history, modified data, permission management needs coding.
There is also the question of how the list is displayed The screen width is limited (especially on a mobile device).

Hello,

I agree we need code to build it. I would like to have code at minimum in order to have an idea about the right way to code with nubuilder .
For the screens, will it be possible to have several screens for different targets (smartphones , tablettes, and desktops ui). Do we need to define precisely the size if each target screens or can we leverage the 12 columns mechanism ? (Responsive - I see Mobile checkbox when creating tables in the last nubuilder pkg, maybe we could leverage this nubuilder feature)

Many thx for ur help.

Yves

In my opinion, a good approach is to design the form primarily for a mobile device (MD) (e.g. 400px) and use an embedded iframe (run button, iframe) to display the tasks. The iframe can be changed in width and height depending on the resolution when the form is loaded.
On a MD, you can scroll to the right, where the less relevant columns can be found (or you open an entry to see all fields below each other, if the Mobile view setting is enabled)

Just a short demo what it could look like on a MD:
And on a wider screen, it would look something like: