Differences

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

Link to this comparison view

Both sides previous revision Previous revision
admin_manual [2019/12/04 05:17]
patrick_heymans [6.3.5 - Editing a Template Revision] 		admin_manual [2019/12/04 05:55] (current)
patrick_heymans [6.3.5 - Editing Revisions]
Line 142: Line 142:
  
 ---- ----
-===== 6.3.5 - Editing Revisions =====+===== 6.3.5 - Editing revisions =====
  
-The following description is about the values you can fill in when creating a new revision or editing a clone or editing a revision that is in draft.+The following description is about the values you can fill in when creating or editing a revision.
  
-The revision form contains three tabs:+The revision form contains three tab pages:
  
   * Schema   * Schema
Line 152: Line 152:
   * Details   * Details
  
-=== Schema - general data ===+==== Schema ====
 This tab contains the general information of the revision. This tab contains the general information of the revision.
  
 {{:admin:admin_templates6.png?direct&400|}} {{:admin:admin_templates6.png?direct&400|}}
  
 +== Subject ==
 The **Subject** field is used in RQuest to identify the request (for instance in the My Requests view). You can use **expressions** in this field to construct a dynamic string containing text and field values.  The **Subject** field is used in RQuest to identify the request (for instance in the My Requests view). You can use **expressions** in this field to construct a dynamic string containing text and field values. 
  
Line 173: Line 174:
 {{:user:user_-_my_requests2.png?direct&600|}} {{:user:user_-_my_requests2.png?direct&600|}}
  
-On this tab you also define the properties that can be used in this revision. You can create, modify and delete properties using the buttons in the toolbar.+== Properties == 
 +On the **Schema** tab you also define the properties that can be used in this revision. Properties are used to define the individual fields of the data structure represented by the template revision. As such they can be used to capture information from the user (using a Form), but also in workflow logic. Note that you are completely free how to model this data structure. 
  
-Every property has the following fields.+You can create, modify and delete properties using the buttons in the toolbar. 
 + 
 +Every property has the following fields:
  
 {{:admin:admin_templates7.png?direct&400|}} {{:admin:admin_templates7.png?direct&400|}}
  
-| **Name** | The name of the property. | +^ Field ^ Description ^ 
-| **Display Name** | The name used on the UI for this property. | +| Name | The name of the property. | 
-| **Type** | The type of the property. Choices are: Boolean, Decimal, Double, Guid, Int32, Int64, String, Duration, Date & DateTime. | +| Display Name | The name used on the UI for this property. | 
-| **Constraints** | Specify the constraints that are valid for this property. Choices are: ReadOnly, Mandatory or Length |+| Type | The type of the property. Choices are: Boolean, Decimal, Double, Guid, Int32, Int64, String, Duration, Date and DateTime. | 
 +| Constraints | Specify the constraints that are valid for this property. See the table below for further information. | 
 + 
 +== Constraints == 
 +^ Constraint ^ Description ^ 
 +| ReadOnly | Indicates that the property read-only. If the property is used in a Form, the user cannot change its value. |   
 +| Mandatory | Indicates that the property requires a value before the owning request can be submitted. | 
 +| Length | Indicates a maximum length and is typically used for String properties only. | 
 === Design - Form, Workflow & Policy === === Design - Form, Workflow & Policy ===