Documentation:Restricting data access: Difference between revisions

Restricting data access

Latest revision as of 06:34, 20 January 2025

This page was created by Stephanie@mdriven.net on 2024-04-05. Last edited by Edgar on 2025-01-20.

Restricting Data Access in MDriven can be achieved in 3 ways including the following ways.

Below is a sample model, with a singleton class that has 2 attributes: Allowed Access and Interested as Booleans.

Access Groups

Documentation Restricting data access 1729507697380.png

Create Access Groups through the AccessGroups Editor in the Designer as shown below.

Add this OCL Expression in the View Enable Expression (Enable of ViewModel edit Controls).

Singleton.oclSingleton.AllowedAccess

To enable the AccessGroup on a ViewModel, click on the 3 dots at the extreme end of the AccessGroups label. This will load the Access groups view. Select the access group to control the page:

1️⃣

2️⃣

Run the application in the browser and select the different Access groups. Observe the page response when the different access group to which the page is not attached responds as shown above.

Note that interest groups are evaluated after access groups. Access groups control whether we can show the tagged action to the user or not. Interest groups only control the visibility of a tagged action. They are also used to declutter the left-side menu.

ViewModel-Enable

See also:

@@ Line 1: / Line 1: @@
+{{Edited|July|12|2025}}
 <message>Write the content here to display this box</message>
-Restricting Data Access in MDriven can be achieved in 3 ways which are:
+Restricting Data Access in MDriven can be achieved in 3 ways including the following ways.
-[[Documentation:Access groups|Access Groups]]
+Below is a sample model, with a singleton class that has 2 attributes: Allowed Access and Interested as Booleans.
-Below is a sample model, with a singleton class that has 2 attributes: AllowedAccess and Interested as Booleans.
-[[File:Documentation Restricting data access 1729507697380.png|thumb|300x300px|left]]
-[[File:Documentation Restricting data access 1729507814010.png|thumb|300x300px]]
+==== [[Documentation:Access groups|Access Groups]] ====
+[[File:Documentation Restricting data access 1729507697380.png|thumb|722x722px|none]]
+<br />Create Access Groups through the AccessGroups Editor in the Designer as shown below.
+Add this OCL Expression in the View Enable Expression (Enable of ViewModel edit Controls).<syntaxhighlight>
+Singleton.oclSingleton.AllowedAccess
+</syntaxhighlight>To enable the AccessGroup on a ViewModel, click on the 3 dots at the extreme end of the AccessGroups label. This will load the Access groups view. Select the access group to control the page:
+️⃣[[File:Documentation_Restricting_data_access_1729510330368.png|frameless|747x747px]]
+️⃣[[File:Documentation Restricting data access 1729510710335.png|frameless|748x748px]]<br /><br />Run the application in the browser and select the different Access groups. Observe the page response when the different access group to which the page is not attached responds as shown above.<br />
+==== [[Documentation:AccessGroups, InterestGroups and ViewModel-Enable|Interest Groups]] ====
+Note that interest groups are evaluated after access groups. Access groups control whether we can show the tagged action to the user or not. Interest groups only control the visibility of a tagged action. They are also used to declutter the left-side menu.
+==== [[Documentation:AccessGroups, InterestGroups and ViewModel-Enable|ViewModel-Enable]] ====
+[[File:Documentation_Restricting_data_access_1729512564921.png|frameless|782x782px]]
+'''See also:'''
-<br /><br /><br />[[Documentation:AccessGroups, InterestGroups and ViewModel-Enable|Interest Groups]]
+* [[Documentation:AccessGroups, InterestGroups and ViewModel-Enable|AccessGroups, InterestGroups, ViewModel-Enable]]
+* [[Documentation:Access groups|Access Groups]]
-[[Documentation:AccessGroups, InterestGroups and ViewModel-Enable|ViewModel-Enable]]