Calyx RIM Administration

Field-Level/Page-Level Security

Field level/page level security is an optional Calyx RIM function. You can create roles in the system that enable you to assign field-level/page-level security. Each role has a set of fields that can be defined as read-only, modifiable or hidden for each page on which these fields reside.

Calyx RIM provides three XML-mapped roles: user, liquent_role1, and liquent_role2. When you create a role, you associate it with one of the XML-mapped roles available. Users and groups assigned to the role you create have access to fields as defined by the role. Field-level/page-level security applies to the following Calyx RIM entities:
  • Product Families
  • Products
  • Applications
  • Registrations
Note: For each role, each field on these entity pages is defined as read-only, modifiable, or hidden.

Users associated with liquent_role1 and liquent_role2 have the ability to create product families. While it is best practice is to not give liquent_role1 or liquent_role2 users data administration access, you can add the following empty field group to liquent_role1 and liquent_role2 in the meta.overrides.xml to prevent members of these roles from creating product families:

<fieldGroup name="adminCreateFieldGroup"/>

Please note, if the overrides file is modified to use this fieldGroup, a harmless MetaException error will occur.

Calyx RIM ships with three roles. However, there is no limit to the number of roles you can define. Contact your Account Executive to consult with our Client Enablement team for information about defining and configuring field-level security for your system.

If you do not use field-level security, the following apply:

  • Users/groups with the appropriate security privileges are able to view all attributes associated with the product family, product, application and registration entities.
  • Users/groups with the appropriate security privileges are able to create and modify product family, product, application and registration entities.