Grooper 21.00.0082 is available as of 12-12-2023! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.00.0042 is available as of 03-22-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0018 is available as of 04-15-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Options
Next Step Expression for Partner
tmartin
Posts: 82 ✭✭
We have a partner that needs a "Next Step Expression" for the following scenario:
- Data Model Field is returning a "Y" or "N" after extraction. If the data field returns "N" the item should go to a certain step in the process, if it returns "Y" is goes to a different step.
I feel like this should be fairly simple, but I do not know the syntax...
- Data Model Field is returning a "Y" or "N" after extraction. If the data field returns "N" the item should go to a certain step in the process, if it returns "Y" is goes to a different step.
I feel like this should be fairly simple, but I do not know the syntax...
0
Best Answer
-
OptionsBradley Posts: 94 ✭✭✭You can't use the Should Submit Expression on the Scan Step that Matt mentioned. The Item object in this expression property is scoped to the same level as the Scope property above it. The only Scope allowed for Scan is Batch. The expression, DirectCast(Item, BatchFolder).IndexData.Fields("The field name").Value = "N", will fail at run-time because the object at runtime is a Batch, not a BatchFolder.
If you still want to use a Should Submit Expression on Scan, use the expression: DirectCast(Item, Batch).HasFlaggedItems
If you go this route, the whole batch will be available in the Scan module. You won't be able to scope individual folders containing invalid index data.
You still need to enable Data Review to allow completion of documents with invalid data and set the Validation Expression on the example field I mentioned above.
5
Answers
Last few steps in his process:
- Data Review
- Scan
- Content Action
- Document Export
After data review he wants the docs that have a value of "N" to go to Scan then finish out though export
After Data Review he wants the docs that have a value of "Y" to go to Export
I feel like it should be something like this but not sure:
If(DirectCast(Item, BatchFolder).IndexData.Fields("The field name").Value = "N", Scan, Export)
Thoughts?
The intelliSense also breaks right before .Value
Thoughts?
Grooper can't move some documents to one step and the remainder of the documents to a different step without using Spawn Batch.
Having Scan in the middle of the a batch process isn't common. If this is meant to catch documents or pages that are missing from a document and need to exist before export, the documents with an "N" really should be spawned to a different batch process that starts with Scan.
Spawn Batch has a Filter option for Invalid Items. If the field name is called "SSN", go to the "SSN" Data Field in the Data Model. Add a Validation Expression:
SSN = "Y"
Click Save.
With the Validation Expression set, you can now use the Invalid Items filter option on Spawn Batch. If a document has the "N" value, the Index Data will be set to Invalid, which will cause Spawn Batch to move that document to the new Batch Process. Note: For Data Review, the property "Allow Completion with Invalid Documents" must be set to True, otherwise, the indexer will never be able to complete Data Review.
Product Manager
mharrison@bisok.com
Product Manager
mharrison@bisok.com
@DungVu does this make sense to you? Will spawning the "N" documents into another batch process work for you?
I think the only way to give you exactly what you need would be the Spawn batch approach.
- You can create multiple branches in a workflow within the same process(i.e.different documents going to different steps), by using "Should Submit" expressions. The problem you have , however, is that you want docs at the folder level to be sent to a "Scan" step. This is not possible because the "Scan" step can only be scoped at the batch level. This is why the expression we were testing earlier did not work.