Authorization DSL - Revision history

Kraeling: corrected indentation

2019-12-02T10:32:33Z

corrected indentation

Yang: /* role */

2017-11-17T11:07:58Z

‎role

Yang: /* role */

2017-11-17T11:06:47Z

‎role

Yang: /* AuthorizationDSL */

2017-11-17T11:01:35Z

‎AuthorizationDSL

Yang: /* role */

2017-11-17T10:56:44Z

‎role

Yang: /* role */

2017-11-17T10:55:40Z

‎role

Yang: /* role */

2017-11-17T10:53:40Z

‎role

Yang: /* role */

2017-11-17T10:53:05Z

‎role

Yang: /* role */

2017-11-17T10:48:38Z

‎role

Yang: /* ENTITY */

2017-11-17T10:17:23Z

‎ENTITY

@@ Line 78: / Line 78: @@
 role Sales {
    ENTITY Mproduct_class ANY
-	ENTITY  Memployee ANY {. . .}
+  ENTITY  Memployee ANY {. . .}
-	PROCESS ProductMaintenance {. . .}
+  PROCESS ProductMaintenance {. . .}
 . . .
+}

@@ Line 131: / Line 131: @@
 * Bean attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
 <syntaxhighlight lang="java">
 BEAN Address ANY {

@@ Line 105: / Line 105: @@
 <syntaxhighlight lang="java">
 ENTITY Mproduct_class ANY
+</syntaxhighlight>
 ENTITY Memployee ANY{
 	attribute first_name INVISIBLE
@@ Line 111: / Line 113: @@
+}
 </syntaxhighlight>
 The following picture is a dialog of <code>ENTITY</code> '''''Memployee''''', you could see for the <code>role</code> '''''sales''''', the attribute '''''first_name''''' is not shown, only '''''full_name''''' and '''''last_name''''' is shown; the reference '''''position''''' is not editable.<br><br>[[File:AuthorizationDSL_01.png|600px]]<br><br>
@@ Line 128: / Line 131: @@
 * Bean attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
 =====DTO=====

@@ Line 19: / Line 19: @@
 * "ENTITY” - define which entity should be authorized, and how to authorize it for the roles, the entity is defined in [[Entity DSL]] model.
-* “attribute” -  define the authorization of the entity attributes for the roles.
+* "BEAN” - define which bean should be authorized, and how to authorize it for the roles, the bean is defined in [[Entity DSL]] model.
-* “relation” - define the authorization of the referenced entity for the roles.
-* “PROCESS” - define which process is startable and if the user task of this process is executable for the roles. The process is defined in BlipDSL model.
+* "DTO” - define which DTO should be authorized, and how to authorize it for the roles, the DTO is defined in [[DTO DSL]] model.
-* “TASK” - define which user task is executable for the roles.
+* “attribute” -  define the authorization of the entity/bean/DTO attributes for the roles.
 ===Syntax===

← Older revision		Revision as of 10:56, 17 November 2017
Line 66:		Line 66:
	\| PROCESS <blip name>{ ... }		\| PROCESS <blip name>{ ... }
	...		...
−	}	+	}
	</syntaxhighlight>		</syntaxhighlight>

@@ Line 87: / Line 87: @@
 <syntaxhighlight lang="java">
 ENTITY <entity name> RoleEnum [{
-attribute <entityAttribute name> INVISIBLE|DISABLED|NONEDITABLE
+	attribute <entityAttribute name> INVISIBLE|DISABLED|NONEDITABLE
-relation <entityReference name> INVISIBLE|DISABLED|NONEDITABLE
+	relation <entityReference name> INVISIBLE|DISABLED|NONEDITABLE
-...
+	...
 }]
 </syntaxhighlight>
-* RoleEnum is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the whole entity. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
+* <code>RoleEnum</code> is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the whole entity. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
 * Entity attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
