Welcome to this EMC Support Community Ask the Expert conversation. This ATE sessionwill cover the recently released Captiva 7.1 platform. Attendees will be able to ask questions about its new capabilities for mobile capture, invoice capture, and many improvements to productivity, performance, and usability.
|Justin Bettencourt is a Product Manager in EMC’s Information Intelligence Group (IIG), managing IIG’s Captiva software suite. Throughout the years he has managed various Captiva products including InputAccel, eInput, PixTools, and ISIS. Justin has been with the Captiva group since April 1998.|
|James Robinson Is the President/CEO of PaperFree (Certified EMC Partner). He is a Certified Professional with over 20 years of experience in information capture and content management, James has experience in all areas relating to solution design, architecture, development, and deployment.|
|Kalpana Katdare is the CEO of Stellaris. She has spent more than 15 years in Software Development and Project Management in the field of application development and imaging solutions. Having earlier worked as the Project Technical Lead on several prestigious projects at Captiva Software Corporation, she established Stellaris Technologies in July 2005 with the aim of providing quality professional software services in the Document Capture domain.|
This discussion will take place on March 3 - 7. Get ready by following this page to receive updates in your activity stream or through email.
This discussion is now open for questions. We look forward to a lively and informative event.
in IndexPlus I have used FilterBatchList event handler to filter list of available batches based on certain conditions. How can this be accomplished using Captiva Desktop?
Here is the scenario why I need this:
I have two Captiva Desktop steps in capture process. First step is "Indexing" and second step is "Control". I have group of operators that can't be divided into separate groups or departments (explicit requirement from customer is that "everyone-can-do-everything").
I need to prevent user that has performed "Indexing" from performing "Control" of the same batch. Previously, with IndexPlus, I used to append "indexing" user name to batch name after indexing, and used that in "FilterBatchList" script to prevent "Indexing" user from seeing that batch in "Control" list.
How can I achieve this with Captiva Desktop?
Thanks in advance,
eInput currently supports Internet Explorer 9 only.
Current IE version is 11. This renders eInput practically useless for serious business, and pictures Captiva as almost obsolete platfrom (at least for Web scanning). When will this be addressed?
I'm not at liberty to commit to future functionality that's not on the published IIG roadmap, but I can assure you that we are well aware of this issue and hope to be able to announce positive news soon.
The challenge as you stated is with ensuring that operator #1 is not presented with the same item twice - this is typically required in a true 'double blind keying' scenario for example where field accuracy on certain fields is desired to be the highest it can be by certain customers. We have ran across this. I will be back to you here shortly with our suggestion and\or thoughts on this! Appreciate the great question!
I camevto know in 7.1 we can create a mobile app for scanning. How far do u think it is easy to develop and how captiva developers can develop knowledge on this??
many thanks for your answer. The longer e-mail that you sent me is not visible here, so I will copy it. Please see my comments in italics.
Great question - thank you! We too have ran across this 'challenge' ourselves and do have a method to suggest. In InputAccel 6.x, what EMC was trying to accomplish with the “FilterBatchlist” was to limit batch access to operators who had the permissions or limit batch access to batches that matched a certain criteria.
In Captiva 7, this is still possible but in a different manner. Instead of directly affecting the batch list (like FilterBatchList did) you now give the operator the batches they have access to from the start. This is done with departments. With the example you described, using departments would be possible because departments can be set dynamically during run time. So for example, your user just finished keying a batch that was read in the “Indexing” department. What would happen next is that the same batch would have its department changed to “Control” during runtime. This means you would end up with a batch that went from Indexing, to Control, just what you needed.
- Dynamic departments existed in IA6.5, however, they can't be used to fulfill my requirement. Let me explain this a bit better: Let’s say I have 5 operators; A, B, C, D and E. ALL of them are members of both „Indexing“ and „Control“ groups/departments. This is requirement from the customer, because they move operators from “indexing“ to „control“ very frequently (once or more per day), depending on required workload (advanced, lean-office principles ). So, if operator B performs indexing, he can also open Captiva Desktop with „Control“ department, and perform control of the document. In IA6.5 I used FilterBatchList to hide specific batch from user B in "control", In Captiva 7.x, I no longer have such possibility. Theoretically, I could have departments such as „control_without_user_A“, „control_without_user_B“,„control_without_user_C”,... but this is practically impossible, because we have ~30 operators, and they change over time. Maybe there is some other solution, but I can't see it at the moment...
- There is another customer’s requirement that I have solved by using FilterBatchList in IA6.5 (the requirement may sound funny at first, but it comes from real world… ). Namely, operators used to pick “tidy” batches (mostly printed with laser printers), and used to open&close hand-print filled batches. They did this becuse "tidy" batches are well recognized by OCR and require significanly less typing. So, we have created a mechanism of “locking” the batch, by appending operator’s name to batch name as soon as it is opened for indexing for the first time. Operator is allowed to cancel or exit the batch, but it is now “locked” for the operator, i.e. no other operator can see it (due to filtering performed in FilterBatchList event), and the operator that opens it for the first time MUST execute it. How could I achieve this functionality in Captiva 7.x?
Also, a little bit more of information for you - in Captiva 7 EMC has expanded access limitation even more. In 7 not only can you limit what batches an operator can access, but you can also limit what they can access from that specific batch. What this means is that once an operator opens up a task you can limit what they see. Maybe you have an operator that should only be checking the image quality, then you can show them just the image and none of the fields. Maybe you have an operator that should just be keying what they see, then instead of showing them the entire image you show them snippets of the image.
- I agree that this is a welcome improvement.
Hope that helps! Keep the great questions coming, this new version has some differences in method and\or approach that take a little getting used to at first. However, once you get a chance to work with it enough the improvements are clearly visible and pretty significant in most cases!
You are correct, in Captiva 7.1 we introduced the Captiva Mobile Toolkit for enabling capture in custom mobile applications. The Toolkit provides on-device image capture and clean-up SDK, server-side RESTful services, and server-side mobile image enhancement filters. The toolkit turns iOS and Android camera-equipped mobile devices into a capture device for server-side processing of images and metadata.
While the toolkit includes numerous samples, the skill set required to build mobile applications is different than that of your typical Captiva application. To develop a mobile app, you will need the following technical expertise:
Sorry about the mix-up with the other post that 'disappeared', that was my mistake on the first send last night. I realized immediately after the initial post that you were in fact looking for something much more complex and thought the post delete worked before it was published - clearly not the way the forum posting mechanism worked
Thank you for the more thorough explanation regardless as that was very helpful and will be to others who read this.
So... I spent time talking to our staff today more in an effort to find out the latest and the greatest with their efforts on this challenge. Unfortunately the latest is that there is no current way to do what you are asking for in the current Captiva 7 Desktop release that we are aware of. Although the use of Departments does bring some nice features as we have both commented on, it does not help in the scenario you described so well where an operator has 'dual roles' with the condition determined dynamically. The use of a 'control indexer' is definitely something we do run across from time to time as well most always in the scenario described earlier with the 'double blind keying' requirement.
What we ended up doing in one of our EMC Certified Solutions (DepositCritical) where the double blind keying is typically always required for critical fields where 100% accuracy is desired is we ended up using the Captiva 7 SDK to build a custom user interface index module that has the ability to utilize onstart and other methods to provide the filtering that you are describing. Thankfully EMC does a great job in providing access to pretty much everything to their SDK and regularly encourage Partners to fill those 'gaps' for very specific and unique end user needs like the one you are describing here (since it seems like we only have this come up once in a awhile with only certain customers).
Thanks again for the great post - I will let you know if we end up finding some sort of other work around for this other than SDK development in the near future!