• Expanding Capacity: Strategies for Large-Scale Invoice Data Extraction

    Hello all,

    I am dealing with an issue where I want to extract specific values from 2 types of invoices and use them in a workflow in order to make specific calculations.

    At first I thought I should use Intelligent Indexing for the extraction but I had 2 issues.
    1. Intelligent indexing has a limit of how many values it can extract and I want to extract more than 25 numeric and 25 text values.
    2. I tried to use a table in order to extract all the values and bypass the limit, but I was unable to find a way to use these values later in the workflow since they are not assigned to a specific metadata field I could use.
    After these attempts I thought of using the document processing functionality. This is a static approach but I don't expect the layout of the invoices to change soon.
    The problem is that one of these two invoices is more than 100 pages and document processing cannot process documents above this number. 

    So the questions are:
    1. Is there a way to configure intelligent indexing to gather more values than the current limit?
    2. Is there a way to use the values from the table in the workflow in order to make calculations? For example, can I store them in variable? 50 values->50 variables.
    3. Can I configure the limit of the 100 pages for the document processing?
    4. If none of the above is configurable, how should I proceed with my case?
    Of course, if there are better approaches to this problem, please add them as well.

    I am working on a cloud environment.
     
  • Conditional Visibility of Properties Based on Other Property's Selection

    Hi everyone,

    I'm working on a project and came across a situation where I need some guidance. In our system, we have various metadata properties associated with items, one of which is a "Supplier" property. This property can take values from a predefined list of suppliers we work with.

    Here's my question: Is it possible to dynamically show or hide additional metadata properties based on the supplier selected? For instance, if Supplier A is selected, certain properties become visible for entry or display, whereas if Supplier B is chosen, a different set of properties becomes relevant and should be shown instead.

    Has anyone implemented something similar in their projects? If so, could you share how you approached this requirement? Any insights or suggestions on how to achieve this would be greatly appreciated.

    Thank you in advance for your help and advice!