Main Page: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
Line 21: | Line 21: | ||
|-style="background-color:#d8f3f1" valign="top" | |-style="background-color:#d8f3f1" valign="top" | ||
| | | | ||
<blockquote style="font-size:14pt"> | <blockquote style="font-size:14pt"> | ||
'''[[ | '''[[Expressions Cookbook]] and [[LINQ to Grooper Objects]]''' | ||
</blockquote> | </blockquote> | ||
This week, we feature ''two'' articles contributed by BIS team member, Brian Godwin! These articles pertain to the wide world of '''''Expressions''''' in Grooper. Expressions are snippets of .NET code, allowing Grooper to do various things outside its "normal" parameters. This includes calculating or validating extracted Data Field values in a Data Model, applying conditional execution of a Batch Process or IP Profile, and more! | |||
Expressions take the high configuration of Grooper one step ''even'' further. However, many users don't know where to begin when it comes to writing them. Brain has collected some common examples into our [[Expressions Cookbook]] article. But we're not stopping there! This article will serve as a central location for anyone to add expression examples as well. | |||
In version 2.9 we increased our expressions functionality further with LINQ (Language Integrated Query) integration. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, LINQ nets the same result while being more concise, readable, and overall, more user-friendly. | |||
For more information on LINQ, visit the full article [[LINQ to Grooper Objects|here]] | |||
For more information on | |||
| | | | ||
You can talk to us! | |||
Do you have an idea for an article? Have you noticed something missing from one already in the wiki? Do you have other comments or feedback about the wiki? | |||
If so, check out the [https://xchange.grooper.com/categories/documentation-requests Documentation Requests] section of Grooper x Change. This is your way to communicate with our documentation team. Please, let us know how we can continue to improve our wiki. | |||
|} | |} | ||
Revision as of 09:37, 3 August 2020
Getting Started | |||
Grooper is a software application that helps organizations innovate workflows by integrating difficult data. Grooper empowers rapid innovation for organizations processing and integrating large quantities of difficult data. Created by a team of courageous developers frustrated by limitations in existing solutions, Grooper is an intelligent document and digital data integration platform. Grooper combines patented and sophisticated image processing, capture technology, machine learning, and natural language processing. Grooper – intelligent document processing; limitless, template-free data integration. |
Getting Started | ||
Install and Setup | |||
2.80 Reference Documentation |
Featured Articles | Did you know? |
This week, we feature two articles contributed by BIS team member, Brian Godwin! These articles pertain to the wide world of Expressions in Grooper. Expressions are snippets of .NET code, allowing Grooper to do various things outside its "normal" parameters. This includes calculating or validating extracted Data Field values in a Data Model, applying conditional execution of a Batch Process or IP Profile, and more! Expressions take the high configuration of Grooper one step even further. However, many users don't know where to begin when it comes to writing them. Brain has collected some common examples into our Expressions Cookbook article. But we're not stopping there! This article will serve as a central location for anyone to add expression examples as well. In version 2.9 we increased our expressions functionality further with LINQ (Language Integrated Query) integration. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, LINQ nets the same result while being more concise, readable, and overall, more user-friendly. For more information on LINQ, visit the full article here |
You can talk to us! Do you have an idea for an article? Have you noticed something missing from one already in the wiki? Do you have other comments or feedback about the wiki? If so, check out the Documentation Requests section of Grooper x Change. This is your way to communicate with our documentation team. Please, let us know how we can continue to improve our wiki. |
New in 2.9 | Featured Use Case | ||||||||||||||||||||||||||||||||||||
|
Discover how they:
|
Other Resources | |||
|