Process flow for Pickup/Delivery Receipt Digitization

Before running the Pickup/Delivery Receipt digitization process, ensure that:

• The signed and scanned delivery note documents are in the PODFolder directory.
• The user arguments are filled in correctly.
• If the RPA process is started manually from the RPA Assistant, the user who starts the process must have Read and Modify access to the PODFolder.
• If the RPA process is started automatically by scheduling in unattended mode, the user configured to run the RPA process on the remote server must have Read and Modify access to the PODFolder without authenticating. If a local user on the remote server is used, a local folder on that server must be configured. This folder can also be shared, and the tenant user can be given access to the shared folder to access and save PDF files there.
• Multiple jobs can be created in RPA Management to trigger the process in unattended mode. When configuring a job, select the remote server in the Devices field and the user who runs the RPA process in the Bots field. In the Users field, select a tenant user with access to RPA Management. This user must configure the user arguments for the process in the Processes section under Manage in RPA Management. This way, multiple jobs are created for the same RPA process with the same device and bot but with different tenant users in the Users field, each with different user arguments. This setup allows support for multiple divisions with separate PODFolder values and different schedules.
  Note: The user can run only one job at a time.

When you run the Pickup/Delivery Receipt Digitization process, RPA performs these actions:

• Verifies if the directories and log files are created in the POD folder. The directories include Failure, Logs, and Success folders.
• Verifies if there are any PDF files in the PODFolder directory and starts processing the PDF files individually. Signed and scanned Delivery Note documents must be placed in this folder.
• Analyzes and extracts the order numbers with the page numbers from the files.
• Verifies and sends the documents to IDM based on the number of order numbers available in the document.

  If the PDF file contains a single order number, the single Delivery Note document is sent to IDM. If the PDF file contains more than one order number, an individual Delivery Note document is created for each order number and is sent to IDM.

  For each Delivery Note document in IDM, the IDM Document Type field is set to Delivery Note. The Accounting Entity, Company, and Division Attributes fields in IDM are populated with the user arguments specified in the RPA Tray Assistant, for the user running the process in the attended mode. In the unattended mode, the user arguments defined for the user assigned to the RPA Job are populated.

• Moves the processed PDF file from the PODFolder to the Success folder if the process is successfully completed. Else, the documents are moved to the Failure folder.
• Rechecks if there is any PDF file remaining in the PODFolder and proceeds with the files.
• Triggers a notification to the configured user or group about the status of the flow, after all files are processed, and completes the log.
• Sends an ION notification to the configured user or users in a user group in the CSD Inbox, including the success and failure counts, after the RPA process implementation is completed. Users can view the processed documents in the Related Information context widget in the CSD application.