Documentation:Restricting data access: Difference between revisions

Restricting data access

Revision as of 06:01, 28 October 2024

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 the OCL Expression below 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 extreme of AccessGroups label, this will load Access groups view. Select the access group to control the page:

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.
Interest Groups

Note that interest groups are evaluated after access groups, it controls if we should bother to 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

@@ Line 1: / Line 1: @@
 <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.
 Below is a sample model, with a singleton class that has 2 attributes: Allowed Access and Interested as Booleans.
-[[Documentation:Access groups|Access Groups]]
+==== [[Documentation:Access groups|Access Groups]] ====
+[[File:Documentation Restricting data access 1729507697380.png|thumb|722x722px|none]]
-[[File:Documentation Restricting data access 1729507697380.png|thumb|300x300px|left]]
+<br />Create Access Groups through the AccessGroups Editor in the Designer as shown below: Add the OCL Expression below in the View Enable Expression (Enable of ViewModel edit Controls)<syntaxhighlight>
-<br /><br /><br /><br /><br /><br /><br /><br /><br />Create Access Groups through the AccessGroups editor in the Designer as shown below: Add the Ocl Expression below 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 extreme of AccessGroups label, this will load Access groups view. Select the access group to control the page:
-[[File:Documentation Restricting data access 1729510330368.png|thumb|300x300px|left]]<gallery>
+[[File:Documentation_Restricting_data_access_1729510330368.png|frameless|747x747px]]
-File:Documentation Restricting data access 1729510710335.png
+[[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]]
-</gallery><br /><br />Run the application in the browser select the different access groups and 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, it controls if we should bother to 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.