Plugin: Site Directory Element Browsers Module
Participant Roles are used to manage permissions at the CDP™ level, see the description on the [purpose of roles]. This section gives a description of the setup and management of participant roles in the CDP™.
To get an overview of the participant roles open the Roles Browser by selecting the Roles icon on the Directory tab.
This browser gives an overview of the existing Participant Roles with Name and Short Name.
By expanding a participant role, the assigned Classes with Name and Short Name are listed, together with the Permission that has been set for each class.
For an overview of preconfigured or typical roles in a Concurrent Design environment, see the description of typical roles.
Persons with a role that has the permission Modify on the ClassKind Person Role are able to access the Roles Browser and create, edit or delete Participant Roles.
A description of the available functionalities is given below.
Next to these it is possible to use the generic functionality using the Search and Help
icons.
To make sure the latest data is shown in the browser, it is always possible to refresh it using the Refresh
icon.
To create a new participant role, select the Create Participant Role icon or in the context menu select Create a Participant Role.
On the Basic tab, provide the mandatory fields for Name and Short Name.
Furthermore it is required to specify the permissions on the available Classes.
The available choices for access rights on these classes are the following:
NONE
No actions allowed. All data for the selected class is not visible to the user in the CDP™.
MODIFY
All actions allowed (inspect, create, edit and delete or deprecate).
MODIFY_IF_OWNER
Actions of inspect and create are always allowed. Edit and delete or deprecate is only allowed for data for the selected class that is owned by the partipant.
Allowed editing actions exclude changing ownership.
READ
Read allowed (inspect). All data for the selected class within an engineering model to which the user is assigned as a participant is visible.
On the Permissions tab, all available classes are listed:
Actual Finite State List
representation of an actual finite state in an ActualFiniteStateList1
Common File Store
representation of a common FileStore for use by all Participants2
Domain File Store
domain specific FileStore for use by single DomainOfExpertise3
Element Definition
definition of an element in a design solution for a system-of-interest4
Element Usage
named usage of an ElementDefinition in the context of a next higher level ElementDefinition that contains this ElementUsage5
Engineering Model
representation of a parametric concurrent engineering model that specifies the problem to be solved and defines one or more (possible) design solutions6
External Identifier Map
representation of a mapping that relates E-TM-10-25 instance UUIDs to identifiers of corresponding items in an external tool / model7
File
representation of a computer file8
Folder
representation of a named folder in a FileStore that may contain files and other folders9
Iteration
representation of an Iteration of an EngineeringModel10
Model Log Entry
representation of a logbook entry for an EngineeringModel11
Nested Element
representation of an explicit element of a system-of-interest in a fully expanded architectural decomposition tree for one Option12
Nested Parameter
representation of a parameter with a value of a NestedElement13
Parameter
representation of a parameter that defines a characteristic or property of an ElementDefinition14
Parameter Group
representation of a group of Parameters within an ElementDefinition15
Parameter Override
representation of a parameter at ElementUsage level that allows to override the values of a Parameter defined at ElementDefinition level16
Parameter Subscription
representation of a subscription to a Parameter or ParameterOverride taken by a DomainOfExpertise that is not the owner of the Parameter or ParameterOverride17
Possible Finite State List
specialization of CategorizableThing that defines a finite ordered collection of one or more named States18
Publication
representation of a saved state within an Iteration where all computed values of the ParameterValueSets of a selected set of Parameters and ParameterOverrides are published to (i.e. copied to) the published values19
Requirement
representation of a requirement in a RequirementsSpecification[^]
Requirement Specification
representation of a requirements specification20
Requirements Group
representation of a grouping of Requirements21
After providing the required details, click Ok to create the participant role.
As mentioned in the section on the purpose of roles, these permissions can be used to customize the allowed views and actions in the CDP™. Note that for almost all classes, a participant role will need to have at least READ access rights to be able to see all the design data within an engineering model. The access right MODIFY_IF_OWNER allows the participant to inspect, create, edit or delete (or deprecate) the corresponding concepts, e.g. design data such as element definitions or parameters, that are owned by the Domain that the participant is representing. This participant will not be able to create design data on behalf of other domains, or edit these. For examples, see the description of typical role setups.
Note that it is in any case required to assign a Person Role when creating a Person to allow a user to login into the CDP™ and perform any possible actions, see the description of persons. To allow a person to open an engineering model, this person should be added as a participant to the model, and has to be assigned to a Participant Role.
To edit a participant role, select the Edit Participant Role icon or in the context menu select Edit.
It is possible to edit all the available fields on the Basic tab, as well as the permissions on the Permissions tab.
After making the required changes, click Ok.
Please be aware that editing a participant role will instantly affect all the persons on the [data source][CDP_D_S] that have this participant role assigned in an engineering model. Changing the permissions should therefore be done with great care to avoid that users are unintentionally limited in their available functionality.
The browsers in the CDP™ client of the user that performed the editing action will be updated immediately. Other CDP™ clients will be updated with a [refresh][Refresh].
On the Advanced tab, a Revision Number is given; see the description of Revision Number for details.
To inspect a participant role, select the Inspect Participant Role icon or in the context menu select Inspect.
In the Inspect modal dialog, all the details can be seen on the Basic and Permissions tabs.
Additionally the status of the participant role is given by the check box for Deprecated, see the description of Delete below.
The Advanced tab provides information that may be useful mostly to CDP™ database administrators. Given are the UniqueID and the Revision Number.
A participant role should not be deleted from the CDP™.
To delete a participant role, select the Delete Participant Role icon or in the context menu select Delete.
Items from the CDP™ are never completely deleted, but they are marked as Deprecated.
This Deprecated status is an indication to users that it should not be used anymore.
To export a participant role, select the Export Participant Role icon.
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.1 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.15 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.28 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.32 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.33 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.35 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.40 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.41 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.45 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.50 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.58 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.64 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.65 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.73 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.75 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.77 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.79 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.95 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.97 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.109 ↩
Source ECSS-E-TM-10-25-Annex-A, v2.4.1, ToC Reference Manual, section 4.108 ↩
Last modified 4 years ago.