-
Story
-
Resolution: Done
-
Undefined
-
ConsoleDot CY22Q4, Notif: Feb 13 2023 Release, Notif: Feb 13 2023 Release #2, Notif: Feb 20 2023 Release, Notif: Feb 20 2023 Release #2, Notif: Feb 13 2023 Release #3, Notif: Feb 20 2023 Release #3, Notif: Feb 13 2023 Release #4, Notif: March 3 2023 Release, Notif: March 3 2023 Release #2, March 23, March 23 #2, March 23 #3, March 23 #4, 4/4/23, 4/4/23 #2, April 23 #1, April 2023, April 2023 #2, April2023, April20232
-
None
-
None
-
False
-
-
False
-
None
-
Unset
-
None
Since we added the Camel processor, processed notifications were sent to a third party server that finishes the processing in an asyncronous way - We can have ongoing process after we store the entry in the database.
These process have a mechanism to notify us when they are done and their status - but currently the notification history only has a boolean to signal the status. This value is used to tell if there was an error or if the process was successfully.
We should replace this boolean with an enum to propperly indicate the current status in the process:
- FAILED_CREATION - When a notification was triggered, but the processor didn't answered properly
- PROCESSING - When a notification was accepted by the processor
- FAILED_PROCESSING - A notification was processed and the outcome was a failure
- SUCCESS - A notification was processed and the outcome was success
A separate story/task might need to be created for the related UI work of displaying this information.
We need to have special care to store the values of this enum as strings and not as numbers.
- mentioned on