User arguments for Proof of Delivery Digitization
This table shows the required user arguments in RPA Assistant or RPA Management:
| User argument | Description | Data type | Sample value |
|---|---|---|---|
| accountingEntity | The accounting entity of M3. Concatenates the company and division values:
company_division |
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 | Specify one of these values to define the recipient of the ION Notification after each RPA process completes:
|
string | USER
or GROUP |
| userIdentifier | If you set the distributionType to USER, you must specify the value in Security User GUID for the user. You can find this value in . This user receives an ION Notification in the M3 Inbox when the RPA process is finished.
If you set the distributionType to GROUP, you must specify the name of the user group created in . Users connected to this group receive an ION Notification in the M3 Inbox when the RPA process is finished.
Note: You must have the UserAdmin role to access this information.
|
string |
7 11111111-ae8d-4d9c-955a-02fab58f5468 M3ProofOfDeliveryDigitization |
| logLevel | When the RPA process runs, it creates one log file per day in the Logs folder inside the configuration folder. The file is named JobsResults[yyyymmdd].txt.
Types of logging:
|
string | INFO
DEBUG NONE |
| msgBoxLevel | When the RPA process runs, it can trigger pop-up messages to inform about the process and any errors encountered. This feature must not be enabled during unattended mode, as it causes the process to stop after the first pop-up message is triggered.
Types of messages:
|
string | NONE
INFO DEBUG |