@@ Line 102: / Line 102: @@
 ENTITY Memployee ANY{
-		attribute first_name INVISIBLE
+	attribute first_name INVISIBLE
-		relation position NONEDITABLE
+	relation position NONEDITABLE
+}
 </syntaxhighlight>
@@ Line 114: / Line 114: @@
 <syntaxhighlight lang="java">
 BEAN <bean name> RoleEnum [{
-attribute <beanAttribute name> INVISIBLE|DISABLED|NONEDITABLE
+	attribute <beanAttribute name> INVISIBLE|DISABLED|NONEDITABLE
-relation <beanReference name> INVISIBLE|DISABLED|NONEDITABLE
+	relation <beanReference name> INVISIBLE|DISABLED|NONEDITABLE
-...
+	...
 }]
 </syntaxhighlight>
-* RoleEnum is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the bean. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
+* <code>RoleEnum</code> is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the bean. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
 * Bean attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
@@ Line 130: / Line 130: @@
 <syntaxhighlight lang="java">
 DTO <dto name> RoleEnum [{
-attribute <dtoAttribute name> INVISIBLE|DISABLED|NONEDITABLE
+	attribute <dtoAttribute name> INVISIBLE|DISABLED|NONEDITABLE
-relation <dtoReference name> INVISIBLE|DISABLED|NONEDITABLE
+	relation <dtoReference name> INVISIBLE|DISABLED|NONEDITABLE
-...
+	...
 }]
 </syntaxhighlight>
-* RoleEnum is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the DTO. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
+* <code>RoleEnum</code> is including ANY, CREATABLE, READABLE, UPDATABLE and DELETABLE. It is defined for the DTO. any means allowed all. Otherwise, only the operation which is listed is allowed, they are CREATABLE, READABLE, UPDATABLE and DELETABLE; it can be one or more operations listed at the same time.
 * DTO attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
@@ Line 146: / Line 146: @@
 <syntaxhighlight lang="java">
 PROCESS <blip name>{
-[is STARTABLE]
+	[is STARTABLE]
-[all usertasks TASKABLE]
+	[all usertasks TASKABLE]
-TASK <blipTask name|Task name> TASKABLE
+	TASK <blipTask name|Task name> TASKABLE
-...
+	...
+}
 </syntaxhighlight>

@@ Line 82: / Line 82: @@
 =====ENTITY=====
 You can define the authorization rule for the whole entity or for one or more attribute/reference of this entity.
@@ Line 108: / Line 107: @@
 </syntaxhighlight>
 The following picture is a dialog of <code>ENTITY</code> '''''Memployee''''', you could see for the <code>role</code> '''''sales''''', the attribute '''''first_name''''' is not shown, only '''''full_name''''' and '''''last_name''''' is shown; the reference '''''position''''' is not editable.<br><br>[[File:AuthorizationDSL_01.png|600px]]<br><br>
 =====BEAN=====
 You can define the authorization rule for the bean or for one or more attribute/reference of this bean.
@@ Line 126: / Line 123: @@
 * Bean attribute and reference could be authorized as INVISIBLE, DISABLED and NONEDITABLE. Only the operation which is listed is allowed, it can be one or more operations listed at the same time.
 =====DTO=====
 You can define the authorization rule for the DTO or for one or more attribute/reference of this DTO.

@@ Line 58: / Line 58: @@
 <syntaxhighlight lang="java">
 role <role name> {
-  ENTITY <entity name> ... [{ ... }]
+    ENTITY <entity name> ... [{ ... }]
 	  ...
-   PROCESS <blip name>{ ... }
+   | BEAN <bean name> ... [{ ... }]
    ...
+     }
@@ Line 68: / Line 72: @@
 <syntaxhighlight lang="java">
 role Sales {
-   ENTITY Mproduct_class any
+   ENTITY Mproduct_class ANY
-	ENTITY  Memployee any {. . .}
+	ENTITY  Memployee ANY {. . .}
 	PROCESS ProductMaintenance {. . .}
 . . .