Role Concept

Customizing

The first step for customizing is the definition of all object instances of the role concept (privileges, roles, positions, projects/org. units, and users). The next step - if applicable - is the implementation of access rules. An additional task involves assigning masks/selections/fields, tasks or access rules to userexits and their parameters.

The following privileges are predefined:

Privilege (task)

Description

EDB-ART-CRM-CWA

Create new version of an item (includes all structures)

EDB-ART-CRM-CWI

Create new version of an item (includes all selected structures)

EDB-ART-CRM-CWO

Create new version of an item (without structures)

EDB-ART-DEL-VER

Delete version of an item

EDB-ART-DEL

Delete item

EDB-ART-INS

Create new item

EDB-ART-UPD

Change item

EDB-DOC-3DM-DEL

Delete document of type 3D_MODEL

EDB-DOC-3DM-INS

Create new document of type 3D_MODEL

EDB-DOC-3DM-UPD

Change document of type 3D_MODEL

EDB-DOC-ARC-DEL

Delete document of type ARCHIVED_DOC

EDB-DOC-ARC-INS

Create new document of type ARCHIVED_DOC

EDB-DOC-ARC-UPD

Change document of type ARCHIVED_DOC

EDB-DOC-CRM-CWA

Create new version of a document (includes all structures)

EDB-DOC-CRM-CWI

Create new version of a document (includes all selected structures)

EDB-DOC-CRM-CWO

Create new version of a document (without structures)

EDB-DOC-DEL-VER

Delete version of a document

EDB-DOC-DEL

Delete document via document master

EDB-DOC-DRF-DEL

Delete document of type DRAWFILE

EDB-DOC-DRF-INS

Create new document of type DRAWFILE

EDB-DOC-DRF-UPD

Change document of type DRAWFILE

EDB-DOC-DRW-DEL

Delete document of type DRAWING

EDB-DOC-DRW-INS

Create new document of type DRAWING

EDB-DOC-DRW-UPD

Change document of type DRAWING

EDB-DOC-PHM-DEL

Delete document of type PHYSICAL_MODEL

EDB-DOC-PHM-INS

Create new document of type PHYSICAL_MODEL

EDB-DOC-PHM-UPD

Change document of type PHYSICAL_MODEL

EDB-DOC-TXT-DEL

Delete document of type TEXTFILE

EDB-DOC-TXT-INS

Create document of type TEXTFILE

EDB-DOC-TXT-UPD

Change document of type TEXTFILE

EDB-DOC-UPD

Change document master

EDB-EWR-DEL

Delete work request

EDB-EWR-INS

Create new work request

EDB-EWR-UPD

Change a work request

EDB-GRP-DEL

Delete class (item group or classification list)

EDB-GRP-INS

Create new class (item group or classification list)

EDB-GRP-UPD

Change class (item group or classification list)

EDB-ORD-DEL

Delete order

EDB-ORD-INS

Create new order

EDB-ORD-UPD

Work order

EDB-PRO-CRM-CWA

Create new version of a project (includes all structures)

EDB-PRO-CRM-CWI

Create new version of a project (includes all selected structures)

EDB-PRO-CRM-CWO

Create new version of a project (without structures)

EDB-PRO-DEL-VER

Delete version of a project

EDB-PRO-DEL

Delete project

EDB-PRO-INS

Create a new project

EDB-PRO-UPD

Change project

EDB-VAR-DEL

Delete variant placeholder

EDB-VAR-INS

Create new variant placeholder

EDB-VAR-UPD

Change variant placeholder

One step in the preparation of the implementation is to define for all roles which object classes must be protected for each function. Additionally, the user functions must also be defined. The composition and relationship between Agile e6 object classes and functions are to be documented by means of a matrix as shown in the following example.

Role: Design Engineer

You can now assign privileges to the previously described combination of functions and Agile e6 objects which in turn can be applied against roles.

In an additional step, you must check all elements of the user interface (fields, selections, menus) with regard to which privileges can be executed in certain events and under what circumstances.

In the implementation of the role concept one needs to differentiate between standard manipulation functions (such as Create, Change, Delete, ...) and user functions.