User Tools

Site Tools


Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:section_handling

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:software:tim:section_handling [2014/07/08 08:58]
melanie.yesilcay
en:software:tim:section_handling [2021/07/01 09:52] (current)
Line 13: Line 13:
  
 The part which should be affected by the Section Handling will be enclosed for example with **DIV** in the smartform, and therefore marks a completed part. \\ The part which should be affected by the Section Handling will be enclosed for example with **DIV** in the smartform, and therefore marks a completed part. \\
-The **DIV** should be given necessarily the attribute class="​section"​. The ID of **DIV** can be chosen optional. \\+The **DIV** should be given necessarily the attribute class="​section"​.An element which has the attribute class = "​section",​ can not have any other classes. The ID of **DIV** can be chosen optional. \\
 Two DIV-areas are seen in the following example: ​ Two DIV-areas are seen in the following example: ​
   * DIV with the ID="​section1",​ contains: ​   * DIV with the ID="​section1",​ contains: ​
Line 34: Line 34:
 </​code>​ </​code>​
  
->> If the Section is inside a table (<​table>​),​ a tBody should be used instead of a DIV, for defining the Section.+>> If the Section is inside a table (<​table>​),​ a tBody(tr,​td) ​should be used instead of a DIV, for defining the Section.
  
 ==== Section Handling Parameter ==== ==== Section Handling Parameter ====
  
-The parameters for the Section Handling, with which the rights are assigned, are defined in [[software:signavioSignavio]] for the process : +The parameters for the Section Handling, with which the rights are assigned, are defined in [[en:software:igrafx_documentationiGrafx]] for the process : 
  
-{{ :​en:​software:​tim:​attributes.jpg?200 |}}+{{ :​en:​software:​tim:​section_definition.png?500 |}}
  
 ==== Section Handling Parameter general ==== ==== Section Handling Parameter general ====
Line 69: Line 69:
 ^ Target group      ^ Notation ​      ^ ^ Target group      ^ Notation ​      ^
 | individual user    | "​user(username)" ​  | | individual user    | "​user(username)" ​  |
-| Swimlanes ​   | "​swimlane(Swimlanename)" | +| Swimlanes ​   | "​swimlane(swimlanename)" | 
-| Group    | "​group(Gruppenname)" ​    |+| Group    | "​group(groupname)" ​    |
 | Wildcard (for no user) | ""​ | | Wildcard (for no user) | ""​ |
-|Wildcard (no restriction) | "​*"​|+|Wildcard (for all users) | "​*"​|
 |Negation(this user can not...) | "! user(…)"​| |Negation(this user can not...) | "! user(…)"​|
  
-Multiple selections can be realized by semicolons, e.g.: "​group(Sales);​group(Controlling);​user(Max.Mustermann)"+Multiple selections can be realized by semicolons, e.g.: "​group(Sales);​group(Controlling);​user(john.doe)"
 ====Locking==== ====Locking====
  
Line 186: Line 186:
 The first example, where only the second section is visible, shall be extended now, that the restriction only applies if the progress of the process is at a particular node. The first example, where only the second section is visible, shall be extended now, that the restriction only applies if the progress of the process is at a particular node.
 This will be illustrated by the following process:\\ This will be illustrated by the following process:\\
-{{ software:​tim:​prozess.jpg?550 }} +{{ en:software:​tim:​section_task.png?550 }} 
-The desired goal is, that as long as the process is at node only the user TIM is allowed to see the upper part of the smartform. Once the process is at node everybody is allowed to see the upper part but not to edit. Therefore for every node section Parameter must be specified. The parameters for achieving the goal are the following:+The desired goal is, that as long as the process is at node Sales only the user TIM is allowed to see the upper part of the smartform. Once the process is at node Controlling ​everybody is allowed to see the upper part but not to edit. Therefore for every node section Parameter must be specified. The parameters for achieving the goal are the following:
 <code XML> <code XML>
 <​section-node-mapping>​ <​section-node-mapping>​
-  <​node-mapping name="A">+  <​node-mapping name="Sales">
     <section name="​section1">​     <section name="​section1">​
       <read assignment="​user(TIM)"/>​       <read assignment="​user(TIM)"/>​
Line 200: Line 200:
     </​section>​     </​section>​
   </​node-mapping>​   </​node-mapping>​
-    <​node-mapping name="B">+    <​node-mapping name="Controlling">
     <section name="​section1">​     <section name="​section1">​
       <read assignment="​*"/>​       <read assignment="​*"/>​
Line 230: Line 230:
 \\ \\
 If I can see the Section in general, I may even search for it and vice versa. If I can see the Section in general, I may even search for it and vice versa.
- 
en/software/tim/section_handling.1404802712.txt.gz · Last modified: 2021/07/01 09:55 (external edit)