Docflow - Rules for Rejections/Forwards

In the Docflow process, various scenarios can lead to different states based on incoming emails or uploads:

Failed:

Business logic issues or exceptions, such as encountering a problematic PDF, can result in a failed operation.

Rejections:

• PDF with Security Restrictions:
  • Action: Automatically rejected with a notification sent to the sender.
    
    
• PDF with an Unknown Receiver Address:
  • Action: PDF with an Unknown Receiver Address (e.g., registration number in dataset reference) -Automatic rejection with notification to the sender.
    
    
• Multiple PDFs with Mixed Security Restrictions:
  • Action: Reject the one with restrictions, forward the rest, and automatically notify the rejected document.

Forwarded:

Invoices that have been forwarded to other users or departments.

Automatic Forwards:

• Single PDF in Email:
  Action: Forward one package ID to OCR.

•  
• Multiple PDFs in Email:
  • Action: Forward several individual package IDs to OCR, handling each PDF separately.
    
    
• Single PDF with Single Attachment:
  • Action: Forward one packageID to OCR and attach the additional document to the attachment tab in Semine once processing is complete.
    
    
• Single PDF with Multiple Attachments:
  • Action: Forward one packageID to OCR and attach multiple documents to the attachment tab in Semine after processing.
     
• Multiple PDFs with Single/Multiple Attachments:
  • Action: Forward PDFs, ensuring attachments are picked up in the inbound inbox.
    
    
• No PDFs, but Several Attachments:
  • Action: Directly sent to Docflow for the user to add as an attachment to the invoice.