From 7c44d23f0cb25da4c7a4eb1f3f439c692a7b1244 Mon Sep 17 00:00:00 2001
From: mpostelnicu <mpostelnicu@gmail.com>
Date: Wed, 17 Jun 2020 10:35:36 +0300
Subject: [PATCH] OCMAKU-671 updated javadoc

---
 .../persistence/dao/form/ProcurementPlan.java      | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/persistence/src/main/java/org/devgateway/toolkit/persistence/dao/form/ProcurementPlan.java b/persistence/src/main/java/org/devgateway/toolkit/persistence/dao/form/ProcurementPlan.java
index 6440686ed..dcc5b2292 100644
--- a/persistence/src/main/java/org/devgateway/toolkit/persistence/dao/form/ProcurementPlan.java
+++ b/persistence/src/main/java/org/devgateway/toolkit/persistence/dao/form/ProcurementPlan.java
@@ -133,7 +133,19 @@ public String toString() {
     }
 
     /**
-     * Procurement Plan is exportable only if there is at least one approved/terminated tender process
+     * please read first OCMAKU-477 to understand why we need to export draft procurement plans.
+     * <p>
+     * the rule to determine if a procurement plan will be published is now the following (by "exportable"
+     * we mean terminated or approved):
+     * <p>
+     * if the procurement plan is exportable - it gets published
+     * if the procurement plan is draft AND it contains at least one exportable project which contains at least
+     * one tender process which is exportable
+     * <p>
+     * This has implications on the public portal pages, since draft submission of procurement plans is
+     * <p>
+     * procurement plans can be exported without file uploads
+     * procurement plans can be exported without approval dates
      *
      * @return
      */