Enhance/offer creation validations

developer/04. Apps/02. App Release Process/App Release Process.md

@@ -646,13 +646,21 @@ Description
 <br>
 <br>
 
-###### #2 Submit App for Marketrelease
+###### #2 Submit App for Marketplace Release
 Description
 
 ```diff
 ! PUT /api/apps/appreleaseprocess/{appId}/submit
 ```
 
+Validations:
+
+* validates document upload (lead image, app image, confirmity document)
+* validates the signed agreements
+* validates if roles are uploaded
+* validates if technical user profile is configured
+* validates if privacy policy is set
+
 <br>
 <br>
 

developer/04. Apps/03. App Release Approval/04. Decline App Release.md

@@ -21,6 +21,21 @@ With the rejection the app manager will receive an notification as well as an em
 ! PUT /api/apps/{appId}/declineApp
 ```
 
+
+Details of the api logic/business logic
+
+* update app status from "IN REVIEW" to "CREATED"
+* sets document status of offer assigned documents back to "PENDING"
+* App Manager of the company will receive the notification (means, with the rejection of the app release, a notification for all the company related users with the role "App Manager" of the offer "Portal" will get created)
+  * Notification type: "SERVICE_RELEASE_REJECTION" (new notification type)
+  * Notification topic "OFFER"
+  * Notification content
+    * "ServiceName":"{add here the ServiceName from offer.name}",
+    * "OfferId":"{add here the ServiceName from offer.id}"
+    * "Message":"{decline reason}"
+  * On top of the notification, the rejection details are send via email
+
+
 <br>
 
 Details regarding the notification can get found in the notification service documentation: Notification Service

developer/05. Service(s)/02. Service Release Process/01. Service Card.md

@@ -74,7 +74,13 @@ Hints:
 * Sales Manager: uuid company user with role sales manager
 * LanguageCode: two digit language short code (e.g. en, de, jp, pt, etc.)
 * Service Type Ids: service type label (currently available: DATASPACHE_SERVICE & CONSULTING_SERVICE)
-
+
+<br>
+
+Validations:
+* title is mandatory (minimum 3 characters)
+* Service Type ID is mandatory
+
 <br>
 <br>
 

developer/05. Service(s)/02. Service Release Process/02. Service Publish Approval.md

@@ -64,15 +64,15 @@ Request body:
 Details of the api logic/business logic
 
 * update status from "IN REVIEW" to "CREATED"
-* create a notification for the service provider about the decline details
+* sets document status of offer assigned documents back to "PENDING"
 * Service Manager of the company will receive the notification (means, with the rejection of the service release, a notification for all the company related users with the role "Service Manager" of the offer "Portal" will get created)
-* Notification type: "SERVICE_RELEASE_REJECTION" (new notification type)
-* Notification topic "OFFER"
-* Notification content
-  * "ServiceName":"{add here the ServiceName from offer.name}",
-  * "OfferId":"{add here the ServiceName from offer.id}"
-  * "Message":"{decline reason}"
-* On top of the notification, the rejection details should also get send via email
+  * Notification type: "SERVICE_RELEASE_REJECTION" (new notification type)
+  * Notification topic "OFFER"
+  * Notification content
+    * "ServiceName":"{add here the ServiceName from offer.name}",
+    * "OfferId":"{add here the ServiceName from offer.id}"
+    * "Message":"{decline reason}"
+  * On top of the notification, the rejection details should also get send via email
 
 <br>
 <br>

developer/05. Service(s)/03. Service Release Approval/04. Decline Service Release.md

@@ -10,24 +10,46 @@ image
 <br>
 <br>
 
-### #1 Decline Service Release
-The decline service release function is used to reject services and sending the them back to the status "CREATED" .
+### Decline Service Release
 
-With the rejection the service manager will receive an notification as well as an email regarding the rejection and rejection details via a message field.
+```diff
+! PUT /api/service/{serviceId}/declineService
+```
 
 <br>
+Please note, a notification will get created and is documented in the notification service documentation: Notification Service
 
-```diff
-! PUT: /api/services/servicerelease/{serviceId}/decline
-```
+<br>
+
+Request body:
+<br>
+
+    {
+      "message": "string"
+    }
 
 <br>
+<br>
 
-Details regarding the notification can get found in the notification service documentation: Notification Service
+Details of the api logic/business logic
+
+* update status from "IN REVIEW" to "CREATED"
+* sets document status of offer assigned documents back to "PENDING"
+* create a notification for the service provider about the decline details
+* Service Manager of the company will receive the notification (means, with the rejection of the service release, a notification for all the company related users with the role "Service Manager" of the offer "Portal" will get created)
+* Notification type: "SERVICE_RELEASE_REJECTION" (new notification type)
+* Notification topic "OFFER"
+* Notification content
+  * "ServiceName":"{add here the ServiceName from offer.name}",
+  * "OfferId":"{add here the ServiceName from offer.id}"
+  * "Message":"{decline reason}"
+* On top of the notification, the rejection details should also get send via email
 
 <br>
 <br>
 
 ##### Email Example
 
 image to be added
+
+