User arguments for Proof of Delivery Digitization

User argument	Description	Data type	Sample value
accountingEntity	The accounting entity of M3. Concatenates the company and division values: `company`_`division`	string	880_BBB
configurationFolder	The internal working path where all scanned documents are placed along with the Logs, Success, and Failure Folders. Users can either use a folder from their own local directory or use a shared folder created by an administrator and hosted on another server. Ensure that you have access to the computer drive or server, and have no restrictions to create files and directories.	string	Local folder: C:\M3ProofOfDeliveryDigitizationScans_880BBB Shared folder: \\SEKIN01\ M3ProofOfDeliveryDigitizationScans_880BBB
OIS155MI_Y_N	Specify Y if delivery approval in OIS155 should be attempted. Specify N if delivery approval in OIS155 should not be attempted.	string	Y or N
distributionType	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: A user with the UserAdmin role is required to access this information.	string	7 11111111-ae8d-4d9c-955a-02fab58f5468 M3ProofOfDeliveryDigitization
logLevel	When the RPA process is run, it creates a log file per day named as JobsResults[yyyymmdd].txt in a Logs folder inside configurationFolder. There are different levels of logging, empty or space is the same as INFO which is the default value, it logs time stamps for the process start and process end, which files are processed, which Delivery numbers are found and the status for each delivery, also success and failure count. In case of errors, exception messages are also logged. DEBUG logs more technical details. NONE results in no logging and is not recommended. Results can be reviewed in the log file, including success and failure count.	string	INFO DEBUG NONE
msgBoxLevel	When RPA process is run, it can trigger pop-up message boxes to inform user about the process and sudden errors. In the case of unattended execution, it must not be activated as it results in the process not being able to continue after the first pop-up message box is triggered. Different levels of messaging vary, empty or space is the same as NONE which is the default value. INFO triggers message boxes in process start, process end, and in errors. DEBUG triggers more messages with technical details.	string	NONE INFO DEBUG

accountingEntity

The accounting entity of M3. Concatenates the company and division values:

company_division

string

880_BBB

configurationFolder

The internal working path where all scanned documents are placed along with the Logs, Success, and Failure Folders.

Users can either use a folder from their own local directory or use a shared folder created by an administrator and hosted on another server.

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

string

Local folder:

C:\M3ProofOfDeliveryDigitizationScans_880BBB

Shared folder:

\\SEKIN01\ M3ProofOfDeliveryDigitizationScans_880BBB

OIS155MI_Y_N

Specify Y if delivery approval in OIS155 should be attempted.

Specify N if delivery approval in OIS155 should not be attempted.

string

Y

or

N

distributionType

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: A user with the UserAdmin role is required to access this information.

string

7 11111111-ae8d-4d9c-955a-02fab58f5468

M3ProofOfDeliveryDigitization

logLevel

When the RPA process is run, it creates a log file per day named as JobsResults[yyyymmdd].txt in a Logs folder inside configurationFolder. There are different levels of logging, empty or space is the same as INFO which is the default value, it logs time stamps for the process start and process end, which files are processed, which Delivery numbers are found and the status for each delivery, also success and failure count. In case of errors, exception messages are also logged. DEBUG logs more technical details. NONE results in no logging and is not recommended. Results can be reviewed in the log file, including success and failure count.

string

INFO

DEBUG

NONE

msgBoxLevel

When RPA process is run, it can trigger pop-up message boxes to inform user about the process and sudden errors. In the case of unattended execution, it must not be activated as it results in the process not being able to continue after the first pop-up message box is triggered. Different levels of messaging vary, empty or space is the same as NONE which is the default value. INFO triggers message boxes in process start, process end, and in errors. DEBUG triggers more messages with technical details.

string

NONE

INFO

DEBUG