HowTo:Configure Users and User Rights - Revision history

NWE: /* See also */

2025-05-05T15:26:03Z

‎See also

2020-01-17T17:00:42Z

2020-01-16T18:28:50Z

2020-01-16T17:52:24Z

‎Controlling the visibility and editability of objects

2020-01-16T14:03:57Z

2020-01-16T14:02:19Z

2020-01-16T13:54:25Z

2020-01-16T13:48:14Z

‎Login

2020-01-15T22:31:32Z

‎Evaluating rights

2020-01-15T22:31:20Z

‎Controlling the visibility and editability of objects

@@ Line 168: / Line 168: @@
 ==See also==
 * [[Login]]
 * [[HowTo:Relate_Objects]]

@@ Line 76: / Line 76: @@
 		// First, let's define our result collection containing the group rights.
 		List<UBIK.Service.DTO.V240.GroupRight> results = new List<UBIK.Service.DTO.V240.GroupRight>();
 		// We'll add the default rights in case we don't have defined any specific rights for the active user's group.
-		results.AddRange(defaultRights);
+		if(defaultRights != null)
 		// Now we try to find the rights defined for this object.

@@ Line 125: / Line 125: @@
 * The ''TARGETTYPERIGHT'' of the rights relation must be MetaMetaClass, because this is the meta class (i.e., the type) of meta classes (which we want to relate to user groups in this case). It's a bit tricky to get the MetaMetaClass using Studio. You'll have to do it using Whobert, fetching and assigning the MetaMetaClass with the following code:
 ** First, we'll ask the Environment for the meta meta class system object. We'll get the Environment from any (''BaseClass'') object, e.g., the parameter object for Whobert.
-** UBIK.Kernel.MetaMetaClass mmc = anyObject.Environment.GetSystemObject(UBIK.Kernel.SystemObjects.METACLASS); // replace anyObject with a UBIK object at hand
+** UBIK.Kernel.MetaMetaClass mmc = anyObject.Environment.GetSystemMetaClass(UBIK.Kernel.SystemObjects.METACLASS); // replace anyObject with a UBIK object at hand
 ** Then assign ''mmc'' to the right target type of the relation:
 ** Relationship relation = anyObject.Environment.UBIKDataFactory().Relation(relationUid);
@@ Line 134: / Line 134: @@
 ** RelationData rd = userGroup.GetRelationDataObject(rightsRelation, this.'''MetaClass''');
-[[Category:How-To|Configure Users]]
-[[Category:Login management|Configure Users]]
 ==== Controlling the visibility and editability of properties ====

@@ Line 124: / Line 124: @@
 If you want to control the rights not per instance individually, but for all instances of a meta class at once, the following adaptions are required:
 * The ''TARGETTYPERIGHT'' of the rights relation must be MetaMetaClass, because this is the meta class (i.e., the type) of meta classes (which we want to relate to user groups in this case). It's a bit tricky to get the MetaMetaClass using Studio. You'll have to do it using Whobert, fetching and assigning the MetaMetaClass with the following code:
-** UBIK.Kernel.MetaMetaClass mmc = anyObject.Environment.GetSystemObject(UBIK.Kernel.SystemObjects.METACLASS);
+** First, we'll ask the Environment for the meta meta class system object. We'll get the Environment from any (''BaseClass'') object, e.g., the parameter object for Whobert.
 ** Then assign ''mmc'' to the right target type of the relation:
 ** Relationship relation = anyObject.Environment.UBIKDataFactory().Relation(relationUid);
@@ Line 133: / Line 134: @@
 ** RelationData rd = userGroup.GetRelationDataObject(rightsRelation, this.'''MetaClass''');
 ==== Controlling the visibility and editability of properties ====

@@ Line 19: / Line 19: @@
 # Create a new instance, filling in at least the ''LOGINNAME'', the ''DOMAINNAME'' and the ''PASSWORD''.
 # Save the new instance.
 === User groups ===

@@ Line 123: / Line 123: @@
+	}
 </source>
 If you want to control the rights not per instance individually, but for all instances of a meta class at once, the following adaptions are required:
-* The ''TARGETTYPERIGHT'' of the rights relation must be MetaMetaClass, because this is the meta class (i.e., the type) of meta classes (which we want to relate to user groups in this case).
+* The ''TARGETTYPERIGHT'' of the rights relation must be MetaMetaClass, because this is the meta class (i.e., the type) of meta classes (which we want to relate to user groups in this case). It's a bit tricky to get the MetaMetaClass using Studio. You'll have to do it using Whobert, fetching and assigning the MetaMetaClass with the following code:
 * In the code snippet, instead of asking for objects and relation data for ''this'', we have to use ''this.MetaClass'':
 ** UBIKClassList<RelationalObject> userGroups = this.'''MetaClass'''.RelatesFrom(rightsRelation);

@@ Line 13: / Line 13: @@
 * ''PASSWORD'': The password
 * ''CONSUMER'': A link to the person this login is associated with (useful if there are multiple accounts per person)
 So, the steps to create a login are:
@@ Line 18: / Line 19: @@
 # Create a new instance, filling in at least the ''LOGINNAME'', the ''DOMAINNAME'' and the ''PASSWORD''.
 # Save the new instance.
 === User groups ===

@@ Line 65: / Line 65: @@
 Here's an exemplary code snippet:
 <source lang="csharp">
 	public override IEnumerable<UBIK.Service.DTO.V240.GroupRight> CustomGroupRights(IEnumerable<UBIK.Service.DTO.V240.GroupRight> defaultRights)
@@ Line 117: / Line 119: @@
+	}
 </source>
 ==== Controlling the visibility and editability of properties ====