User parameters for Bill of Lading Digitization

This table shows the required arguments to run this solution:

User argument Description Data type Sample value
configurationFolder This parameter defines the internal working path where all scanned documents are placed along with the Logs, Success, and Failure Folders.

Ensure that you have access to the computer drive or server, and have no restrictions to create files and directories.

 string C:\...\ M3BillOfLading (local)

\\NetworkAddress\..\M3BillOfLading (remote)
accountingEntity This parameter is an accounting entity of M3.

Concatenates the company and division values "company_division"

 string 100_AAA
distributionType This parameter determines the recipient of an ION Notification generated after the RPA process execution is complete. Set this to USER for a specific user to receive the notification or to GROUP for a user group to receive the notification. string USER or GROUP
userIdentifier If the distributionType is set to USER, the value in Security User GUID for the user must be configured. The value is found in OS > Security > Manage > Users. This user receives an ION Notification in the M3 Inbox when the RPA process execution is finished.

If distributionType is set to GROUP, the name of the user group created in OS > Security > Manage > Groups must be configured. Users connected to this group receives an ION Notification in M3 Inbox when the RPA process is finished.

Note: UserAdmin role is required to access this information.
string

GUID or Group

xxxx-xxxxx-xxxxx/AdminGroup
logLevel When RPA process is executed, it creates one log file per day named as JobsResults[yyyymmdd].txt in a Logs folder inside configurationFolder.
Types of logging:
  • INFO: This log is also considered as empty or space which is the default value. It logs time stamps for the process start and process end, which files were processed, which delivery numbers were found and the status for each delivery, and also success and failure count. In case of errors, exception messages are also logged.
  • DEBUG: Logs technical details.
  • NONE: Results in no logging and is not recommended. Execution results can be reviewed in the log file, including success and failure count.
 string

INFO

DEBUG

NONE
msgBoxLevel When RPA process is processed, it can trigger pop-up messages to inform user about the process and eventual errors. It must not be activated in case of unattended mode execution as it will result in the process not being able to continue after the first pop-up message box is triggered.
Types of messages:
  • NONE: This message is also considered as empty or space which is the default value.
  • INFO: Triggers message boxes in process start, process end, and in the case of errors.
  • DEBUG: Triggers more messages with technical details. To avoid activating the parameter, you must set it to NONE, leave it empty or with a blank space.
 string

NONE

INFO

DEBUG