The Plan (was Project) is the top level container for all the models. It comes with a default kanban view, the user is able to manage the details of each Plan. Following and overview of the major characteristics:
- general details (title, plan code, partners, plan host, plan actuator, plan handler, total recipients number, project max duration(months))
- activities details summary, like a list of Courses
- deadlines dates with Alerts calculated with the Call rules
- fund and Call assignment
- economic details (budgets, down-payments, etc)
- cutom file Attachments
- phases of execution (with a Back button to possibly revert a Plan phase):
- draft: the plan is still to be send to evaluation, submission date field is visibile and fillable;
- submitted: "submission date" field must have a valid date to pass into this phase, now the start date field is now visible and fillable;
- active: "start date" field must have a valid date to pass into this phase, the complete date field is now visible and fillable;
- completed: "complete date" field must have a valid date to pass into this phase, the "audit date" field is now visible and fillable;
- accounted: "accounted date" field must have a valid date to pass into this phase, the "closed date" field is now visible and fillable;
- closed: "closed date" field must have a valid date to pass into this phase, the plan is officially closed and no more editable in this phase.
Current tasks (always on update, for history follow the comments)
The Plan (was Project) is the top level container for all the models. It comes with a default
kanbanview, the user is able to manage the details of each Plan. Following and overview of the major characteristics:Current tasks (always on update, for history follow the comments)
plan_code. If yes, append to theplan_codevalue an increment like "(1)"