Process parameters for Attended mode
This table shows the process-level parameters that are used for Attended mode.
| Name | Date type | Value |
|---|---|---|
| Agent | boolean | True |
| aocCodeEndpoint | string | AOC_Description_Similarity_Endpoint |
| companyAIEndpoint | string | Payable_Company_identification |
| DaysToArchive | integer | 3
This parameter specifies the number of days of inactivity before a file becomes eligible for archiving. If the last modification date of a file in the ReProcess Folder is older than the current date minus the number of days that DaysToArchive defines, then the file is moved to the archive folder in the configuration folder path. |
| ERP | string | FSM |
| extractNumericFromPO | boolean | False |
| includeDueDate | boolean | True |
| localFolderNames | string | Failure|InProgress|Success|ReProcess|OtherInvoices|Logs |
| Non_US_DateFormatString | string | d/M/yy|dd/MM/yy|d/M/yyyy|dd/MM/yyyy|d-M-yy|dd-MM-yy|d-M-yyyy|dd-M-yyyy|d.M.yy|dd.MM.yy|d.M.yyyy|dd.M.yyyy|d-MMM-yyyy|dd-MMM-yyyy|d-MMM-yy|dd-MMM-yy|d MMM yyyy|dd MMM yyyy|d MMM yy|dd MMM yy|d MMMM yyyy|dd MMMM yyyy|d MMMM yy|dd MMMM yy|yyyy-MM-dd|yyyy/MM/dd|yyyy.M.d|yyyy.M.dd|yyyy.MM.dd|yyyy-M-d|dd/MM/yyyy HH:mm:ss|dd MMM, yyyy|d MMM, yyyy|d/M|dd/MM|d MMM|dd MMM|d MMMM|dd MMMM|MMM yyyy|MMMM yyyy|yyMMdd|yyyyMMdd|dd/MM/yy HH:mm|dd/MM/yyyy HH:mm|dd/MM/yyyy hh:mm:ss tt|dddd, d MMMM yyyy|ddd, d MMMM yyyy
This parameter is used for easy customization. Since an invoice can contain any date format, if a new Non-US date format appears that is not among the defined formats, the user can add the new format by placing the separator pipe (|) followed by the new date format. |
| scanLines | boolean | True |
| sendNotificationMail | boolean | True |
| tenantID | string | This value varies for each tenant. For example, https://ming.le-cqa-ionapi.cqa.inforcloudsuite.com/D820T10_AX1 |
| US_DateFormatString | string | M/d/yy|MM/dd/yy|M/d/yyyy|MM/dd/yyyy|M-d-yy|M-d-yyyy|MM-d-yy|MM-d-yyyy|M.d.yy|M.d.yyyy|MM.d.yy|MM.d.yyyy|MMM d, yyyy|MMMM d, yyyy|MMM d, yy|MMMM d, yy|MMM-dd-yyyy|MMMM-dd-yyyy|MMM-d-yyyy|MMM-dd-yy|MMM d yy|MMMM d yy|MMM dd, yy|MMMM dd, yy|M MMM yyyy|MM MMM yyyy|MMMdd,yyyy|M/d|MM/dd|MMM d|MMMM d|MMM yyyy|MMMM yyyy|yyMMdd|MMddyy|yyyyMMdd|yyyy/MM/dd|dddd, MMMM d, yyyy|ddd, MMMM d, yyyy|MMM d yyyy|MMM dd yyyy|MMMM. d, yyyy|yyyy-MMM-dd|MM/dd/yyyy HH:mm:ss|MM/dd/yyyy h:mm:ss tt|MM/dd/yyyy hh:mm:ss tt
This parameter is used for easy customization. Since an invoice can contain any date format, if a new US date format appears that is not among the defined formats, the user can add the new format by placing the separator pipe (|) followed by the new date format. |
| ValidInvoiceTypesString | string | This parameter is used for easy customization and invoice types processing.
These values are the allowed types in the standard solution: Standard Invoice|Credit Memo|Credit Note|Debit Note|Debit Memo|Debit Invoice|Statement If the user wants to add a new type, a separator-pipe (|) must be placed and followed by the invoice type document class. |
| vendorAndRemitToAIEndpoint | string | Vendor_address_similarity |
| vendorNameAIEndpoint | string | Vendor_Name_Similarity |