31,026
edits
Module Interventions (developer): Difference between revisions
m
→Feature
PolyglotBot (talk | contribs) m (Import interlang links (links to translated versions of this page in other languages) from Multi Language Manager table.) |
m (→Feature) Tag: 2017 source edit |
||
| Line 19: | Line 19: | ||
It's goal is principally to follow such activities. | It's goal is principally to follow such activities. | ||
In a future version, you should be able to transform interventions cards into invoices. | In a future version, you should be able to transform interventions cards into invoices. | ||
= Usage = | |||
== Default setup == | |||
When the module is enabled, it is possible to create intervention files. The workflow of an intervention is the following: | |||
<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". | |||
= Entity Intervention = | = Entity Intervention = | ||