From 5effb7111c7fe1e79a4a3631cf41f6486d470a92 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9dric=20Bonhomme?= Date: Wed, 14 Mar 2018 09:12:10 +0100 Subject: [PATCH] Updated feature custom templates (markdown) --- feature-custom-templates.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/feature-custom-templates.md b/feature-custom-templates.md index 450f487..cc15385 100644 --- a/feature-custom-templates.md +++ b/feature-custom-templates.md @@ -7,12 +7,13 @@ The default behavior must be to use the [templates bundled with MONARC](https:// * the administrator of a front office won't be able to delete templates provided by the back office (or the default templates bundled with MONARC); * the administrator of a front office will be able to upload custom templates directly on the front office; * to go further it should also be considered to allow several templates per languages per category of deliverable. This do not add to much complexity on the back end (models) of MONARC. But the user interface to manage the templates in the front office should stay usable and friendly; +* by default maximum 3 templates per category (without the defaults templates); * custom templates will be available for the whole front office; ## Major changes required -* update the models (cli database); +* update the models and controllers (zm-client); * add a view in the front office for the management of templates (.docx): * ideally: ng-backoffice (deliveries_models.kb_mgmt.html) -> ng-anr (with some tests if in BO/FO) * almost the same page than the page actually used in the back office but