In xCP, user can compose pages in xCP designer for different roles and role specific pages are shown to end user. A lot of requests have come from field where user wants to disable or hide a button on a page or a menu item in context menu or a set of form fields on the UI depending on basic or extended permission of the user logged in on an object. A lot of applications supported such use cases by firing a stateless process which fetched user's basic and extended permission.

This can be achieved easily in xCP 2.3. Permission (Basic as well as Extended) has been exposed as Business Object, Content, folder, cabinet model attributes. Permission values can be used in expressions like any other model attribute. E.g. Hide a button if user does't has RELATE Basic Permission on an object or hide copy menu item in context menu if folder object doesn't has CHANGE_FOLDER_LINKS Extended Permission. Since, these permission attributes are available with model, they can be used in instance pages or fragments and context menu.

Picture15.png

Picture16.png

Values of basic and extended permission attribute

 

Possible Values for Basic Permission (Integer/Single Value)

 

  • 1 – NONE
  • 2 – BROWSE
  • 3 – READ
  • 4 – RELATE
  • 5 – VERSION
  • 6 – WRITE
  • 7 – DELETE


 

Possible Values for Extended Permission (String/Multi Value)

 

  • EXECUTE_PROC
  • CHANGE_LOCATION
  • CHANGE_STATE
  • CHANGE_PERMIT
  • CHANGE_OWNER
  • DELETE_OBJECT
  • CHANGE_FOLDER_LINKS