IBM WFSS Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

Regarding 40873 311 758 - Length check in MER

As discussed with Gabi von Carlowitz, I opened this RFE. It is regarding the length checking functionality which is missing in the MER application to avoid that customer entered too long message and thinking that the message is valid.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Duplicate
Component Usability
Priority Medium - Important
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Apr 09:10

    very userfull ideal as it is a non-sense to validate the message that later on will be refused and that has to be resend 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Apr 09:13

    AS business impact: a msg which is successfully validated in MER may nevertheless fail to be send to SWIFT, because it fails the length check in DNF_ILC_FIN due to the fact, that DNF_ILC_FIN considers the mandatory trailers which are to be added in block 5 when calculating the message length. as the end user think the message is validate and do not expect to have it rejected, the same check done at DNF_ILC_FIN level should be introduced in MER to avoid such a situation.