콘텐츠로 건너뛰기
메뉴
커뮤니티에 참여하려면 회원 가입을 하시기 바랍니다.
신고된 질문입니다
1 회신
20100 화면

Hi, I created a new group to have a middle level between "Project / Manager" and "Project / User". Once the group created is not accessible through the dropdown of User/Access Rights but as checkbox at the bottom of the page. Why it does that and how I can put it in the dropdown? Thanks

아바타
취소
베스트 답변

Yes it is strange behavior. If you inherit group one by one, then it will be in list (like roles). But if you have standalone at least one, then it will be like options. It cause impossible define exclusive roles.

If you need middle level, for example "Project/Specialist", then you need inherit Specialist from User and Manager inherit from Specialist.

<record id="group_xxx_user" model="res.groups">
    <field name="name">User</field>
    <field name="category_id" ref="module_category_yyy"/>
</record>

<record id="group_xxx_specialist" model="res.groups">
    <field name="name">Specialist</field>
    <field name="category_id" ref="module_category_yyy"/>
    <field name="implied_ids" eval="[(4, ref('group_xxx_user'))]"/>
</record>

<record id="group_xxx_manager" model="res.groups">
    <field name="name">Manager</field>
    <field name="category_id" ref="module_category_yyy"/>
    <field name="implied_ids" eval="[(4, ref('group_xxx_specialist'))]"/>
    <field name="users" eval="[(4, ref('base.user_root'))]"/>
</record>

, where xxx - name of module, yyy - name of category.

Or define it through web interface: "Settings/Users/Groups/Inherited"

아바타
취소

It's extremely useful, thanks. For those who don't understand it for the first read (like me): if you use a dropdown like Vasily suggested, a dropdown item will make the user the member off all groups ABOVE that group too! So this's why it's impossible to define exclusive roles.

관련 게시물 답글 화면 활동
10
12월 23
36854
0
12월 24
9567
3
9월 24
21826
5
12월 24
53134
4
7월 24
10647