[Orchestrator] - Some attributes could be fetched by orchestrator directly instead of being stored within FD Ldap - avoiding potential duplication
[Orchestrator] - Some attributes could be fetched by orchestrator directly instead of being stored within FD Ldap - avoiding potential duplication
For example, tasks extractor, conserves a multi-evaluated list of emails extracted from members. Orchestrator should only take the members in order to get the emails.
This is to be evaluated, analysed properly to see any potential impact on the creation and workflow of subtasks.