This is related to using the Form Processor for Vendor invoice processing - automatically. Currently the Form Processor in AI Builder detects the lines sections (mostly) and we have managed to get it working with some degree of success. The issue we run into is if the AI detects a maximum of three pages, three tables are identified as Table0, Table0_2 and Table0_3 for the three line sections on the three pages. In the Flow when we read this information we have to read each table independently (three duplicate loops configured for each table), meaning the flow is limited to what it has been written for. If an invoice for four pages is then received the flow is only able to read and process the first three pages, ignoring the additional page. We have been informed that this is the current behaviour of the solution. Possible suggested changes to allow for: 1. During the AI Builder model creation, allow us to define the table range manually as well (like for the fields). We have seen in some cases that the AI cannot identify the table ranges correctly due to the layout the vendor used on the invoice - usually overlapping information confusing AI. 2. Also in the AI Builder model creation, allow us to define each line break in the table as well. Similar to above the format of the invoice doesn't allow for correct identification of each line. 3. Allow for the table name to be set in the Builder so that multiple tables can be set to the same name. That is, page 1, 2 and 3 line sections could have the same table, meaning that the flow can be set to read all three in one section. 4. Train the AI Builder that if the lines sections occur three times and are all defined to be the same table name, that if 4, or more start coming through, the assumption will then be that they will be part of the same table name. Contact me if you want copies of the documents we are trying to load.
... View more