Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Access rights
 
Notifications
Clear all

Access rights

8 Posts
2 Users
0 Reactions
3,453 Views
Jan
 Jan
(@kobetsu)
Posts: 101
Active Member
Topic starter
 
[#8683]

Hello,

Happy New Year BTW,

Using views of "AccessProfileAll" and "AccessRight" I'm able to build map of rights associated with given profile but I cannot access rights collected in UI
as "Specific access", "Access to reports", "Access to forms".

Please tell me in which DB view I can find info about:
a. "Specific access" of given profile
b. "Access to reports" of given profile
c. "Access to forms" of given profile
 


 
Posted : 02 Jan 2023 21H18
(@babynus)
Posts: 14952
Member Admin
 

a. "Specific access" of given profile => habilitationother
b. "Access to reports" of given profile => habilitationreport
c. "Access to forms" of given profile => habilitation


 
Posted : 03 Jan 2023 11H31
Jan
 Jan
(@kobetsu)
Posts: 101
Active Member
Topic starter
 

Thanks.
One more question...
In view "AccessProfileAll" and similar like "AccessProfileNoProject" seems there is no clear separation between ProjectDependend and ProjectNotDepended access rights. Looks like I have to use "AccessProfileAll".
Is there a view getting only info about ProjectDepended and another view of ProjectNotDependent access right ?
I see field "isNonProject" but looks like it is not accessible.


 
Posted : 03 Jan 2023 11H42
(@babynus)
Posts: 14952
Member Admin
 

AccessProfile : for project dependant
AccessProfileNoProject : for non project dependant
AccessProfileAll : for both

Note that there are profiles with same names in first and second, but they have different ids


 
Posted : 05 Jan 2023 16H11
Jan
 Jan
(@kobetsu)
Posts: 101
Active Member
Topic starter
 

1.
In rights of given profile I found right described as "Global view" which is stored in "AccessProfile" (project dependend) but I do not see this right in PQ in administrator/Access to data (project dependant) view. I found it in "habilitation".
So looks like "Global view" exists (in DB) in "habilitation" and in "AccessProfile".

Am I right that this one in "AccessProfile" is garbage ?
If YES, is it danger for pq stability ? Is there any tool to clean up such garbages ?

2.
Additionally, I see we have in out db profiles (habilitation table) which does not exist in the table AccessRight.
These profiles have id and name with the same value (numerical).
Looks like some garbages.
Is it danger for projeqtors stability ?
Is there any process we can clean up such items ?

3.
Additionally, I see we have in our db duplication of records in table habilitation - means - there are double records for idMenu=263 (nameMenu = "Translations").
I suppose projeqtor take first occurence to get info about rights.
Looks like some garbages.
Is it danger for projeqtors stability ?
Is there any process we can clean up such items ?

4.
Additionally I see we have in our db, in table "habilitation" record with nameManu = "Financial" which seems does not exist in PQ UI / Access to forms.
Looks like some garbages.
Is it danger for projeqtors stability ?
Is there any process we can clean up such items ?
 


 
Posted : 07 Jan 2023 23H30
Jan
 Jan
(@kobetsu)
Posts: 101
Active Member
Topic starter
 

Any response ?


 
Posted : 14 Jan 2023 12H29
(@babynus)
Posts: 14952
Member Admin
 

[list=1]

  • There is no "Global view" record in AccessProfile in standard deployed version.
  • "Global view" is only a menu name in standard deployed version.
    This is an access mode added by your admin.
    So if it is not used, it is secure to delete.

  • Yes, items that appear in lists with a number are items that do not exist any more.
  • Framework is built so that is should not be possible to delete profiles that have Habilitation or AccessRight.
    Possibly those profiles where manually removed from DB.
    There is no way to fix mannually added inconsistancy other that manually delete.
    It should be OK to delete them, but manual delete in the DB are never secure.

  • Yes, there should have no duplicate for (idProfile, idMenu) in table habilitation.
  • This is fixed with standard migration process.( functrion deleteDuplicate() )

  • Yes, this some to be some garbage.
  • Possibly historically righ, that was not removed when upgrading the model.
    This will have no side effect on the application.
    Can be delete or not.
    Possibly we'll include cleansing in a next version (no hurry for that)

     
    Posted : 16 Jan 2023 11H29
    (@babynus)
    Posts: 14952
    Member Admin
     

    After reflexion, point 4 should not be an issue.
    May still be used for Old GUI menus : this record will tell if the parent menu must be displayed for the users with this profile.


     
    Posted : 16 Jan 2023 11H34
    Share:

    Scroll to Top