| [SICSR-16448] Previous Message - ELRAC 2nd Message is also regarded as First Message | |
|---|---|
| Product Line: | P&C |
| Component/s: | eMessaging |
| Affects Version/s: | SICS 4.8 |
| Fix Version/s: | SICS 4.9.3 SICS 4.9.2 SSP3 |
| Customer: | Swiss Re Zurich |
Problem:
Firstly, the UC says 'add a Less than test', whereas the mapping we have has a greater than test. We imagine the mapping is right, as this has been extensively tested, but logically it should be 'less than' – e.g.
Previous message creation date 2019-06-11
Current message creation date 2019-06-12
The first date is less than the second (and should be included). Any message with a date greater than 2019-06-12 should be excluded.
The second problem is when creation dates are equal. The mapping rules allow for 'greater than' or 'less than', but not for 'not less than' or 'not greater than' (or put another way 'greater than or equal to'). So a message with an identical creation date will be excluded whichever option is used! It's far less a problem if the time is included in creation date, but a significant one when it is.
Solution:
Documentation of tests for match on Greater Than and Less Than to be changed to Current Message greater than Previous Message, Current Message Less Than Previous Message (which is the existing functionality for datetime comparison.
Introduce similar tests for Greater Than or Equal and Less Than or Equal.
Workaround:
Root Cause:
Extent of Impact:
Impact on Existing Data
Recovery Method for Existing Data Affected