Refactor notification service's job planner events table layout... (#748)

* Refactor notification service's job planner events table layout

* Apply review

src/docs/JobPlanner/references/JobPlannerServiceReference.adoc

@@ -207,13 +207,14 @@ An inclusion or exclusion calendar can become not retrievable if it cannot be do
 
 == Notifications
 
-The <<_glossary_job_planner,*Job Planner*>> can send notifications to users when particular events occur. The <<_glossary_notification_service,*Notification service*>> documentation can be found link:../admin/ProActiveAdminGuide.html#_notification_service[here].
+The <<_glossary_job_planner,*Job Planner*>> can send notifications to users when particular events occur. The <<_glossary_notification_service,*Notification service*>> user guide documentation is available link:../user/ProActiveUserGuide.html#_notification_service[here] and its
+configuration in the admin guide is available link:../admin/ProActiveAdminGuide.html#_notification_service[here].
 
 To start receiving notifications from the <<_glossary_job_planner,*Job Planner*>>, you must:
 
 - Configure your Job planner's <<_glossary_notification_subscription,*Subscription*>> as it is described in link:../user/ProActiveUserGuide.html#_service_subscriptions[Service subscriptions documentation] of the <<_glossary_notification_service,*Notification service*>>.
 - Inside the Job planner subscription, select from available events the ones you wish to be notified of.
-Available Job planner events with their description and example values are detailed in the table in link:../user/ProActiveUserGuide.html#_job_planner_notifications[Job Planner event types].
+Available Job planner events with their description and example values are detailed in the table link:../user/ProActiveUserGuide.html#_job_planner_notifications[Job Planner event types].
 
 == Job Planner Configuration
 

src/docs/user/references/Notification-service.adoc

@@ -353,22 +353,16 @@ INFO, WARNING, ERROR, CRITICAL. The default severity is INFO.
 [cols="2,2,2,5,5"]
 |===
 | *Type* | *Readable name* | *Severity* | *Message* | *Description*
-| `ASSOCIATION_FAILED`
-| Association failed
+.3+| `ASSOCIATION_FAILED`
+.3+| Association failed
 | CRITICAL
 | The server was unable to retrieve the resource Native_Task_Windows in the bucket basic-examples
 located \https://{HOST}/catalog/buckets/basic-examples/resources/Native_Task_Windows/raw.
 Changing the status of the association 152 of the calendar every_minute to FAILED.
 | A <<_glossary_catalog, *Catalog*>> resource is not found, the association changes to FAILED status
-| `ASSOCIATION_FAILED`
-| Association failed
-| ERROR
-| The association 52 of the workflow Variables_Propagation to the calendar every_monday had a failed execution
-, as it is configured, the association status is set to FAILED
+.2+| ERROR
+| The association 52 of the workflow Variables_Propagation to the calendar every_monday had a failed execution, as it is configured, the association status is set to FAILED
 | An association's status has been updated to FAILED due to the previous execution having an error
-| `ASSOCIATION_FAILED`
-| Association failed
-| ERROR
 | Update the association 45 of calendar every_week_day status to failed: Failed to retrieve planned calendar.
 | <<_glossary_job_planner,*Job Planner*>> could not retrieve the calendar of a Workflow-Calendar association. The association's status has been updated to FAILED.
 | `CANNOT_SUBMIT`
@@ -381,30 +375,21 @@ Changing the status of the association 152 of the calendar every_minute to FAILE
 | WARNING
 | Submission of the workflow Variable_Propagation planned at Tuesday 15 June 2021 10:35:00 CEST by association 202 of calendar every_minute is postponed because job [639] is on-going
 | A submission has been postponed because the previous execution is still under way
-| `SUBMISSION_CANCELED`
-| Submission canceled
-| WARNING
+.3+| `SUBMISSION_CANCELED`
+.3+| Submission canceled
+.3+| WARNING
 | Submission of the workflow Variable_Propagation planned at Tuesday 15 June 2021 10:41:00 CEST by association 202 of calendar every_minute is canceled because job [644] is on-going
 | A submission has been canceled because the previous execution is still under way
-| `SUBMISSION_CANCELED`
-| Submission canceled
-| WARNING
 | The workflow Variables_Propagation in the bucket basic-examples from the association 202 of calendar every_minute was not executed at Tuesday 15 June 2021 10:48:02 CEST
 | The workflow execution time is before the current time that means we missed an execution and it is not configured to postpone the execution
-| `SUBMISSION_CANCELED`
-| Submission canceled
-| WARNING
 | The workflow Variables_Propagation in the bucket basic-examples from the association 202 of calendar every_minute was not submitted 10 times, skipping execution to the next association
 | Binded to the upper notification, it informs how many execution were missed
-| `DELAYED_SUBMISSION_EXECUTING`
-| Delayed submission executing
-| INFO
+.2+| `DELAYED_SUBMISSION_EXECUTING`
+.2+| Delayed submission executing
+.2+| INFO
 | The workflow Variables_Propagation in the bucket basic-examples from the association 202 of calendar every_minute planned the Friday 11 June 2020 16:45:02 CEST
 was postponed and executed the Friday 11 June 2020 16:46:12 CEST
 | A planned workflow execution that has been postponed is now executing
-| `DELAYED_SUBMISSION_EXECUTING`
-| Delayed submission executing
-| INFO
 | <<_glossary_job_planner,*Job Planner*>> has detect that the execution of the workflow Variables_Propagation in the bucket basic-examples from the association 202 of calendar every_minute
 has been missed the Friday 11 June 2020 16:54:00 CEST. As it is configured, Job-planner will submit an execution now at Friday 11 June 2020 16:59:22 CEST
 | The workflow execution time is before the current time that means we missed an execution and it is