[CORE] - Supann life cycle - automation via Orchestrator

The goal is to have FusionDirectory tasks system, embedded within its core, ready for Orchestrator when the automatism of supann life cycle is being developed.

The following steps must be taken into consideration. (OBSOLETE) Please confer to the simple design document that can be found here : Cycle_de_vie_-development-design_document__DRAFT_.odt

Note that this document is subject to update and is definitely not in its final form

BELOW contains historical design - somecontent is obsolete - see above design document

1. A new attribute in tasks generic must best added, and the schema therefore must be modified to have the "lastExec" date present. (Done).
2. The generic task must be updated accordingly if tab supann is selected:

• The redundancy should be automatically set to daily, and the case “new members only” should be unpicked. (Done).
• The mail tab should therefore not be possible to be activated. (Done)
• A message when opening the tab supann should appear explaining this behavior. (It makes no sense to no do it as supannRessourceEtat are fix dates - daily check). (Done)

3. The tab supann Task

• ObjectClass supannTask, should make visible the behavior set in the configuration backend. Read-only. With message to change it in the configuration if required. (No schema update as noLdapSave).
• The list of members will be processed automatically, only the members having an active account with expired date as end.
• The creation of subtasks will be triggered the same way as for the mail tasks, only, maybe lesser information required. Although emails in subclass can be left as is. Still is a referenced to the user account.

4. (Plugins) FD must have an updated schema of supann-fd-conf as we need to add a new section about the behavior required in case of Account closure.

• This must include a tick box saying that we will manage this via Orchestrator
• An array of related existing supannRessourceEtat should be available and a matching with the behavior required for others supannRessourceEtat.
• An array of one-to-one match departing from AccountStatus seems the good way to perform it.

5. (Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if the above tick box of "usage of Orchestrator" is set, the plugin should not perform anything itself.
6. A documentation on all this process is required in sphinx on FD core website.