You are viewing limited content. For full access, please sign in.

Question

Question

Within self-hosted, is there any way to automate when Smart Fields actually run

asked on November 12

Excited to get Smart Fields going in my environment but immediately have concerns about running it. These cannot be triggered by Workflow. And "Enable automatic extraction" is a repository-wide setting.

I thought individual templates would at least have the ability to enable/disable Smart Fields functionality, but so far as I can tell there are no options for that.

Am I missing something? I fear they are going to run a lot when I don't want them to, and in this case my concern is not about processing overhead but because I have to pay per extraction.

One early example I have concerns with is some quarterly tax statements that I will be dealing with.

  1. The Federal form has data that will be extracted via Smart Fields, including things like the company (subsidiary) information, a couple of key fields like employee count, and the year and quarter for the form.
  2. There are supporting documents that will not have data automatically extracted. I have a separate template for them, however, there are some shared fields including:
    1. Company name
    2. Year
    3. Quarter

 

It appears that if I want to automatically extract data from the Federal forms, the supporting documents will also be sent through the Smart Fields logic even though I don't want them to, they have a different template, and there is no reason for it.

Is this really the case? Is there any way to control when it runs other than manually clicking the Extract Values option? (Side note: if doing manually I can't even do it in bulk. Multi-selecting documents in the folder browser hides the Extract Values option.)

1 0

Replies

replied on November 13

You are correct, right now the "Auto-extract" option is a shared property across templates. This has the benefit of being configurable for multiple templates at once, but the side-effect of making all templates "smart" even if you don't want them to be. You could create a new template whose sole purpose is to do the extraction within workflow or forms and then set the correct template and copy the field values from the smart template to the correct template.

1 0
replied on November 17

Pieter - One thing I do want to clarify that I'm not sure if you missed, you can trigger these through workflow and they do handle in bulk. Anytime you set a template on an entry with fields available to extract, it will automatically extract it on the Server-side. So, yes, that means that it will trigger on the field regardless of which template it's on (as you note), but it also provides the benefit that just setting the template in workflow or in a bulk operation will also extract the fields. Yes, the specific button is there because that represents a more manual one-by-one approach with user interaction, but bulk actions will happen on assignment as well. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.