Configuration

Custom / Specific Roles

 

Key Value Description

Role.admin

OE_ADMIN

This role is configured as a default admin role that has entire application access. Default is OE_ADMIN

Role.public

OE_PUBLIC

System user role configured as default public role

Crawler.role

Example: DATA_CRAWLERS

These are custom roles created in OvalEdge and configured to be used for crawling the new data sources.

Role.governance

 

These are custom roles created in OvalEdge and configured to be used for validating the custom fields in the incoming objects. Along with this the enforce. validateobjects key should also be changed to "TRUE". Then an advanced job to process validate objects needs to be executed.

Oe.userdelete.role

 

Alternative user management to delete the users

Tag.role

Example: TAG_CREATORS

These are custom roles created in Oval These are custom roles created in OvalEdge and configured to be used for creating parent and child tags in the application.

Ovaledge.api.role

Empty

API Role(Leave empty to permit all user roles)

Empty-accessed by anyone

OE_ADMIN- API's only accessed by OE_ADMIN