Skip to main content

Status "Subsequently Sent"

When an eDocument fails, the document (for example a posted sales invoice) is usually picked up again by the next process and sent there. Until now the old process still showed the eDocument as Failed. Running Repeat in the old process would then send the same document a second time.

With the process step MARK_SUBSEQ_SENT ("Mark failed eDocs of this document as subsequently sent"), mseDoc365 can mark such eDocuments with the status Subsequently Sent.

Setup​

The step is optional. Nothing changes until you add it to a process template.

  1. Open the process template that sends the documents.
  2. Add the step MARK_SUBSEQ_SENT after the SEND step. The SEND step does not have to be the last step of the template; place MARK_SUBSEQ_SENT directly after it.

If the eDocument has no finished SEND step when MARK_SUBSEQ_SENT runs (for example because SEND was skipped by a step filter), the step is skipped and nothing is marked.

What does the step change?​

The step looks for other eDocuments of the same document that have the status Failed:

Failed eDocument was sent overResult on the failed eDocument
the same sending type as the successful sendStatus changes to Subsequently Sent. A response names the process and eDocument that sent the document.
another sending type (for example Peppol instead of e-mail)Status stays Failed. A response names the process and eDocument that sent the document over the other sending type.

The eDocument that runs the step gets a response with the number of marked eDocuments.

A send over another sending type does not replace the failed one, so you decide yourself whether the failed eDocument still has to be sent.

What you see​

  • The Status column of the process card and the eDocument list shows Subsequently Sent. The line is shown in yellow, so it is easy to tell apart from a regular Completed eDocument.
  • The original error stays visible in the responses of the eDocument.
  • The process list has a new column No. of Subsequently Sent Documents. These eDocuments no longer count as failed, and a process whose remaining eDocuments are all completed or subsequently sent is shown as done.
  • Repeat only picks up eDocuments with the status Failed. Subsequently sent eDocuments are not sent again.

Existing data​

Only eDocuments that fail before a later send with MARK_SUBSEQ_SENT are marked. eDocuments that failed and were sent again before the step was set up are not changed.

Only outgoing documents are affected. Incoming documents are not sent, so nothing changes for them.