Capture Profile acting like gum on my shoe

asked on May 2

We are setting up a series of capture profiles for Bills of Lading, with eight individual profiles organized into a group. One profile in particular keeps getting applied to all documents, even after we have removed the profile from the group.

It also returns true for this one profile even then we use it on documents that are not remotely similar to BOLs. Here is the token assignment:

And then the template assignment:

The workflow monitor shows the detail:

And the profile is not even in the group:

It is acting like a default that says, if I can't ID a certain document, I'll assign it to this profile, even if the profile is not even in the group. Gum on my show, and it won't go away. Any thoughts?

0 0

replied on May 2

I'm not aware of any issues like what you're describing, however, it is easy to miss a publishing step (which would result in the Workflow running an older version of the Capture Profile Group and not having your changes).

After updating the Capture Profile Group, please make sure you:
1) Publish the Capture Profile Group
2) Open the workflow in the Workflow Designer (or refresh the page if it's already open) and edit the Run Capture Profile activity to use the latest major version of the Capture Profile Group
3) Publish the workflow

Regarding

It also returns true for this one profile even then we use it on documents that are not remotely similar to BOLs.

For more details on how Capture Profile Groups determine which profile to run, see my explanation in https://answers.laserfiche.com/questions/218846/Feature-Request-Add-RegEx-qualifiers-to-the-data-zone-in-addition-to-the-anchor-zone.

2 0

Question

Question

Capture Profile acting like gum on my shoe

Replies

Sign in to reply to this post.