Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A api
  • Project information
    • Project information
    • Activity
    • Members
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • ironapi
  • api
  • Wiki
  • Permissions

Permissions · Changes

Page history
Edited online authored Mar 12, 2019 by Andrea Pavlovic's avatar Andrea Pavlovic
Hide whitespace changes
Inline Side-by-side
Permissions.md
View page @ c6f9add4
...@@ -25,9 +25,11 @@ See [Category] for an example. ...@@ -25,9 +25,11 @@ See [Category] for an example.
## Tickets ## Tickets
Apart from read, create, edit and delete actions, there is an additional "set_department" action which will set the value of the cost_bearing_department of a ticket. Apart from read, create, edit and delete actions, there is an additional "set_department" action which will set the value of the cost_bearing_department of a ticket.
This is a good example for showing the xml definitions for different agenda, so here is how it's done:
``` ```
<transitions> <transitions>
<!-- custom transitions for customers - owner is set automatically and only some attributes may be set-->
<transition name="add" description="create ticket" notification="" pre-state="" post-state="" type="create" binding-reference="owning_client"> <transition name="add" description="create ticket" notification="" pre-state="" post-state="" type="create" binding-reference="owning_client">
<transition-attribute name="subject" required="true"/> <transition-attribute name="subject" required="true"/>
<transition-attribute name="category" required="true"/> <transition-attribute name="category" required="true"/>
...@@ -38,7 +40,7 @@ Apart from read, create, edit and delete actions, there is an additional "set_de ...@@ -38,7 +40,7 @@ Apart from read, create, edit and delete actions, there is an additional "set_de
</transition> </transition>
<transition name="purge" description="delete ticket" notification="" pre-state="" post-state="" type="delete" binding-reference="owning_client"> <transition name="purge" description="delete ticket" notification="" pre-state="" post-state="" type="delete" binding-reference="owning_client">
</transition> </transition>
<!-- custom transition for accounting -->
<transition name="set_department" description="pay the costs" notification="" pre-state="" post-state="" type="edit" binding-reference="cost_bearing_department"> <transition name="set_department" description="pay the costs" notification="" pre-state="" post-state="" type="edit" binding-reference="cost_bearing_department">
<transition-attribute name="cost_bearing_department" required="true"/> <transition-attribute name="cost_bearing_department" required="true"/>
</transition> </transition>
...@@ -46,21 +48,22 @@ Apart from read, create, edit and delete actions, there is an additional "set_de ...@@ -46,21 +48,22 @@ Apart from read, create, edit and delete actions, there is an additional "set_de
<agenda name="customer" description="customer creates tickets" binding-module="system" binding-entity="client"> <agenda name="customer" description="customer creates tickets" binding-module="system" binding-entity="client">
<agenda-bindings> <agenda-bindings>
<!-- see definitions of transitions above -->
<agenda-binding module="helpdesk" entity="ticket" transition="add" /> <agenda-binding module="helpdesk" entity="ticket" transition="add" />
<agenda-binding module="helpdesk" entity="ticket" transition="modify" /> <agenda-binding module="helpdesk" entity="ticket" transition="modify" />
<agenda-binding module="helpdesk" entity="ticket" transition="purge" /> <agenda-binding module="helpdesk" entity="ticket" transition="purge" />
</agenda-bindings> </agenda-bindings>
</agenda> </agenda>
<agenda name="employee" description="en employee - can see all comments and tickets" binding-module="" binding-entity=""> <agenda name="employee" description="en employee - can see all comments and tickets" binding-module="" binding-entity="">
<!-- default transitions - full create/edit/delete rights -->
<agenda-bindings> <agenda-bindings>
<agenda-binding module="rocks" entity="granite" transition="read" />
<agenda-binding module="helpdesk" entity="ticket" transition="create" /> <agenda-binding module="helpdesk" entity="ticket" transition="create" />
<agenda-binding module="helpdesk" entity="ticket" transition="edit" /> <agenda-binding module="helpdesk" entity="ticket" transition="edit" />
<agenda-binding module="helpdesk" entity="ticket" transition="delete" /> <agenda-binding module="helpdesk" entity="ticket" transition="delete" />
</agenda-bindings> </agenda-bindings>
</agenda> </agenda>
<agenda name="accounting" description="department bound accounting agenda" binding-module="helpdesk" binding-entity="department"> <agenda name="accounting" description="department bound accounting agenda" binding-module="helpdesk" binding-entity="department">
<!-- see definitions of transition above -->
<agenda-bindings> <agenda-bindings>
<agenda-binding module="helpdesk" entity="ticket" transition="set_department" /> <agenda-binding module="helpdesk" entity="ticket" transition="set_department" />
</agenda-bindings> </agenda-bindings>
......
Clone repository
  • API
    • Available Endpoints
    • Changing Passwords
    • Form Input Types
    • Introduction
    • Logout
    • Plugins
    • Queries
    • Queries
      • Attributes
      • Context
      • Query Examples
      • Query Search Options
      • Referenced Instances
      • Saved Queries
    • Schema_Changes
    • Storing Files
View All Pages