Changes

m
Clarified difference between life cycle and signature status
Line 25: Line 25:  
{{ActivationModuleEn}}
 
{{ActivationModuleEn}}
   −
= Usage / Life cycle=
+
=Usage / Life cycle=
   −
== Default setup ==
+
==Default setup==
 
When the module is enabled, it is possible to create intervention files.  
 
When the module is enabled, it is possible to create intervention files.  
 +
 +
When an intervention is validated or closed, it is possible to add a signature on it.
    
''The workflow of an intervention is the following (The number between parenthesis is the technical code of the status)''
 
''The workflow of an intervention is the following (The number between parenthesis is the technical code of the status)''
Line 39: Line 41:  
</pre>
 
</pre>
   −
== With option FICHINTER_CLASSIFY_BILLED ==
+
==With option FICHINTER_CLASSIFY_BILLED==
 
If the hidden option FICHINTER_CLASSIFY_BILLED is defined, a step Billed is introduced.
 
If the hidden option FICHINTER_CLASSIFY_BILLED is defined, a step Billed is introduced.
   Line 49: Line 51:     
Warning, this status/option will be removed. It must  be replaced with a property "billed" that can be defined whatever is status "Validated" or "Done".
 
Warning, this status/option will be removed. It must  be replaced with a property "billed" that can be defined whatever is status "Validated" or "Done".
 +
 +
==Signature status (Dolibarr v21 alpha)==
 +
Native signature statuses are available with Dolibarr v21 (currently in alpha testing) :
 +
{| class="wikitable"
 +
!Status label
 +
!Status code
 +
|-
 +
|Not signed
 +
|0
 +
|-
 +
|Signed internally
 +
|1
 +
|-
 +
|Signed by third party
 +
|2
 +
|-
 +
|Signed by third party online
 +
|3
 +
|-
 +
|Signed by all parties
 +
|9
 +
|}
 +
Signature status can be set once an intervention is validated. They are independent of life cycle statuses. Default signature status is "Not signed".
 +
 +
Native online signature by a public user (third party) will automatically set the signed status to "Signed by third party".
 +
 +
Signature status makes use of <code>FICHINTER_MODIFY</code> action trigger with added context information, for automatic events and email notifications.
6

edits