0
I have many questions to model data of the type Posts. Ex:
funcionario------cargo = 1
chefia-----------cargo = 2
chefia da chefia-cargo = 3
big boss---------cargo = 4
In that case, it would be interesting for me to create a screen that would show all the options regardless of your position level, and when you want to enter a restricted place I would ask if you have the proper position and would not let you pass or create a screen for each position?
2
The two approaches are valid. The choice depends on some factors:
Similarity - how much the canvas of each post is similar or not. This way, it can make sense to even mix the two approaches. For example, you can decide that the employee screens and the big Oss are very different and each have their own screen, while the bosses' screens are more similar and a single screen, with small differences solves.
Complexity - On the opposite side of the previous item, what is the complexity of each screen? What data sources does it have to load? What are the differences between each actor?
Scale - And tomorrow? How much can this system grow? Who will provide maintenance?
Usage - Each user will have access to a computer or they have to share the same?
Structure - Depends on the style of the developer. Some prefer few files with a lot of built-in functionality, while others prefer to spray code on several smaller files.
All these details should be weighed in choosing your approach.
Another question you raise is the identification of the position. It is assumed that being a business system, the user identifies himself when starting the use of the computer (login) and at this time, you would already direct the screen to this subject.
Otherwise, that is, use without identification, you have no choice but to show all options and restrict access according to the case.
1
I think you could tailor the screen according to its proper position, but this would not need to get sample for the user, for example:
user 1 cargo 1 ---- vai acessar a tela perfil(ex.) > adiciona elementos genericos
user 1 cargo 2 ---- vai acessar a tela perfil(ex.) > genericos + (elemento relacionado ao cargo)
user 3 cargo 1 ---- vai acessar a tela perfil(ex.) > generico
but then you check for results of some API and add the elements in the form of single page application.
Browser other questions tagged front-end
You are not signed in. Login or sign up in order to post.