Difference between revisions of "Module Interventions"
m (Clarified difference between life cycle and signature status) |
|||
| (18 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <!-- BEGIN origin interlang links --> | ||
| + | <!-- You can edit this section but do NOT remove these comments | ||
| + | Links below will be automatically replicated on translated pages by PolyglotBot --> | ||
| + | [[fr:Module_Fiches_d'interventions]] | ||
| + | [[es:Módulo_Fichas_de_intervención]] | ||
| + | [[pt:Módulo_Intervenções]] | ||
| + | <!-- END interlang links --> | ||
| + | |||
[[Category:Intervention]] | [[Category:Intervention]] | ||
{{TemplateDocUser}} | {{TemplateDocUser}} | ||
| Line 8: | Line 16: | ||
userdoc=This page|}} | userdoc=This page|}} | ||
| − | = Introduction = | + | =Introduction= |
| − | + | Interventions are a form for service / maintenance orders. | |
| − | = Installation = | + | =Installation= |
{{NoInstallModuleEn}} | {{NoInstallModuleEn}} | ||
| − | = Configuration = | + | =Configuration= |
{{ActivationModuleEn}} | {{ActivationModuleEn}} | ||
| − | = Life cycle / | + | =Usage / Life cycle= |
| − | + | ||
| + | ==Default setup== | ||
| + | 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)'' | ||
| + | <pre> | ||
| + | Draft (0) --------> Validated (1) ------> Closed - Done (3) | ||
| + | \ / \ / | ||
| + | \----------<--------/ \----------<-------/ | ||
| + | \ | ||
| + | \------> Convert into a recurring intervention | ||
| + | </pre> | ||
| + | |||
| + | ==With option FICHINTER_CLASSIFY_BILLED== | ||
| + | If the hidden option FICHINTER_CLASSIFY_BILLED is defined, a step Billed is introduced. | ||
| + | |||
| + | <pre> | ||
| + | Draft (0) -----> Validated (1) ----> Billed (2) ----> Closed - Done (3) | ||
| + | \ / | ||
| + | \----------<------/ | ||
| + | </pre> | ||
| + | |||
| + | 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. | |
| − | |||
Latest revision as of 12:51, 19 August 2024
| Interventions | |
|---|---|
| Numero/ID of module | 70 |
| User doc. of module | This page |
| Developer doc. of module | Module Interventions (developer) |
Introduction
Interventions are a form for service / maintenance orders.
Installation
This module is included with the Dolibarr distribution, so there is no need to install it.
Configuration
To use this module, you must first enable it using an administrator account, via the menu option "Home - Setup - Modules".
Choose the tab where the module is listed. Then click on "Activate".
The module is now activated.
If a cog icon appears 
on module thumb or at end of the line of the module, click on it to access the setup page specific to the module.
Usage / Life cycle
Default setup
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)
Draft (0) --------> Validated (1) ------> Closed - Done (3)
\ / \ /
\----------<--------/ \----------<-------/
\
\------> Convert into a recurring intervention
With option FICHINTER_CLASSIFY_BILLED
If the hidden option FICHINTER_CLASSIFY_BILLED is defined, a step Billed is introduced.
Draft (0) -----> Validated (1) ----> Billed (2) ----> Closed - Done (3)
\ /
\----------<------/
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) :
| 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 FICHINTER_MODIFY action trigger with added context information, for automatic events and email notifications.