Greetings to all! I had a problem of this kind: there are a few users on the system monitor, you need to do so that would be when you log on with your personal data, they could only see their facilities for monitoring. There is also a user such as "The Boss" which should see all of the objects of all the operators, but the change in them could not. How do I do it. ???
How do I know where you can have permissions to create a group of users who see all objects and can only come into their own. I do not like it when a lot of difficult objects to find their tree. No way the search bar in the tree, and without this element is difficult to look in the right tree. https://www.winccoa.com/fileadmin/image ... _scada.pdf
Dynamic tree widget
Search
Dynamic tree widget
- Attachments
-
- users_scada.pdf
- (2.47 MiB) Downloaded 249 times
Re: Dynamic tree widget
I'm not sure if I fully understand your questions, but let me try.
I guess there are two ways that you might consider.
1) The most elegant is called 'CNS' or COmmon Name Service. It has been in OA for some time but the first proper editor is scheduled for 3.13 (2015). The CNS is like a model that you define on top of your datapoints. The scenario that you describe would be perfect for CNS but today, you would have to script everything yourself. CNS is a model that you can use to make your datapoitn tree look different. That is : instead of having datapoint type and instance you could call the nodes anything you want. You could call it area, machine, component, variable. Internally, you would still be using the sama datapoint.
2) The second option would be to implemnent your own tree from scratch. You could give your datapoints an element called 'area'. You could then use the standard user management to define areas and assign them to the users. User1 gets area1, user2 gets area2. The 'boss' gets permission for all the areas.
You could then user 'getUserPermissionForArea()'. This would solve the fact that persons see different parts of your tree
But you also want to give the 'Boss' different options in the tree. You could achieve this by defining multiple 'permission bits'. Example: the user gets userpermission 4. The Boss gets permission 5.
If you like to be innovative then take option (1) and call Lukas Schopp. If you want a result fast then you'll have to build ther whole tree by yourself. Should not be so much.
Good luck
Frenk
I guess there are two ways that you might consider.
1) The most elegant is called 'CNS' or COmmon Name Service. It has been in OA for some time but the first proper editor is scheduled for 3.13 (2015). The CNS is like a model that you define on top of your datapoints. The scenario that you describe would be perfect for CNS but today, you would have to script everything yourself. CNS is a model that you can use to make your datapoitn tree look different. That is : instead of having datapoint type and instance you could call the nodes anything you want. You could call it area, machine, component, variable. Internally, you would still be using the sama datapoint.
2) The second option would be to implemnent your own tree from scratch. You could give your datapoints an element called 'area'. You could then use the standard user management to define areas and assign them to the users. User1 gets area1, user2 gets area2. The 'boss' gets permission for all the areas.
You could then user 'getUserPermissionForArea()'. This would solve the fact that persons see different parts of your tree
But you also want to give the 'Boss' different options in the tree. You could achieve this by defining multiple 'permission bits'. Example: the user gets userpermission 4. The Boss gets permission 5.
If you like to be innovative then take option (1) and call Lukas Schopp. If you want a result fast then you'll have to build ther whole tree by yourself. Should not be so much.
Good luck
Frenk
-
Gertjan van Schijndel
- Posts: 634
- Joined: Mon Aug 02, 2010 10:37 am
Re: Dynamic tree widget
If the number of facilities is limited, you could use a permissionbit for each facility. This permissionbit can be set in the paneltopology and should make only the facilities visible for which the user has permission.
This option has the advantage over the CNS option that it uses already available data rather then adding more data to the database.
This option has the advantage over the CNS option that it uses already available data rather then adding more data to the database.