Details

    • Type: New Feature
    • Status: Open
    • Severity: Medium
    • Resolution: Unresolved
    • Affects Version/s: 4.2.0 GA (4.0.0 GA Suite Release)
    • Fix Version/s: Backlog
    • Component/s: Job Entry
    • Labels:
      None
    • PDI Sub-component:
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
    • PM Ranking:
      Low

      Description

      In many cases, it is really important to send a NAK message in case of message processing failure, instead of only working with timeouts.
      First of all, working with timeouts is not trustable. If it is too brief, a simple network slowness can make processed messages by the receiver be treated as an error.
      By creating the NAK message, it guarantees to the sender that there was an error on the sent message. Moreover, a description of the error can be added to the NAK messages, making it easier for the sender to know where is the root of the problem, easing the communication.
      Its pretty simple to implement

      ACK message:
      MSH|^~\&|||||||ACK||P|2.3.1||||||8859/1
      MSA|AA|1234|OK

      NAK messages:
      MSH|^~\&|||||||ACK||P|2.3.1||||||8859/1
      MSA|AE|1234|ERROR

      MSH|^~\&|||||||ACK||P|2.3.1||||||8859/1
      MSA|AR|1234|MESSAGE REJECTED

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                gabrielmendes Gabriel Gomes Mendes
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: